Yeah, saying “most GitHub users can’t live without a commercial entity” is such a nonsense. GitHub is successful while it works well. The moment it doesn’t, there will be other services.

At the same time, I feel like nowadays there’s less forums or places people can ask help with, although today ChatGPT can be a good help with newbie questions.

TumbleOS

The problem with Sublime is that it’s a paid one, and not everybody wants to pay for something that is perceived by the community as something that should be free and open source.

Yeah, I guess the idea of VSCode isn’t to be a “ready to use” IDE, but to be configurable — which it is.

The main thing that makes it popular nowadays is the ecosystem of plugins around it. Ex: when Copilot was released, I believe the VSCode plugin was the best one.

Also many frameworks docs have instructions on how to use it with VSCode and which plugins to install, such as some web frameworks and Flutter.

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.

There’s no free lunch after all. Go’s quick compilation also means the language is very simple, which means all the complexity shifts to the program’s code.

This kind of thing can be easily automated nowadays. It’s not really a problem.

And at that point you’ll also have a better idea of the problem and solution.

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.

I think Lemmy has very few users to have such limitations.

It helps to look up certain concepts in the Wiki (Arch Wiki is probably the most complete and well explained) as you come across them. The idea is to increase knowledge little by little, but over time it compounds.

First thing I install in each platform is fish

Seems like it allows self hosting as well. It seems to have more stuff indeed.

It isn’t a native UI, but the effort made to look native on each platform must be appreciated.

This is very useful. I think I’ll stick with it.

As much as I do like programming in Java, you have a good point.

What about accessibility?

Or anything that downloads code from an untrusted source…

That’s the same thing I’d do when o used Arch. Always kept up to date to announcements of something major like a DE upgrading and usually would reset all the settings just in case. It avoided me any problems during the years I ran it.