Dopamine reward loops, good content and a reasonable UX.
If you gave a good, detailed answer with sources, you got rewarded for your effort with upvotes more than a low effort answer. This kind of appreciation motivated quality content generators to generate more content.
as usercount grew to a certain threshold, you basically got users from all sorts of domains generating quality content covering pretty much all topics
while official UX was horrible and 3rd party apps were needed, the basic system of sorting and indendation of answers allowed for long, detailed discussions which could be navigated and followed effortlessly.
Highly customized/optimized Linux images certainly are one use case of gentoo.
if it’s cool you might be willing to put up with the drawbacks
The "cool factor" is a significant point. My gentoo laptop (which I update rarely besides browser/security updates) boots in under 3 seconds to graphical login :-)
Compiling can be done by a the cluster
Actually most compiling is pretty quick on modern systems (compile in DDR4 ramdisk, nvme, fast CPU etc.)
I'd say, most stuff compiles as quickly as installing a binary nowadays.
It's the huge stuff that's annoying: webkit, rust, Qt, boost, firefox/chromium etc.
But one can skip updates easily or use precompiled binary packages that are provided for big stuff.
Pi4 is perfectly doable. But Pi Zero won't be a lot of fun.
Real benefit. For average users it's debatable but if you want to exclude certain components or have complex dependencies "just work" without tons of docker images or need bleeding edge performance by tweaking everything, I don't see any other choice.
Also if you need to seamlessly integrate new projects that don't provide packages, writing a live ebuild is straight forward and will keep updated from a regular git repo just like any other package.
Want to compile certain stuff with clang and the rest with gcc? Or use libressl instead of openssl? Stuff like that? No problem. Just be aware that you might need to file bug reports if you do exotic stuff because gentoo won't prevent you from doing stuff nobody did before.
And installing gentoo by going through the install manual step-by-step, is certainly priceless for diving into linux under the hood. It's a bit like a LFS but without the hassle.
I understand all of it. I just point out your dilemma. Your whining will get you nowhere.
You're a user not willing to read manuals completely but expect stuff to work at your fingertips. You'll get older and as stuff keeps changing, you'll find it harder and harder to catch on. You'll spend a shitload of money to people promising the ease of good old patterns you are used to but you just can't keep up with folks using more efficient techniques.
And well, FOSS just doesn't seem to be your thing. Obviously, you need to unload your frustration on some service hotline worker... or random people online.
I was talking about all *nix-typical principles. e.g. that everything should integrate into batched jobs. Modularity. Human readable error messages. Transparent logging. Integrated software repositories & version control, man pages. file permissions & user groups. etc.
Stuff that seems strange and unnecessary complex for new users, who don't know how to use stuff.
no, you're talking from a patreon perspective. You have no clue of the subject and you simply demand people serving stuff the way you think is best. Also you don't care why things are the way they are.
Basically a Karen User.
The vast majority of people don't know - or care - how their car works. They just know it has to start.
Exactly. The vast majority buys a $50.000 car and only use 2% of it's features. And if the manufacturer starts to charge for a feature you like or decides to spy on you, there's nothing you can do about it.
Which principle exactly? Early motif UIs still are in use in a lot of nieche applications.
Not saying UI design is easy or FOSS apps shine with excellent GUIs, but they work for their users and complaining doesn't help.
My point is: Either improve the UI or pay someone to improve it. Or at least make a suggestion to the devs but don't blame linux people for not providing a free product perfectly adapted to your personal habits.
This is the problem with the Linux crowd. You guys write software to write software and not because you are a user of that software.
It's a problem you have since your OS pretends that Software (or a Computer in general) isn't complex.
Linux crowds use *NIX principles that are >50 years old and didn't change a lot, because they work. Not because some software devs circlejerk or want to annoy you.
That's what I thought, hence I mentioned the bowl of water. Which was heated with wood or coal which had to be carried manually... in buckets... Imagine that :-)
Yearly. They look at slices generated by compressed layers of snowfall. Thick layer = cold year. They look at more stuff but that's roughly how it works.
edit: not sure why you're downvoted. It's a good question.
Of course I do and I expect my employees to report such incidents to IT. Such documents are common attack vectors.
In my experience, customers are not aware of failing interoperability or possible security threats and often grateful for such hints.
There's a reason why libreoffice (and I guess other office suits aswell), evince or antivirus show a big, fat warning when opening such documents.
Surely there are cases were macros are useful or necessary, but if they have to leave the company, you're doing it wrong.
It's opensource, just add it yourself or open an issue asking for addition.
If the codes aren't available on the web already, you basically have to setup lirc, record the code for every key of your remote and give the output to the project to have them added.
How is it stupid? It's true and not even contradicting OPs experience.