Baldr

Surely they will never stop trying, and the challenge will get certain people really worked up to be creative in how to do it.

Remember iOS used to have a huge community on hacking the phone. The interest slowed down after Apple sort of implemented the features people used that for. iOS is certainly more secure nowadays, but there’s no shortage of vulnerabilities being constantly discovered, and with vibe coding apparently being integrated even large companies, I suspect more and more dumb vulnerabilities will be looming just waiting to be exploited.

That says you’re already way beyond the non tech savvy user.

I’ve been thinking about this and I wonder if Linux can have more success if we have pocket computers that gradually add phone functions instead of trying to have phone hardware work with a system that isn’t made for phone-like experience in general.

That was an interesting read.

Huh? It seems to me these are all books about technical skills.

Also AWK is made to be fast, right? I suppose doing something in CPython in a non efficient way might not be noticeable with a bit of text, but would show up with a large enough data stream.

This is the best I could find: https://www.gnu.org/distros/free-distros.en.html

Yeah, just a note, basically these Linux distros are the same at their “core”, but what differs among them is mostly about the software they have and the way they’re managed.

So you have distros that offer only open source software in their repository, some include proprietary drivers. Some distro families will have some differences in the path of certain folders, different families use different formats of their packages (which include the actual binary of the software together with the metadata about how to install them in the system), although a purely Linux binary should be executed in any Linux distro. Some offer more guidance during installation and setup, some offer a more “raw” experience that force you to chose every little detail, and so on.

Another difference is in their philosophy of how the packages and dependencies are made available. Distributions such Arch Linux and its derivatives always offer the latest versions of each package, reason why they’re called “rolling release”. Distributions such as Debian offer a specific version that’s “frozen” and tested thoroughly until a new version of Debian is released with more updated software.

Some say a rolling release distro is better for gamers because you always get the latest features and performance improvements, but they’re naturally less reliable than a stable distro.

So I’d say the important thing is to understand the trade-offs so that you can choose the best thing for you. And also there’s no downside of experimenting different distros in a virtual machine, for example.

Also has an interface that clicks easier with people used to Windows.

Here’s a nice pic that make you feel less “lost” about how some popular distributions relate to each other:

This is a troll’s or a teenager’s line of thinking.

Kinda reminded me back in college I had a friend who I’d describe as a genius in computer science and programming. I was always so jealous how he was so knowledgeable about everything teachers talked about to the point of correcting them sometimes (and hurting the ego of some of them, which isn’t very smart).

He was like a C++ nuts to the point of having some of his code on the Boost library (which was impressive for a 20yo), but when Rust started getting popular back then, he really got into it and quickly became an “evangelist”. For some years, everything was about Rust, if you stopped to talk to him.

I met him year later and asked if he was still working with Rust, and he said after using it for enough different use-cases, he actually started to dislike it and pointed out a lot of problems and flaws that I wouldn’t possibly remember. I think he also said the community was very toxic and was taking the language to a direction he didn’t like. I suspect nowadays he is just another fella using Lua and C++ for his personal projects.

Even if it was, there’s no way to know, people can just lie. It’s not like it will be obvious, some people might have a feeling it is (based on their experience playing with LLMs) but won’t be able to point exactly why.

Besides what other people said, one example is classes being closed by default (you need to explicitly set a keyword to make them open to extension). That was done to prevent inheriting from classes that weren’t designed to be inherited, and forcing you to use composition instead.

Imagine when the author hears about the “Create an app in 20 minutes with AI” tools.

Only chatGPT has these kinds of comments as if you’re seeing code for the first time. 😆

I’m not against adding comments where is needed: in the company I work for (a big bank) my team takes care of a few modules and we added comments on one class that is responsible to make some very custom UI component with lots of calculations and low level manipulations. It’s basically a team of seniors and no one was against that monster having comments to explain what it was doing in case we had to go back and change something.

For 99% of the code you just need to have good names though.

Just a reminder that reencoding already compressed videos is a recipe for destroying the quality, unless you’re using a very high bitrate, which quite often gets you the same size as the input video.

I think the consensus is that if your video isn’t 4k or higher, there isn’t much gain in using HEVC if it is already H.264.

So if you want to store them long term, reencoding them now means that if you decide to do it again later (for whatever reason) you’ll have too many artifacts accumulated.

Yeah, a video is a video.

If the distro is rolling release, it can always support the latest software in theory, you’d just need to have the correct package formula, which is exactly what AUR offers.

The problem with AUR is just that the author of the package is likely not the author of the software and not affiliated with the distro, so you should normally check what the script is doing.

I really understand how hard is maintaining something for every single package manager and distributions

But for apps distributed in your system’s package manager, it’s not the devs that are distributing them in every package manager. It’s the distribution itself that goes to each repository, checks and tests the dependencies they need and creates the package for the distribution, along with a compiled binary.

When they aren’t offered in the distro’s package manager (or the version is outdated because the distro isn’t rolling release) things become more complicated indeed, and sometimes you can’t even do it because the dependencies are older than the ones you require.

Also Windows has a button similar to “don’t update this week” or similar.