cakeistheanswer

That's industry talking!

"Net Neutrality policies are a national standard by which we ensure that broadband internet service is treated as an essential service. It prohibits internet service providers from blocking, throttling, or engaging in paid prioritization of lawful content. "

So if they block or throttle you when you hit a cap...

Seriously this is probably lost to time, but we were setting up for this battle in the DSLAM era because every provider over sold their bandwidth. It lays pretty much untested because nobody was worried about pennies in a gold rush and that's about the time fiber backbone started to make the problem irrelevant again.

With the caveat I'm technical not legal... Its largely kept data caps off domestic lines, but not entirely. Net neutrality has had a couple taking points and its a long fight at the FCC that's gotten weirder by the decade.

Net neutral meant Microsoft couldn't make the MSN dial up network prefer windows network traffic, over the years companies got smart and just opted to pay for peering instead of running the low profit access tunnel.

Google even drops boxes to cache stuff at tiny ISPs/WISPs, but doesn't deprioritize traffic to other end points.

There have been intermittent swings at labeling this the pay to play it is, but since the investment isn't spilling out of public works there's a decent case this is the fastest you could give out access to everyone.

Source: am former network closet guy who racked google cache devices, installed WISP equipment, legal layman.

You're just the latest member of a long and storied fraternity of the best worst operating system architecture.

https://web.mit.edu/~simsong/www/ugh.pdf

One of us...

Its the same problem as standardized Unix systems in the 90s. There's more ideas on how to implement hardware than there are hands to integrate driver software.

When it comes together it'll be because we either make the manufacturers warp around something like POSIX, or provide a common target on phones like the steam deck.

Otherwise every hardware generation will get the undescribable misery of supporting the last one, from the one they're on, while writing the next one. The problem tends to compound.

K, teachable moment maybe.

How complicated do you think a web browser is? Out of the box there is support for 30 years of web and file systems, support for socket types that will never be commissioned again and a pipeline to every native media format.

It's complicated, it's essentially an OS. with perfect backward compatability. (Mostly)

I have an increasing amount of bile for the Mozilla Corp, but if you're on Lemmy you probably noticed corporations don't make the best decisions for you... My question is how many of the options do you see in about:config do you think chrome and safari don't show you?

Mostly to their benefit I'd add, except if they set them maliciously you'll never know.

Zypper is very solid, and I can't say anything bad about suse, but it was 15 years ago I was strictly working off of VMs while the company I was working at advertised support. If there wasn't the Debian social contract I think a lot more projects would have forked it.

They had a better reputation down the company chain than redhat, but the orders always seemed to go to IBM.

Gentoo is an open book test on compile flags at all times.

All you have to know is all your system variables, compiler flags that exactly two distros use, init, daemons and hardware and it's great!

On some level I admire the people who know that stuff, but I've had my OS compiled for me for a long time. I loved portage once I figured out how to use it though.

I might add some version of Suse (open or enterprise) to that list though. Last I checked there were a bunch of shops kicking the tires as cent os shut off. Didn't keep up on how that turned out.

I like fuzzel, had a few issues with dpi scaling on wofi out of the box.

Easy to integrate clipboard/window select/dmenu binds and a way to distinguish indexed entries from straight text was a plus.

Honestly unless you're going out of the box to something new (Walker and anyrun caught my eye) dmenu has had everything I needed for years... But I don't want to set it up again. Not again.

It gets better!

I took a deep dive on fonts my first week(they were fuzzy). I now know a lot about things I almost never use or set, but every win will give you a piece of the whole thing.

Eventually you figure out the "core" (that stays the same everywhere and you don't have to do near as much work to tack on the extras.

It's big and complicated because you're replacing windows with the hundred individual things windows does, each were made by someone else, in some cases decades apart.

Somehow it all works pretty well, but we stand on the shoulders of some giants.

Edit: I also don't like manjaro, but someone here has covered why better than I would have. I run endeavouros and would recommend if you want arch with less config, but it is arch. Mint is where I have been pointing people to start recently.

That's probably closer today than it was then. The added complication being that client is probably not thin enough for them to return to mainframe model which would be vastly easier to monetize.

Besides we got WSL out of the bargain, so at least inter op isn't a reverse engineering job. Its poetically the reason linux ended up killing the last few win sever shops I knew. Why bother running win sever x just to run apache under linux. Why bother with hyper v when you can pull a whole docker image.

If the fortune 500 execs are sold on microsoft ita mostly as a complicated contactual absolution of cyber security blame.

I know about 3 people on earth that ever ran it in anything approaching production. Two of them still found a way to use the acme editor til LSPs took over, one is still at it.

It remains a pretty cool project you can still find people maintaining the bones of it. I think the core utils are ported and in the arch repo.

I use the Debian social contract as an example of the an unmitigated good in open source.

That doesn't mean the org always live up to it, but that's partially why there are battles for things like representation inside. I wouldn't extend the benefit of the doubt to canonical, and I prefer rolling as opposed to security ported updates on my own hardware, but they made what you see possible on the internet in large part because people came together to make a free platform.

The orgs dogmas look like product of a bygone age to be, and changes to environment in software is probably as hostile to their approach as ever. I'm amazed they're not more dysfunctional just from the outside looking, it's a rock solid implementation.