71–80 of 85 posts
Earlier quoted context omitted.
Their handling of the in-place flag is different enough to cause irritation if you forget which one you're invoking.
I'd like to change it in FreeBSD, but haven't really (yet) come up with a clever way to make it work without breaking years of scripts that may be using -i.
Earlier quoted context omitted.
I'd like to change it in FreeBSD, but haven't really (yet) come up with a clever way to make it work without breaking years of scripts that may be using -i.
Are you a maintainer of sed on FreeBSD?
What would be an advantage of switching from GNU coreutils to BSD coreutils? Doesn't GNU utils have more features?
Stability, readable code and unchanging flags. GNU project code is infamously cluttered and hard to grok (mostly since it's a pretty old codebase and GNU has always favored having too many chefs in the kitchen over fewer, but competent, chefs). FreeBSD code is also usually much more stable than the Linux counterparts; tends to be less buggy from my experience at least. GNU also has gotten in the habit over the years…
I was under the impression that it was a result of 1. supporting a terrifying spread of platforms - by the time the code handles the quirks of AIX, IRIX, Minix, Solaris, all the BSDs, and oh yeah also Linux, yes it has a rather lot of clutter, and 2. specifically implementing things in a different way than commercial UNIX™ so nobody could accuse them of copyright violation.
whoever doing this has some serious time wasting issue. Check the previous project https://news.ycombinator.com/item?id=26303996
Earlier quoted context omitted.
Stability, readable code and unchanging flags. GNU project code is infamously cluttered and hard to grok (mostly since it's a pretty old codebase and GNU has always favored having too many chefs in the kitchen over fewer, but competent, chefs). FreeBSD code is also usually much more stable than the Linux counterparts; tends to be less buggy from my experience at least. GNU also has gotten in the habit over the years…
> GNU also has gotten in the habit over the years of randomly shifting flags around for no real reason other than to make sure that they stay as the coreutils. Do you have examples of this?
Earlier quoted context omitted.
Could we call it GNU-free/Linux?
Some people call that Alpine.
There’s a Rust coreutils too.
Some utils are faster already, and they are working on cp and mv progress bars. From the fosdem 2023 presentation: https://sylvestre.ledru.info/presentations/coreutils-fosdem-... == Example #1: $ hyperfine -r 10 \ "target/release/coreutils sort -R shakespeare.txt > shakespeare.txt.rand; \ target/release/coreutils sort shakespeare.txt.rand > /dev/null" \ "sort -R shakespeare.txt > shakespeare.txt.rand; \ sort shakespe…
Earlier quoted context omitted.
I don't know about you, but I can't eat code. That said, some people don't care about outside contributions or reuse, so I guess I find the pro-GPL partisanship more than a little misguided. Some people just have different goals, and that doesn't make them better or worse, just different.
And that's the reason for their downfall.
What downfall, exactly? If I want to get paid, the GPL doesn't help me with that. If I don't care about outside contributions, the GPL doesn't provide any advantage. Insofar as I have written something that is complete in itself then a BSD license makes perfect sense.
Earlier quoted context omitted.
I don't know about you, but I can't eat code. That said, some people don't care about outside contributions or reuse, so I guess I find the pro-GPL partisanship more than a little misguided. Some people just have different goals, and that doesn't make them better or worse, just different.
And a project can't survive without the code. And even then companies are famous for leeching on open source projects, with gpl you at least have some hope of companies leaving you alone or giving back something.
How is it "leeching" if I deliberately release my source code under a BSD license because I don't care if other people use it or not? It can't be "leeching" if I don't care about their contributions either. The only other scenario that would apply is if I wanted to be paid for my work... in which case neither a BSD-like license, nor the GPL, would be adequate.
This is the problem I have with GPL partisans: They refuse to accept that projects can be completed, or that anyone can have any interests other than GPL-compatible ones.