Well, I’ve been a C/C++ dev for half of my career, I didn’t find Rust syntax ugly. Some things are better than others, but not a major departure from C/C++. ObjC is where ugly is at. And I even think swift is more ugly. In fact, I can’t find too many that are as close to C/C++ as Rust. As for logic… Well, I want to say you’ll get used to it, but for some things, it’s not true. Rust is a struggle. Whether it’s worth it, is your choice. I personally would take it over C++ any day.

Have you tried zed? Written in rust, has many extensions. I gave it a try, I quite like it. It’s blazing fast. But I haven’t tried on an old machine.

Tried it today, didn’t expect much, but I have to say I was pleasantly surprised at the speed and look and feel. I will give it a try for a while to see if I will switch from vscode permanently.

So, not the droid we Are looking for… :(

mexican russian joker

From my small experience with Qualcomm in the past, I’m not too hopeful. In a company I used to work for, we wanted to use one of their SoC with Linux, which they claimed they supported. It was many years ago. But was full of closed binary blobs which even when signing NDAs, we couldn’t get the source for. We’re talking user-space drivers, sensors offloaded to a separate core with closed source firmware etc. It’s Linux, but it’s not Linux in spirit, it feels so closed and proprietary and secretive. They’re coming from Android, which google architecturally enabled vendors to close their drivers by utilizing HAL. It’s the single most significant blow to Linux by any corporation so far. It enabled thousands of vendors to close their shitty driver in user-space and not maintain it for newer kernels (kernel driver is just an IO proxy for user-space drivers). I get that without it, there wouldn’t be Android phones we have today, but I expected them to slowly open up. 10+ years later, almost nothing changed, in fact - things seem worse to me.

This looks the most promising. I’ll take a closer look. Does it provide a rtsp stream?

Compatibility is iffy on some of the newer ones. Here’s a list of what works for some of them: https://github.com/Dunedan/mbp-2016-linux

This is great! I've only recently discovered jq and was thrilled to have it after bashing my head in bash for a couple of days. I replaced the whole operation with a single line. This tutorial is just what I need. I like that it's interactive and has neatly grouped examples! Bookmarking it, as I'll need it very soon again.

If it works for you, don't touch it, great. Manjaro mostly just works, but occasional headaches I kept getting, like packages being broken for days at a time, no easy place to look for solution (their repo being different to arch's makes 99%of the difficulty) made me switch to arch/endeavorOs. Eventually, they may get stable enough to be acceptable, but I don't think their way is the right way to do it and they may even harm or slow down arch development and community in the process. Just looks like arch with extra steps, so I always recommend endeavorOs, Garuda or plain Arch, before Manjaro. But that doesn't mean Manjaro is trash and in some cases, it may even be the best solution.

Yes, that’s exactly it. You could try out and see what you prefer. I tried everything, but also tastes change over time. I used to use KDE cause it felt more like windows (we’re talking XP era), later I tried Gnome, Unity, xfce, fluxbox, but then I tried i3 and it is really minimal and tiling and I don’t need anything more. Not for beginners, but after some time, it might become your jam.

Kinda like that, but a bit more. Those are desktop environments, which differ in more than just styling. Most popular ones are gnome, KDE, xfce, but there are dozens of others. Most distributions come with one directly supported, but you can install others usually and pick at login.