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.

A wave with an infinitely long period isn’t really recognizable as a wave. It’d just be interpreted as a flat line anywhere in the universe. And as mentioned, the energy of light is tied to its frequency: E = hf. (Or with hbar • omega, but that’s just multiplied with and divided by 2π, so, the same thing.)

So an infinitely long wave would have f=0 and thus no energy.

The highest frequency you’d get would be 1/planck-time, so the energy would be the Planck constant divided by Planck time, which would be roughly 12.3 GJ. That’s a lot of energy for just one photon, but if it’s just the one, likely not world-ending.

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.

Sun films have been available commercially for a long while. Choose how much sunlight you want reflected (generally more in bedrooms that you generally want dark and cool, less in rooms where you want a view), and either get a professional to apply or do it yourself—it just takes a bit of soap water and effort.

Generally better to have the sun rejection happen on the outside of the window, so as little as possible energy gets absorbed.

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

Is the GSM2 network still functioning? I think here it was shut down so the frequencies could be reused for 5G

That’s how it starts. Just let it develop for a century or something and you’ll probably be decent at it

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.

yeah, matte in Norwegian. Same as the word for a mat (ei matte).

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!

No, but a bad MS/Windows decision is often a catalyst. I came over to Linux from Windows ME. :)

It’s generally conspicuous consumption, where the main point is to flaunt wealth.

Functional aspects like how well an engine runs or a clock displays time are part of that, as poorly functioning but expensive-looking stuff is generally derided, but you also can get great-working stuff that doesn’t look flashy.

I escaped reddit for this?