GeForce Now is not Stadia.

Stadia was custom thing requiring development build for stadia.

GFN is just a VM with access to Nvidia hardware running Windows and using the standard Steam client (or Xbox for pc, epic store). When it first came out, literally every game on steam was available, though some weren't working right. GFN had to modify it to only allow certain steam games to appease devs who for some reason didnt approve.

Its not as low latency as local steam link, but as a dad/former gamer, its not so baggy that its the reason I get pwned, its still me.

I wouldn't do iRacing or CoD on it, but fortnite against kids is solid on a good internet connection.

The downside is the one game I really want to play on it doesn't use cloud saves, so its not seamless in that game (to be fair, my last save was close to 1gb in size :/

Congrats asswipes, Ive already canceled my YouTube.tv sub because I missed the last F1 race because of this bullshit.

Just canceled my Disney+ sub because I have to pay extra there to get ESPN to get F1 ...

FUCK YOU RICH ASSHOLES.

I'll just go outside instead, and enjoy my $180/month for other things.

I could give not 1 flying fuck why, you are both ridiculously profitable, fuck you greedy assholes. Both of you are trying to blame the other guy, yet profitable is not in anyway a problem you have.

I hope ya'll die the most painful death, you deserve it.

"If confronted with a gnome login gui, how do you make the system useful again?"

Alt-F1 (or whatever it is in Linux - I only use certified UNIX systems, which Linux will never be)

Or you know, build robust apps that don't have one cloud provider as a single point of failure.

This wasn't a root dns failure of TLD servers, so it wasn't by any means an unsolvable problem.

But that takes effort, and to be fair, if the company cared about reliability, they wouldn't be on AWS anyway. Not that AWS isn't generally reliable, its a great service for many things, but when you outsource everything to someone else because its hard - and don't understand that you're still actually responsible for the 'hard' parts - well thats on you and its why you should have done it yourself first.

The shit you outsource to AWS is actually the EASY part. Putting all that stuff together into a working architecture is and always has been the difficult part. Keeping rack servers running is a pretty well understood process at this point, its not hard to keep racks of running computers, it just takes people who know how to build your automation and understand that time is more expensive than cpu cycles.

It's reasonable when you consider they have to "support" those drives via their various support channels.

You put in a drive with incompatible firmware, then start asking for support because an issue with the firmware comes up, it directly costs them money.

Im not arguing the cost is valid, but if you've ever dealt with large commercial product support you would completely understand why its logical.

No you cant just refuse support to those people because
A. You will still contact them and waste resources to confirm an unsupported drive
B. Most states require vendors to honor warranty/support for modified products unless the vendor can PROVE the modification is the source of the problem.
C. Even after proof, some customers would continue to argue and add legal costs
D. Finally the customer will trash talk the vendor online and word of mouth, right or wrong ... costing the vendor even more money

Or they could just block your cheap drive and not have you as a customer and lose less money cause you're a tight wad.

You're not the customer they are interested in, you're a potential cost rather than profit.

Fun fact - I prefer just filling out that bland web form rather than trying to talk on the phone to someone or an AI.

That was one of the great things about the web, people didn't have to deal with that slow process anymore, you could just got fill out the form without talking and be done.

I DON'T WANT YOUR UPSELLING AGENT.

I haven't wanted it for the last 30 years, I don't want an AI powered one for the next 30 years

Turning them off and landing in an empty field or on the Hudson, or rolling off the end of the runway may be preferable to the plane burning itself up in flight. It's extremely unlikely it was entirely unforced error and the pilot/copilot did something malicious.

Obviously it wouldn't be preferable ever at this airport, but there is an assumption that the pilots arent actively trying to down the aircraft.

There are thousands if not millions of ways a pilot can actively sabotage the aircraft. They are the one group on the plane that is trusted not to. It's nearly impossible to prevent it without removing them entirely from the plane. And all the passengers too ...

Sometimes, not very often ... the pilot is a problem.

No.

No breaks or excuses.

You cant bolt security on after the fact. The entire protocol and application MUST take security into account from the start.

Trying to add security on after the fact is how we ended up with ActiveX on web pages and VBA in documents and NEVER WERE ABLE TO MAKE IT SECURE.

To make web browsers secure, they pretty much all started over (website, firefox) because trying to strap it on was impossible.

You dont typically use avgas in fuel trucks at large airports like this as most ICE engines are on small aircraft that dont fly in large airports for all sorts of reasons.

You dont fly your little Cessna single engine into an airport with 787s landing or taking off. Thats a nightmare/disaster in the works. The Cessna would be like a leaf in a hurricane.

They drive to a gas pump AWAY from the jet wash that will destroy them.

Larger prop driven aircraft are powered by turboprop engines - they use jet fuel as well, not areas.

It's not impossible of course, but pretty unlikely.

Nope, you can absolutely roll off the end of the runway at any speed except full stop. Take off is always a choice.

The landing in the other hand is governed by physics, mostly gravity. If you dont leave orbit, landing is mandatory, its only a question of when and what it looks like. The aircraft will be on the ground eventually.

It may be a good landing, it may be a fiery crash, but you absolutely are going to land.

Well, the Xbox launcher is a slow bloated POS that always complains its not up to date so you cant play until you update.

I will buy games on steam before installing the gameplay free version in the Xbox app JUST because the launcher is such a PoS. Laggy and bloated.

JS developers are typically less experienced, less qualified developers who tend not to know all the ways you can be exploited by software from a 3rd party.

A very simple example of this is that almost all who use NPM have their builds configured to use the very latest version of each dependency, which means they have no idea what code is actually used each build.

This practice is encouraged by the community, and it takes extra effort to pin versions. This is pretty basic engineering stupidity, but its the NPM way.

Then th ey usually build their app each time it starts. It's not recompile, it goes and pulls down the dependency, whatever the latest version is ... each time it runs.

So even if it was built and 'released' with version X of its dependency, it could restart with X.1, or same version number, but hacked version upstream ( this has literally happened multiple times over the years ) because there is no validation.

Then, the "language" is so broken and non-standard there are dependencies for some silly shit, like parsing tabs correctly, and so each dependency you pull in, it may have a dependency tree of another hundred things.

The end result is pulling in even though basic things, you pull in hundreds of other dependencies. All of them set to then pull the latest version of child dependencies without any sort of validation.

NPM is used by a bunch of immature developers who lack the experience to understand that pretty much everything they consider a feature of the language is in fact a flaw that other languages/ecosystems dont allow for or highly discourage.

JS/NODE/NPM are designed around and encourage anti-patterns the rest of us stopped doing years ago.

Well, as typical with a JS fanboy, you need to get your facts straight. This is why the rest of us dont take you seriously.

Quantum computing is very very very rarely faster than classical computing today. It has NO practical value and its big "wins" have been simulated in most cases, about what they'll be able to do eventually after working out more bugs. It is currently 100% useless beyond research.

But this is exactly the kind of uneducated decisions that come from JS developers.

NPM is just one, but not the only example required to understand why your a dumbass to use JS for anything. That level of craptastic pervades the entire JS ecosystem. Im sure you think NPM is wonderful.

Meh, I too call bullshit on your claims.

45 years? That puts you in a pretty small group of people. All of which have enough experience to know why those languages are ones you run away from.

OR your last 45 years of "programming" experience has been at the Excel macro/VBA level, in which case you arent qualified to be at the big boys table either.

I'd like to believe you, but my 25 years of building complex systems has seen how people trying to use kiddie languages for anything beyond a basic ops script ends badly and takes years to unwind.

If you've been using those languages for serious work over the last 45 years, I'm the guy who has to come in and replace your jumbled pile of crap script after you get fired.

The fact that you dont understand that those aren't appropriate for most things is a strong reflection on your lack of engineering prowess and actual experience. Use the right tool for the job, and dont build yourself into a hole.

You arent magically different than every other low grade Javascript dev, you just dont realize it.

Linus doesn't brow beat anyone.

He just doesn't put up with arrogant and ignorant snowflake developers who think they are gods gift to the world.

He doesn't care about your little feelings, He cares about code quality. And every single time you saw Linus go off on someone- it was after the person pushed back like they were king shit and acted like Linus wasn't the kernel maintainer for 30 years and that their 6 month journey into writing Linux device drivers for their unheard of project for the first time makes them Billy Bad Ass know it all.

Linus is a douche to douchebags, rarely if ever does he go off on someone that doesn't 100% deserve it.

Stop crying