If you squint your eyes just enough, insurance is like gambling... You are betting that something is going to happen to you, the insurance company is betting against that. The insurance company can improve their chances by adding conditions to that something.
orangeboats
joined 1 year ago
For many systems out there, /bin and /lib are no longer a thing. Instead, they are just a link to /usr/bin and /usr/lib. And for some systems even /sbin has been merged with /bin (in turn linked to /usr/bin).
Not just Linux... 99% of the time you see something weird in the computing world, the reason is going to be "because history."
Gen Z's are well aware of traditional phones. Smartphones were not really that ubiquitous (up until 2010(ish)), and by that time Gen Alphas were already born.
The C developers are the ones with the ageist mindset.
The Rust developers certainly are not the ones raising the point "C has always worked, so why should we use another language?" which ignores the objective advantages of Rust and is solely leaning on C being the older language.
They very rarely have memory and threading issues
It's always the "rarely" that gets you. A program that doesn't crash is awesome, a program that crashes consistently is easy to debug (and most likely would be caught during development anyway), but a program that crashes only once a week? Wooo boy.
People vastly underestimate the value Rust brings by ensuring the same class of bugs will never happen.
Ah you got my comment wrong! I didn't mean to suggest Gecko is closed source. I just wanted another web engine that is also open source.
Servo was an experimental ground for Mozilla in some ways (like testing out a new CSS engine and porting it back to Gecko if it works). So it's quite normal for people to be unaware of it, it was not meant for the public.
But later on it was abandoned by Mozilla and stuck in a limbo, until it got picked up by the Linux Foundation. Now it's a standalone project and I wish them well. We really need a new FOSS web engine.
It really depends.
If I know I will never open the file in the terminal or batch process it in someways, I will name it using Common Case: "Cool Filename.odt".
Anything besides that, snake case. Preferably prefixed with current date: "20240901_cool_filename"
People back then just grossly underestimated how big computing was going to be.
The human brain is not built to predict exponential growths!
One of the issues at hand is that X11, the predecessor of Wayland, does not have a standardized way to tell applications what scale they should use. Applications on X11 get the scale from environment variables (completely bypassing X11), or from Xft.dpi, or by providing in-application settings, or they guess it using some unorthodox means, or simply don't scale at all. It's a huge mess overall.
It is one of the more-or-less fundamentally unfixable parts of the protocol, since it wants everything to be on the same coordinate space (i.e. 1 pixel is 1 pixel everywhere, which is... quite unsuitable for modern systems.)
Wayland does operate like how you say it and applications supporting Wayland will work properly in HiDPI environments.
However a lot of people and applications are still on X11 due to various reasons.
view more: next ›
[deleted]