Deckweiss

the window rules one really fucks me up.

It stopped working at the beginning of the year for me and nobody gave a shit about the bug reports.

Now I have to keep juggling windows and their sizes every day like a caveman.

Income from Steam is what ultimately made gaming on Linux viable. And to do that, they made significant open source contributions.

So I'll keep giving them money of course.

Depends on the career path. Some need only the very basics - for example in frontend development, you'll mostly use % and basic +/-.

tbh. Most of the useful programming related knowledge you'll learn at yoyr first job, not at uni.

The curriculum sometimes will force you to learn something unrelated to your career and it has multiple purposes:

People learn the fastest in the topic where they already know a lot. And the slowest where they know very little.

Learning stuff outaide of your comfort zone literally works out your brain. You learn to learn. And your thinking becomes more flexible.

You should not become somebody who is only good at one narrow singular task and a complete idiot at anything else.

You never know if it becomes useful later in life. So I suggest still trying to do your best at any topic. And studying more for the exams where you are not as proficient.

As to which career path to go for:

Don't be afraid to change midway, but make sure that you enjoy it. If you enjoy compsci, keep at it. (Or if you have student loan, put some more thought into the cost of switching).

Thats great!

But I think we need to look at it from the perspective of somebody migrating from GitHub. If OP is used to the GitHub GUI and uses it extensively in their workflow, they will probably be very frustrated while trying to do the same on sr.ht .

Whats your website stack?

How do you host it?

Share the link to your site or an example log so that we can check out what kind of data needs storing.

There are several ways to store some data either on the users end or on the backend, with different pros and cons. But which one you should pick is highly dependent on the stack and the details of your needs.

https://github.com/schlagmichdoch/pairdrop

This works really well. The readme says "local network" at the beginning, but it works across the internet by sharing a link.

GPT4All is a nice and easy start.

Bottles is a noun and not an adjective.

Also bottles has no IT related meaning, while immutable does.

"Immutable OS" is not a product name.

An "immutable" OS becomes mutable whenever a user wants to change anything on it.

Now imagine I keep describing my car as undrivable, because it only becomes drivable when somebody gets in and drives it. - You'd think that this is a completely deranged statement.

The main difference to your examples is that an "immutable OS" is in fact mutable, while none of your examples describe themselves with an adjective that is contradicting with their function/inner workings.

Flatpak is a pretty good name, because it makes software flat in the sense that it avoids having a (tall) dependency tree.

I print from my phone just fine

Ah yes, the immutable OS, except for all of the various mutable parts.

We should totally not call it anything less confusing.

How could you install anything or change any setting if it "doesn't change" ?