Not just Linux… 99% of the time you see something weird in the computing world, the reason is going to be “because history.”
Not just Linux… 99% of the time you see something weird in the computing world, the reason is going to be “because history.”
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.
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!
Assuming the entire US court system isn’t in the corporate pocket
I love your optimism
Probably not wrong. But it’s a double edged sword, if Tachiyomi wasn’t hosted on Github it’s likely that it wouldn’t have gotten this far.
It’s harder for other devs to discover your project when you use the other Git forges (e.g. Gitlab).
Tell me you haven’t seen people adamantly defending IPv4 without telling me so…
Good luck getting a block of IP addresses from your regional internet registry for this community ISP… IP address exhaustion is just that, no more addresses. That’s why we are sharing them.
We do have a solution and it’s called IPv6, but its deployment is still not as widespread as people would like to be. If I self-host my website on IPv6, a lot of people from Europe would still be unable to access it.
That’s pretty much just pushing the centralization from Google, AWS etc to the hosting services.
It’s pretty difficult nowadays to self-host websites when everyone and their nanny shares a single public IP address (IPv4 address exhaustion is real, everyone!) unless you purchase a hosting service.
It’s not a fork of wlroots. wlroots is a library to assist developers in creating Wayland compositors.
Not nearly as performant as either Java or COBOL.
Overall everyone will use less data when there’s a data cap, I found.
My ISP implemented data caps back then too (thankfully it’s all removed now, but 60GB was really bonkers!) and I just find it fascinating how much traffic I generate nowadays, when I don’t have to care how much data I have left this month.
Anyways, data caps shouldn’t be relevant anymore in 2023 when absolutely everything can handle gigabits and more. It’s interesting how American ISPs still implement them.
I sorta understand why data caps were implemented in the past. Some people hosted servers on their home connection, and their total internet traffic in a week would far exceed that of a normal user’s. Data caps were meant to force people to be conservative on their internet usage so this would not happen.
But come on now, it’s 2023. If your internet infrastructure could not handle that amount of traffic, you are a laughing stock of ISPs.
I feel like there’s already a significant downgrade in content quality since the blackout.
The subs I frequent seem… dead. Posts would regularly get 200+ karma before the blackout, but now even the top ones get only 100+, the rest hover around single digits. Mostly shallow discussions / simple topics that I simply don’t have the urge to engage in.
And those subs that don’t seem “dead”, are being filled by bots (obvious to see because they are very, very enthusiastic about everything lol)…
Ah, I misunderstood your original comment, oops! But yes, IPv6 packets are routed just like IPv4 ones, just without the NAT’ing process i.e. the packet remains untouched the entire trip.
IPv6 has both NAT66 and NPTv6. (Note that NPTv6 was once called NAT66 too, but I am referring to the “stateful, one-to-many” NAT66 here. Yeah, it’s confusing.) NAT66 is more like the traditional stateful NAT that all of us know and understand.
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).