There are also many (some in the comments to this post) who have excluded themselves because of it.
Not that they should have the final word the subject of course. I'm just saying you can't assume they they didn't because they have a contrary opinion.
I am saying that they can get away with lower quality subtitles in such places because the average user does not care that much about it. The target audience is not the same as when they first started doing subtitles and it doesn't make business sense anymore. Anime is not special. If the rest of the video streaming industry can get away with simpler subtitles, then Crunchyroll can too.
People that are into anime are into anime because it is special. JoJo's Bizzare Adventure is cool when Marvel movies aren't because JoJo was made by one mangaka and a Marvel movie is made by a committee of committees.
Same way people choose what to listen to in other kinds of media most likely.
I am constantly asking people who I admire or respect where they get their news/information from because I'm trying to find better ways since the general media landscape is very dismal.
I've lived in several countries in 3 continents now, and the more I get to
know different peoples, the more I feel we're all the same—albeit stuck in these almost kaleidoscopic ways of outwardly displaying the very same humanity.
Perhaps OP got fixated on the collective differences instead of seeing through them. Perhaps.
The major difference in the more extreme case were I was shot at, or had a gun put to my head, or was caught in between a knife fight, or systematically on a regular basis saw people getting the shit beat out of them. Which I acknowledge can happen anywhere, but such trauma is not so easily rationalized when considering what I'd like my kids exposed to and after viscerally experiencing it in real life.
In any case, "I've found good people from all sorts of cultures and countries" is something I've definitely found to be true, and I don't view that as mutually exclusive. The trouble being, the amount of bad things a certain sector of people get away with can vary a lot depending on where you are and what the cultural response and incentives to that is.
Neither this issue, which doesn't appear to be a bug at all but merely an unimplemented feature, nor the fact that uutils doesn't (yet) pass the entire testsuite, seem to me to at all be an indictment of the uutils project, merely a sign that it is incomplete. Which is hardly surprising when I get the impression it's primarily been a hobby project for a bunch of different developers. It does make me wonder about the wisdom of Ubuntu moving to it.
It's a part of Ubuntu 25.10 to get it ready for prime time for Ubuntu 26.04.
Users who need stability should use the LTS releases. The interim releases have always been more experimental, and have always been where Canonical introduces the big changes to ensure everything's mature by the time the LTS comes around.
> Every six months between LTS versions, Canonical publishes an interim release of Ubuntu, with 25.10 being the latest example. These are production-quality releases and are supported for 9 months, with sufficient time provided for users to update, but these releases do not receive the long-term commitment of LTS releases.
Maybe the thought is that there will be more pressure now on getting all the tests to pass given the larger install base? It isn't a great way to push out software, but it's certainly a way to provide motivation. I'm personally more interested in whether the ultimate decision will be to leave these as the default coreutils implementation in the next Ubuntu LTS release version (26.04) or if they will switch back (and for what reason).
they have a tendency to try novel/different things, like upstart (init system), mir (desktop compositor (?))
and this is probably a net positive, there's now an early adopter for the project, the testsuite gets improved, and the next Ubuntu LTS will ship more modern tools
So this is a good thing even for coreutils itself, they will slowly find all of these untested bits and specify behaviour more clearly and add tests (hopefully).
yeah, based on some more digging, it looks like a test case for `date --reference` in GNU coreutils was only added a few hours ago [0] so I assume it was in response to this bug.
but I don't think that should let the uutils authors off the hook - if `--reference` wasn't implemented, that should have been an error rather than silently doing the wrong thing.
after even more Git spelunking, it looks like that problem goes all the way back to the initial "Partial implemantion of date" [1] commit from 2017 - it included support for `--reference` in the argument parsing, including the correct help text, but didn't do anything with it, not even a "TODO: Handle this option" comment like `--set` has.
> then that would mean the upstream tests still need work
More coverage is nice, but the foremost care should be to do the right thing, not have some tests for it. Some cultures do not include testing-first and instead treat tests as a tool for edge cases. Nobody bothered to add a tests, for -r, because the did not thing of that as an edge case, but as a core behaviour.
"Open Source" meaning the license is OSI approved (or at least meets the definition for "Open Source" by the OSI[1]) and source available is anything to which you can get the source to, but the license doesn't meet the above criteria.
Accepting patches isn't a requirement, but it roughly means that you can make your own changes, publish those changes, and use the software for whatever you want. These don't automatically come with being allowed to view the source code.
The latter meaning the four freedoms or something equivalent (e.g. complying with the OSD and/or the the DFSG). They don't have to accept patches upstream but they do have to permit sharing your patches with other users one way or another.
Not that they should have the final word the subject of course. I'm just saying you can't assume they they didn't because they have a contrary opinion.