That seems to me to be a direct result of too many actors involved in the creation of the Deutschlandticket actually ebing against this ticket, and so those in favor tried to appease them and created this absolut disaster of a booking process. There is no other reason for this otherwise, and it would be trivial to sort this out by e.g. having a validity period of 31 days, or always going until the end of the month and costing only a percentage. But that would be too easy.
I was with you until this point, but 1.2 is bigger than 1.10, because 1.2 is a shortened version of writing 1.20 _unless_ you explicitely want these to be version numbers or something like that. The normal expectation would be to treat numbers as, well, mathematical numbers, and not SemVer, especially if we only have one decimal point, don't you think?
As I said, the sorting rule won’t always give pleasing results, but it seems to me like a simple and reasonable modification of lexicographic ordering.
1.10, the number, is equivalent to 1.1. It is less than 1.2. You say you want numbers to sort as numbers, but you want 1.10 to be greater than 1.2.
Do you consider '1/4' to be a number? Should it come before or after '1/3'?
I'm guessing that you don't want to sort one character at a time if you encounter one of [0-9]. Instead, you want to group all consecutive [0-9] as a single sortable number. But aren't characters '.', ',', '/', '-' also part of numbers?
It doesn’t work for decimals. It also doesn’t work for pi, or most dates. That’s okay. Supporting those cases would require “reading your mind” / trying to guess what the user wants by applying opaque rules. I certainly don’t want that.
Treating consecutive digits as numbers is a simple modification (I still think it’s quite simple) that is easy to understand and supports 99% of real-world use cases.
Just some days ago I found some videos (not sure if on YT or Instagram) from a young women who took over a restaurant from her grandfather, and she was tattooed, had colorful hair, and was a great chef. She faced a lot of backlash in the rural area where this was located due to her looks, and I assume, this is also a problem where young people try once and then forget about it, or don't even try...
Yeah, Japan is an extremely conservative country in many aspects, but it looks like young people are slowly pushing against some obsolete social rules. A year ago there were big news when big corporations like McDonalds ended their hair color rules, because otherwise they can't find enough employees.
Just to add this to make it more clear: GrubHub used to belong to the same company as Lieferando, and was only sold at the end of 2024. So in a way this comment is more a "yes, they did it in the US as well".
Technically, you can use them for payment, they are still valid money; but the price will be rounded to 5 cents when paying in cash and you won't get them in the other direction.
The 1 and 2 eurocent coins are still legal tender in the Netherlands, stores just have the option not to accept them and are allowed to round prices to avoid having to stock them (if communicated beforehand).
It's been years since I last saw a eurocent coin, but it's been eliminated by permitting businesses to remove the need for them, not because they're being phased out.
Small nitpick: the example "LATIN SMALL LETTER SHARP S (“ß” U+00DF) uppercases to the two-character sequence “SS”:³ Straße ⇒ STRASSE" is slightly wrong, it seems to me, as we now do actually have a uppercase version of that, so it should uppercase to "Latin Capital Letter Sharp S" (U+1E9E).
The double-S thing is still widely used, though.
Duden mentions this: "Bei Verwendung von Großbuchstaben steht traditionellerweise SS für ß. In manchen Schriften gibt es aber auch einen entsprechenden Großbuchstaben; seine Verwendung ist fakultativ ‹§ 25 E3›."
But isn't it also dependent on the available glyphs in the font used? So f.e. it needs to be ensured that U+1E9E exists?
I don't think there exists any code that makes uppercasing decisions based on the selected font. Besides, if it doesn't exist in the current font, there's probably a fallback font.
But what if you need to uppercase the historical record in a vital records registry from 1950ies, but and OCRed last week? Now you need to not just be locale-aware, but you locale should be versioned.
Not just a Swiss user as there are many German words that use ss and not ß. And having an ss where there should be an ß will be a lot less disruptive as the inverse because people are used to ASCII limitations.
"Unlike the NT™, system does not feature a separate Hardware Abstraction Layer (HAL) between the physical hardware and the rest of the OS. Instead, XT architecture integrates a hardware specific code with the kernel. The user mode is made up of subsystems and it has been designed to run applications written for many different types of operating systems. This allows us to implement any environment subsystem to support applications that are strictly written to the corresponding standard (eg. DOS, or POSIX)."
Modern NT builds haven't really been using the HAL the same way either. It's been a pain because windows on arm kernels have been pretty tied to Qualcomm hardware so far.
HAL.dll was intended to solve the exact same problem as device trees. That's why there's custom HAL.dlls for weird x86 but not PC platforms like some of the SGI boxes. Stuff like sure, it's the same processor arch, but the interrupt controllers, system bus, etc are completely different and not introspectable via normal PC mechanisms.
The issue is that WoA kernels have moved away from heavily embracing hal.dll, instead inlining a lot of functions into the kernel that used to be hal.dll functions for perf reasons. If they kept the original architecture it would have been easy, but they've changed it fairly recently to be less portable.
