You’re right, but that’s not the point. The other poster said it’s a skill issue. Sure, if the person can’t run commands in a terminal or doesn’t know what’s an executable that’s a skill issue.

Getting stuck because the game is having weird glitches that show off once in a while and you need classes on computer graphics to debug isn’t skill issues imo. Otherwise are all gonna establish that Linux isn’t for non programmers then?

That’s what I do, except I straight up create the python venv in a folder, activate it and then do pip install yt-dlp. No messing up with my system.

You’re right that garbage collection makes Go simpler, and maybe other patterns do contribute to prevent complexity from piling up. I never worked with Go outside of silly examples to try it out, so I’m no authority about it.

What I meant was more of a “general” rule that the simpler a language is, the more code is necessary to express the same thing and then the intent can become nebulous, or the person reading might miss something. Besides, when the language doesn’t offer feature X, it becomes the programmer’s job to manage it, and it creates an extra mental load that can add pesky bugs (ex: managing null safety with extra checks, tracking pointers and bounds checking in C and so on…).

Also there are studies that show the number of bugs in a software correlate with lines of code, which can mean the software is simply doing more, but also that the more characters you have to read and write, the higher the chance of something to go wrong.

But yeah, this subject depends on too many variables and some may outweigh others.

That’s a good argument.

If I was gonna make a suggestion, it would be to use some formatting tool such as black to make sure your code is styled in a standard way.

The mental model I have about performance is that the higher abstraction usually beats the lower level abstraction.

So in that sense, a well architected software with proper caching, multithreading where it matters etc. will beat badly architected software (ex: one that brute forces everything). Then, that being equal, good algorithms and solutions beat bad ones. Only then faster runtimes make more of a difference, and at the bottom things like more efficient processor architectures, more efficient compiler etc. beat slower ones.

A good example is Lemmy itself, which as far as I know was made in Rust to be super fast, but then at the beginning was being DDOSed quite easily because of the way the database was designed and lots of queries were very slow. Once they fixed that, Lemmy became actually usable.

What about accessibility?

Mojo is surfing on the AI hype, so only time will tell whether it lives to fulfill the expectation.

What I’ve noticed that happened in Brazil is that most major news channels have 2 websites: a subscription one with quality articles and a free one with very summarized AI lazily written news with no details or context.

There’s really not much to it, quality content needs money and ads don’t pay off for all of it (besides the fact nowadays people just blocks them).

The problem is people are lazy and most places I’ve been, peoeple make bad commit messages and often very non informative.

Just as an example, I worked as a contractor with the biggest bank in Latin America before and basically all their server code is Java (with new code in Kotlin nowadays).

I have friends who work at the biggest bank in Latin America, where most backend stuff used to be Java. Nowadays all new code is written in Kotlin.