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.
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.
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.
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
The first command installs a package.
The second command updates all packages.
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…
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…
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.
The Edge engine before Blink was called “EdgeHTML”.
Because shaking your cursor to spot it is kind of universal?
What is this article talking about? That’s a UX change. It has nothing to do with privacy or Mozilla’s commitment to privacy.
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).