To perhaps lean more into why complex carbs are useful:

Your body can’t really not digest something you’ve eaten. Once it’s in your stomach, it will be broken down and gets put into your blood. With the simple carbs, you get a lot of blood sugar very quickly and your body then has to deal with that. It does so by producing insulin, which tells the rest of your body to take sugar out of the blood. It’s put into either a limited, temporary storage (glycogen) or, once that’s full, into more permanent storage (body fat).
Eating lots of sugar can also lead to your body producing too much insulin, which will cause too much sugar to be taken out of the blood, so you often have a high and then a crash/low after ingesting sugary foods.

Ideally, you want blood sugar to always stay at a reasonable level, where it can supply your brain and muscles, but where your body does not have to start storing lots of it. And that’s where complex carbs are neat, because they don’t get broken down all at once, when they’re in your stomach/intestines, meaning their sugar enters your blood at a more sustainable rate. By eating them instead of sugar, you’re less likely to put on fat and less likely to have a crash.

Opposite of neurospicy. 🙃

Oh yeah, that for sure.

I’ve heard before that it can be more difficult for folks on the autism spectrum, because we perceive more of the details in each voice, so it’s more likely to overwhelm us.

But it certainly doesn’t have to be. Neuroboring folks also don’t find it helpful when two speak at the same time.

I mean, depends on the situation. Personally, I wouldn’t call it rude when someone kind of free-fire responds to a question they hear. In that case, best course of action is to just chuckle at them responding synchronously and ask for only one of them to speak at a time.

Hmm, you mostly press the button in the top right to progress through turns as well as through the individual ‘decisions’ within a turn. And each decision is something like “What should this unit do?”, so it will automatically select a unit and you can instruct it by either clicking on the map to tell it where to walk/attack or with the buttons in the bottom left.
In your first turn, one of those units is a settler, which you might tell to found a city. In that case, you also have to tell the city what building to construct, for which it will bring up the city screen and then you select that in the list on the left. Well, and if you do build a city, you also have to select a technology for it to research, which brings up another screen with the possible technologies in a tree structure, where you select one technology and confirm it.

I’m sure, there’s tons of places one can get stuck on, but it is fairly linear gameplay, so don’t overthink it…

Well, if you played it a few years ago, the tutorial was also still rather sparse. That should be better now, too.

Lots of shops like that in the Europes…

For those with traditional music files (MP3, OGG etc.), the file format for exporting playlists is called "M3U8”.

It is literally a text file where each line is a file path.

Yeah, but the law genuinely treats (near-)monopolies differently from their competitors. What’s legal for a small company does not have to be for a company which dominates the market.

The thing is, laws are supposed to bring the greatest benefit to a society. In most cases, fairness aids that goal. But that’s not the case for competition laws, which is why they’re relatively unintuitive.

It’s like a conspiracy theory for that guy. Everyone who tells them it’s not true that you can get rid of programmers, has to be a programmer, and therefore cannot be trusted.

suddenly found myself in the Realm of Zot.

Yeah, when I got there the first and only time, I was also surprised how little separates you from Zot once you’ve made it through the Dungeon and the rune branches. Far too many of my characters have died on the final stretch…

For anyone wondering, the Rettungsgasse (“rescue aisle”) is something we do on longer stretches of road whenever congestion happens, to allow ambulances to pass through as quickly as possible. Everyone on the right side of the road keeps to the right and everyone on the left keeps to the left, forming a roughly ambulance-sized gap in the middle. On multi-lane roads, it’s formed to the right of the left-most lane.

There’s also laws for it. You can get fined, if you hold up the ambulance, because you failed to form the Rettungsgasse, or if you have the audacity to drive down the Rettungsgasse to try to skip a traffic jam.

It’s not really a thing in cities like shown in the video, as we’d typically try to drive into side roads or onto parking spaces or the sidewalk to make room for the ambulance. The laws don’t apply there either.

> C:\
> on linux

Absolutely illegal.

I mean, that seems to be kind of the point of that money. Microsoft was being anti-competitive, so they have to fund their competition.

Well, I imagine, it’s more a matter of them needing an amp, because they’re playing an e-guitar, and once you have an amp, might as well turn it up. Playing the bagpipes or a trumpet/trombone/whatever loudly is actually exhausting…

Yeah, I doubt WebAssembly when executed in a browser will become multi-threaded anytime soon, since JavaScript is single-threaded just as well. If you need multiple threads, you need to use web workers. Haven’t done anything with those yet, but I’d assume them to be usable from WebAssembly as well, since the whole JavaScript API seems to be accessible.

Well, and in Rust, I’m pretty sure the runtime that’s typically used for async stuff (tokio) will produce a compile error, if you try to enable the “multi-thread” feature flag on the WebAssembly target.
But yeah, might be more of a problem with other languages.

LibreOffice has a way to switch to a sidebar UI. I always preferred that, because of what you describe…

Well, part of the problem is that web apps themselves are kind of alien on the web. The web is generally document-based. Web apps take the document format and try to turn it into something it’s not.
There’s a way to not do the JavaScript, but it doesn’t fix things being document-based and it can be argued that it makes other things worse in some respects.

I’m talking about WebAssembly. Basically, you can write your web app in HTML+CSS+Rust and then the Rust part is compiled to WebAssembly, which then takes the role that JavaScript would normally take. It does not have to be Rust, lots of languages can be compiled to WebAssembly, but Rust has the most mature ecosystem for that, as far as I’m aware.

In principle, it is also possible to use WebAssembly to render directly to a pixel buffer, but that’s really rather heavyweight and not terribly responsive, so not generally done, unless you implement a game¹ or similar.
Alright, so back to the document mangling approach. There’s various frameworks available for Rust. I’ve used Leptos so far. There’s also Dioxus and Yew and probably others.

Advantages:

• Don’t have to write JS.
• Can write Rust. Rust has some concepts that mesh really well with frontend dev, like the Result and Option types for error handling, which you can pass directly to your rendering stack and it can show either the data or the error (or nothing).
• Can use the same language in backend and frontend and therefore also get compile-time checks that the two work together.

Disadvantages:

• The ecosystem is young. You will find barely a fraction of the component libraries as you can find for JS.
• Rust also has concepts which don’t mesh well with frontend dev, like the whole memory management concept. Those frameworks bypass that or make use of it in clever ways, but things can be a bit peculiar or overly complex at times.
• WebAssembly is sent to the browser in one big blob, because it’s a compiled program. This means you get somewhat of a loading time when first loading the web app. There’s ways to mitigate that with “hydration” strategies, but yeah, still a thing.
• While JS is often minimized/uglified and therefore not readable anyways, WebAssembly makes that even more of a reality, because it is essentially assembly code that’s sent to the browser. It does still call the same APIs under the hood as JS does, so content blocking shouldn’t be affected, but yeah, can’t try to understand the code itself. This can also make debugging during development somewhat more painful.
• Well, and it’s also yet another web standard that browsers have to support. It doesn’t make browsers simpler in the sense that suckless would like.

I’ve listed a lot of disadvantages, so just to point out that, yes, to me, the advantages are absolutely worth it. But I can totally understand, if others see that differently.

¹) See, for example, Bevy and this UI example in particular.

Damn, seems you’re right. For folks reading along: That’s not how that word usually works in German, but I guess, it is how it works in German legalese…

Yeah, Wikipedia tells me the longest word that was actually in use is Grundstücks­verkehrs­genehmigungs­zuständigkeitsübertragungs­verordnung. It was a decree from 2003 until 2007.

Basically:

• “Grundstück” is a plot of land.
• “Verkehr” is traffic “trade” in this context.
• “Genehmigung” is approval.
• “Zuständigkeit” is responsibility.
• “Übertragung” is transfer.
• “Verordnung” is decree.

So, it decreed that the responsibility of approving traffic on trade of private plots of land should be transferred (to a different government body).