Ephera

Casually torpedoing the Buy European movement...

Aber gibt's einen Grund warum das ein separater Unterbefehl ist? Oder haben da die Shareholder zugeschlagen und gesagt, macht mal irgendwas mit KI und dann hat man eben so halblebig einen Alias für die normalen Docker-Befehle eingeführt...?

Personal pet theory that may also play into it: Trans people are also often in information security roles. Potentially, because when you have to hide your real identity, you start to get good at it.
And Rust also has various security benefits, especially when compared to C, but also when compared to garbage-collected languages (race conditions are largely prevented).

Yeah, did they deploy it development mode or something? It just needs to display static HTML, so just ignoring the error would fix this.

Ah, right, because of google.com and google.co.uk and such. The search engines I use, don't have the money for so many domain names, so it's just a UI selection. 🫠
With the address bar rework, you could register both of them as a search engine and then simply select the other one to change language/region.

Copying the URL could be problematic, yeah. I don't have the update yet, so I wouldn't know, if it's something real simple like just right-clicking the address bar. If you really do need it, then it should still be possible to browse to the search engine's webpage directly and issue your query via the search box on the webpage.

No...

Hmm, what do you dislike about the behaviour on mobile? Like, do you actually need to edit the URL of your search provider? Personally, haven't run into a situation where I needed that yet...

There's always been a tendency of folks reading programmer humor to be beginners rather than seasoned devs. I think, there's just more of those in general, as there's lots of fields where entry-level coding skills are good enough...

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.

Ah yes, intentionally misunderstanding someone's comment. We've all seen them.

I mean, what the heck is this passive-aggressive comment? If you disagree with me, then come at me.