Ephera

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.

Yeah, fair enough. I use laptop keyboards so much that I need to get used to a full-sized keyboard, whenever I use one. 🙃

Unfortunately, laptop keyboards are a mess of different layouts, so it’s not either like I can sit down at someone else’s laptop and immediately know where everything is…

As a software engineer, I’d say statistics is more useful for journalism. If in doubt, you could be analysing papers about entirely different fields, like physics or biology or whatever. Those also deal with statistics.

But I also just feel like there’s not terribly much journalism to be done surrounding computer science. There’s the bog standard news cycle of tool XYZ had a new release, but beyond that, it’s more a field where techies try out or build things and then they tell each other about it.
I guess, you could also consider some of the jobs adjacent to computer science / software engineering, like technical writer or requirements engineer or project/product owner. In some sense, the latter two involve interviewing customers and their domain experts to figure out what’s actually needed.
Having said that, to my knowledge you typically get into these roles by being a software engineer and then just taking on those tasks regularly enough until someone notices…

One decent reason is that it brings the mouse closer, so you can move your hand over more quickly and are more likely to find the right keys when moving the other way.

It’s a programming language, which is particularly relevant for Linux, because it doesn’t require a runtime (separate program that runs the code). This allows it to be used in the kernel.

But it also means that it’s very good for building libraries. With a small bit of extra work, virtually any other programming language can call libraries implemented in Rust (like you can with libraries implemented in C).
Add to that, that Rust allows for performance similar to C and makes lots of typical C bugs impossible, and suddenly you’ve got folks rewriting all kinds of C libraries and applications in Rust, which is something you might have also heard about.

Since no one else responded so far, the last thing I remember about it is that it got overrun by conspiracy nuts. Don’t know, if that’s still the case or if it was just a local thing, but yeah.

Yeah, as I understand, in the terms of language design theory, it is technically still “manual memory management”. But since you don’t end up writing malloc() and free(), many refer to it as “semi-automatic” instead, which certainly feels more accurate.

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).

I figured, I’d ruffle some feathers by saying that. 😅
But yeah, I stand by my point. Just because your target users are capable of dealing with complexity, doesn’t mean you should be making use of that rather than simplifying usability, since your users have plenty other things they could be learning instead.

I will caveat that I can see it becoming worth it to learn an intricate logic for a power user, when things fall into place and make sense at a higher level as you learn more about it.
But in my experience, that’s just not the case with package managers. You need a few specific commands to be obvious and then the special cases can be obscure flags.

Arch’s package manager is pretty terrible.

Here’s two commands. See if you can guess what they might do:

pacman -S package_name
pacman -Syu

I believe, there’s some sort of logic to the letters, but man, most users seriously do not care. They just want to install, update and remove packages 99% of the time, so they shouldn’t need to learn that intricate logic for three commands.
I guess, you could use pkcon to do that instead, but that doesn’t really help new users…

Larger open-source projects tend to have forums. Here’s a few off the top of my head:

• https://forum.luanti.org/
• https://tavern.dcss.io/
• https://users.rust-lang.org/ (and https://internals.rust-lang.org/ )
• https://forums.opensuse.org/

If a GUI can be built which accomplished something in 1-2 clicks, then there’s very likely a CLI which can do the same with 1-2 commands, as CLIs are easier to implement than GUIs…

Original link (in Spanish): https://www.xataka.com/servicios/foros-internet-estan-desapareciendo-porque-ahora-todo-reddit-discord-eso-preocupante

Well, vegan foods with lots of proteins include: Beans, lentils, peas, nuts, peanuts, tofu, soy.
Personal favorites are red lentils (cook pretty quickly and don’t need to be soaked before) and pre-cooked white beans (I just have a jar of those in the fridge and will scoop a spoonful into all kinds of meals).

Proteins are cool, because they stick around in your stomach for a while, but they’re bad at filling you up. For that, salads and veggies are the best. Sometimes, I’ll eat an entire bowl of salad, which is not a lot of calories, but still fills me up.

I would also recommend slowly changing your diet over. Your gut microbiota need time to adjust to a different diet. If you don’t give them that time, they can kill your will pretty effectively.

Well, it was more of a rant, I wasn’t exactly asking for suggestions. But you making a suggestion was perfectly fine anyways. I do just have opinions on proprietary Android apps.

I mean, thanks for the suggestion, but it doesn’t seem to be open-source, so that’s a hell no from me…

I have this problem with Android. Google has turned the filesystem into unusable garbage, so you’re lucky, if you can launch a gallery app with a file path and it allows you to actually go through the images in that folder.

And of course, that’s with a local file path, so the situation is completely hopeless when your images are on a network share. Unless the gallery app itself implements the network protocol, you’re out of luck.
Wanna guess how often that happens? Yeah, it simply doesn’t. Even if it’s theoretically just a library, when you build it into the gallery app, that dev has to continually maintain and test it.