Humans also frequently need to try a wrong approach first to get the idea of a better approach, no matter if we’re rested or not. Which is why it’s important to be able to throw away prototypes rather than push an “it seemed like a good idea at the time” to prod.

But having a good sleep, walk in a park, shower, etc lets us think better than if we’re just banging our heads in the same corner all day long. Breaks are important. General health, too.

Mandatory reminder that it’s easiest to have the biggest percentage growth for the smallest categories.

Pissing? In this heat?

Remember to get enough salt as well! Hyponatremia is no fun :(

Yeah, JSON is essentially a side effect of having JavaScript already. It makes sense that it shows up a lot of places, especially web. But just like with JS, it’s not really good, just ubiquitous.

I know, I just think it’s annoying. I even turned on some option to see “adult games” in Steam for a little while because I thought it meant it would shut off the age verification for games like BG3. Instead it started showing me porn games (with no age verification), while still requiring an age check for actual adult games.

Americans.

Side note: I wish they’d just call them porn games, not “adult games”. I expect adult games to be games for adults, as in, the games that are age-restricted to 18+.

Or are they going to start removing stuff that’s PEGI 18 / ESRB M, like Baldur’s Gate 3? No? Exactly.

We could probably stand to have some organisation standards in repo roots, but I tend to agree that dotfiles aren’t the way to go there. The project root is similar to ~/.config and the like: When you’re there you should not be subjected to further hidden levels. Those config files are a significant part of the project.

State files however, like all the stuff in .git, lockfiles and the like are generally¹ fine to hide away. Those are side effects of running other tools, not ordinary editable configuration. Same goes for cache—and both cache and runtime files should likely go in the ordinary XDG dirs rather than be something every project has to set up a gitignore for.

If anything I’m more frustrated with the C projects that just plop every source file in the root directory.

¹ Just don’t make it too easy to sneak unexpected crap in there. We don’t need to make the next Jia Tan’s job easier.

I’ve very barely dipped my toes in dbus before, and the option to have something else is on its face attractive (not a fan of XML and the late 90s/early aughties style of oop), but JSON for a system interface?

I mean, Kubernetes shows that yaml can work, but in this day and age I’d expect several options for serialisation, and for the default to be binary, not strings.

String serialisations are primarily for humans IMO, either as readers or writers. As writers we want something with comments (and preferably no “find the missing }” game), so for that most of us would prefer something like TOML if the data is simple enough, and actually Yaml for complexity at the level of Kubernetes—JSON manages to be even more of a PITA at that level.

But machine-to-machine? Protobuf, cap’n’proto, postcard, even CBOR should all be alternatives to examine

There’s wasm if you need to target browsers.

Similar in Norwegian: Ugress. Un-grass.

I’ve heard one definition of it that I like: The grass that your (grazing) animals won’t eat.

We’ve also recently introduced Coding Challenges to our site! These new challenges represent a new, fun way for developers to level up by tackling captivating puzzles and earning recognition for your skills and creativity. It’s a rewarding way to practice and expand your knowledge with the Stack Overflow community in a space that celebrates diverse and unique approaches.

aka

>pls provide training material for the LLMs for free :pray:

lol. lmao, even

When you see that sign you must. When you see this sign you can:

Often it is preferable anyway, but there’s a difference between informational signs (blue rectangle) and mandating signs (blue circle). Here in Norway we generally don’t have mandatory bike & ped paths, just the voluntary ones.

These combinations are generally not a good fit for urban areas, there we should have bikeways with sidewalks:

(Generally new infrastructure in urban areas is being constructed as bikeways with sidewalks, and old shared bike/ped-ways are being upgraded to bikeways with sidewalks.)

Yeh. Ubuntu also discussed it back in 2019, and wound up keeping some of it so Steam would keep working.

I expect the willingness to bend over backwards for one proprietary and very profitable app doesn’t last forever, and given how involved gaming often is with pushing technology, it’s frankly weird that Steam is still shackled to 32bit like that.

Yeah, I think the fact that the next LTS will be 26.04 is the driver here, I just get the impression that things might get a little rocky and that they might’ve been better off had the next LTS been further into the future.

But it’ll be a real smoke test release, at least. Hopefully they have enough resources to fix the issues that are uncovered, and don’t wind up reverting for the LTS, or with a crummy LTS.

I’m generally an en_*.UTF-8 user (even tried en_DK.UTF-8 for a bit for a reason we’ll come back to), so I don’t have a complete picture of it and would have to go look at the documentation or source for that, but I’d expect

• documentation
• date formats: en_DK.UTF-8 should give you ISO8601-formatted dates, if I can’t have that I at least want DD/MM/YYYY; the US-american nonsense is just plain unacceptable
• sorting: e.g. Norwegian will have …zæøå and expect aa to be sorted as å, the Swedes have …zåöä, the Germans …zäöü, the Turks will want ı and İ sorted and upper/lowercased correctly, and there are some options around how you deal with “foreign” letters and diacritics.
• Probably more stuff relating to LC_* that I can’t think of off the top of my head

but in any case, an ls -l output should be different depending on your locale, and in ways you likely don’t even think about as long as it looks normal.

Yeah, I think those are just lacking in the internationalisation?

People like me, who at most have some reading glasses needs and have their computer set to generally English utf-8 will be likely be fine.

Between that and the uutils-coreutils, Ubuntu 25.10 sounds like it’ll be an interesting experience for users, especially those with accessibility and internationalisation needs.

Having had a look at the archived version linked below, it seems pretty clear that it’s entirely hogwash:

• The referenced init system replacement is called “rye-init”
• The wiki does not have anything on “rye-init” or even just rye
• The only hit on a package search for rye is rye, the precursor to uv
• I find no general search hits for rye-init, except references to the rye mentioned above (as in rye init), and some hits for this article and forum posts with people confused about it.

The Commission chose this route to avoid its proposals being vetoed by Slovakia and Hungary, whose governments have opposed the ban. Sanctions would be the strongest legal basis for banning Russian gas, but require unanimous approval from all EU countries.

It’s good that they found a way around those fifth columns!

I think if someone’s curious about that they might be in the market for something more like just, as in, here’s an example for running recipes with uv or use [script($INTERPRETER)].