Or I'm commenting on the actual article this was attached to.

Good lord.

Anyone that thinks you're going to high-side yourself by having a moving flywheel interacting with a clutch either hasn't rode a motorcycle in their life, or hasn't been doing it very long.

Hint: you can use the rotational mass of the engine to keep you upright at stop signs, and then slip the clutch to start moving again with the RPMs you already are turning. This is very normal for experienced riders to do if they don't think they'll be stopped very long (i.e. stop sign with right turn)

I want to know if they can replicate a "hover" that you can do with an ICE + clutch, where you can come up to a stop sign, go full clutch and give enough throttle to turn the engine at about 1500 RPM to create gyroscope balance effect and keep you upright, allowing you to ease out the clutch for a takeoff quickly after seeing it's safe to do so.

That would be a trick.

The plural of "anecdote" is not "data."

We're working with Ford's stated sales numbers here, not surveying people for how many of a particular car they see.

Also remember that you can recharge the truck at any campground you might be parking the trailer at. A lot of posts I've seen have a TT30 on them as well as a NEMA 14-50 and they both work because one is 120V@30A and the other is 240V@40A.

Plug your trailer and your tow vehicle in at the same time.

It's also officially abandoned by the company that created that protocol and connector, which I believe was the point.

I'm sorry, do you not understand the correlation between the charging connector in use, and availability of charging infrastructure?

Why do people think that embedded systems that don't get kernel updates will stop working because kernel maintainers are not supporting 40 year old hardware for next year's kernel release?

It's not like every previous kernel winks out of existence the instant a new version is published. They can go right on running Linux 6.x on their 40 year old hardware forever.

I want the MRI to run on whatever allows it to generate a valid imaging. I don't give two fucks if it runs a 10 year old kernel, or a 10 day old kernel.

There are ways to keep things secure through network sequestration if you have an embedded system that isn't getting updates - this isn't a new concept, and we've been doing that since embedded systems started existing.

There were problems if you didn't know what to look for, and in the early days of the Internet, people didn't know what to look for.

Namely: crap motherboards that would overclock the PCI or AGP busses, crap motherboards that would share interrupts between PCI and AGP slots, and due to the presence of ISA bus devices, could not enter the world of PCI bus mastery and edge-level triggered interrupts.

Also, there were problems with Windows 95 that would cause random bluescreens and shit if you didn't load some shim driver you had no idea you needed.

If you had the knowledge you needed and the drivers and patches available to make it work right, they were great. But there was a lot of people out there that wanted to save money over Intel, and didn't know what they were buying themselves into.

Is there some purge of all previous versions of the kernel underway from every system in existence, or can you continue to run the version you're running today, forever?

More than that - are there any improvements happening to 32-bit Linux that would have any positive effect on a 25-year old system?

At some point you just surround it in bricks and let it go as long as it's gonna go.

To be fair, the 3Dfx Voodoo / Voodoo2 and Voodoo Banshee were the best you could get at the time. Then they decided to compete with their customers by releasing the Voodoo3 series, and literally every one of their customers started licensing Nvidia Riva TNT / TNT2.

3Dfx was a dead company 2 years later, with Nvidia buying the asset portfolio, and Nvidia SLI was born.

Transmeta was purchased by Apple, and that's where the Apple A-series chips came from.

The K5 wasn't bad.

Cyrix was shit. The only way they could compete was to overclock the bus, which fucked up your PCI and AGP slot timings because everything was a multiple of the main system bus. Instead of running it at 66Mhz they decided that 75 gets them where they want on the CPU, with their customers not realizing that they are running the PCI bus at 38Mhz instead of 33; and any AGP slot at 75 instead of 66, and how that might just screw up a GPU that was designed to run at peak performance with a standard main bus clock.

And, of course, when you point this out to some cheap asshole that bought the Cyrix and doesn't understand why his GPU drivers keep crashing, they bitch about having to "underclock" their system in order to put literally every other component in the system into the spec it was designed for.

Cyrix deserved to have been rapidly ushered out of the market for that bullshit.