You can estimate roughly if you know the scope amd constraints.
And you can't plan if you don't have rough estimates (not counting OPs example)
comments
Military. Search and rescue, specifically.
Wow. Idiots being idiots. The guy tried to play with legal rules and - surprise - lost. I am glad you got out of there in time
If you think I have any interest in personal squabbles over 8 lines of code, I don't.
That meme at the start was directed at your argument, not you in particular; those are not the same thing. I apologise if it came across as personal to you, but it wasn't meant to be. Notice how I immediately went to discuss the actual topic with no further "personal attacks" until you decided to get pissy with your next comment. Had you just shrugged and actually wrote your counterpoint instead, that would've been the end of it. You didn't. Just... you know, if you wanna go around being snarky on the internet, be prepared to receive some snark back as well.
With that said, I think the argument about uutils' license is a much more sound one. As a matter of fact I expressed the same concern a over year ago, albeit in a much less elaborate fashion:
https://lem.lemmy.blahaj.zone/post/23171431/13400085 (Which of course I didn't expect you to dig up because that'd be absurd)
I'm not a big fan of uutils, believe it or not. It's not nearly as stable as they tout it to be, they broke cp recently as an example, and it's is generally not a step in the right direction IMO. Still, the fact that uutils may be ill conceived doesn't invalidate the fact that relying on public, official, C APIs is perfectly reasonable. Both can be true.
Had this post been about the license instead of "oh look the hypocrites use C APIs in the end" as if there was any alternative, we wouldn't be having this conversation.
You're still doing it ...
It's one thing to treat open source like a giveaway and an other to treat it like infrastructure. If that difference doesn't matter to you then there's probably no reason to continue this conversation, but since you asked:
The main downside of the MIT license compared to the GPL is that it doesn't guarantee that derivative works remain open-source. This exposes code to a few key risks:
- Proprietary "Forks": Companies can take MIT code, make improvements, and sell a closed-source product without contributing anything back. This is its biggest weakness. Competitors can create modified, closed-source versions that might splinter the community and reduce its control over the project's integrity.
- No Patent Protection: MIT offers no explicit patent grant, so if a user of your code is sued for patent infringement, the MIT license offers no defense.
The GPL's "copyleft" policy is specifically designed to prevent these issues by ensuring that modified versions distributed to others must remain open source.
The good news is that code under MIT can be re-licensed as GPL by the copyright holder, but not the other way around. Unfortunately that sort of change probably won't sit too well with uutil's funding agreements.
If I were to depend on this project, 5 years from now, I’d rather not wake up to find the core contributors sold or yielded to a closed-source vendor.
Notice, I didn't once go after anybody with personal attacks over this. You couldn't seem to stop yourself.
Derp. Yes. I dropped a "reverse".
No, it is not rust implementation if the library (not does it call itself that). It is a rust implementation of one of core utility programs. Here is the code it reimplements, it is similarly short, and hopefully dispels the confusion - https://github.com/coreutils/coreutils/blob/165b62de8083ed9dec9ef4e1699ed44c3c7a2b91/src/logname.c
there's only one person here being butthurt about this whole situation and trying to be confrontational and it ain't me.
coreutils has lots of stuff in it, there's going to be trivial stuff in it as well, which has to be programmed if one wants to make a full rewrite. I don't get what the big deal is. how is that sabotaging free software in any way?
There's definitely some actual business logic in coreutils that can benefit from being actually written in a memory safe language of some kind.
so despite this not being an example of that you just had to chime in with a general statement? Why so thirsty to talk shit for no reason?
Mine was more of a general statement. There's definitely some actual business logic in coreutils that can benefit from being written in a memory safe language of some kind. I find complaining about getting a simple string using C APIs on a C based OS to be a pointless critique. That's not cannibalizing C APIs, it's making use of the only thing that's available.
I'd love to hear about how this improves on the original implementation.
I'm sorry but you sound like this: 
(Not a Rust zealot to be clear, if something works and is fast enough idc what it's written in)
To be fair, I doubt there's much that can be done about having to use C interfaces when interacting with Linux itself.
That's a really good budgeting idea. My worst boss wanted the estimate accurate to within fifteen minutes. He churns through employees like popcorn.
I thought Dutch auctions were where you force the covers over your SO's head and let rip.
I love your boss based on just this. You in private or MIC? I know a Harrier/F35 wrench that I'm trying to get to move someplace nicer.
My favorite place I worked, it was a 9-5 but really just get your work done and be in the office from 11 to 2 because that's when all the clients call. We'd close our doors and turn off the phone one day a week just so we could get work done, because every week there's at least one day we all spend manning phones and putting out fires all fucking day instead of doing the work we're paid to do.
It's nice having that kind of pull/weight to throw around, but sometimes the boss still won't listen. Different industry, we had a major change in tax law happen. I read about it, figured out how to do it, then told the boss that we needed to start now training the company on the new method because it would take a year for us to catch up.
His response was to ignore it, because "congress is going to undo the law". I left for another firm, precisely because I didn't want to be in charge of the last minute project he'd assign with a month to go on a hard legal deadline. Got a phone call about two weeks before the deadline. Fortunately it went to voicemail because I couldn't stop laughing for like half an hour.
I thought Dutch auctions were where your date and you split the costs of the bid.
I have so much to learn about microeconomics
Dutch auctions are the ones where the high initial price decreases until someone buys the object.
Nothing is more triggering to me than the question "how long will this take?"
It will take as long as it fucking takes, and you shouldn't be reporting anything until it's done. Measure progress by fully working, end-to-end features, not by a number of hours someone pulled out of their asses.
Haha! Yeah, I do this with requirements creep:
- Can you also compete task C while you're there?
- Sure! In this timeframe which features are you prepared to sacrifice to make it happen?
- ...I'll think about it
Works every time!
That pattern is also recommended in the book. Break down estimates into chunks of 5 hours or less.
With lots of smaller tasks, estimates tend to both be more accurate due to smaller scope, and some of the over/under inaccuracies will cancel out.
i didn't expect how spot on this would be
All tasks are highest priority.
Then why do we even assign priorities?
Because they all need to be done.