When things get dire, the fast and high bandwidth Internet we know will be gone, but a form of slow, intermittent Internet will probably be around; still technically an Internet.

The E stood for Elimination.

Part of me wonders if they sell your driving telemetry to your insurance company, and if those companies pay out more for data on worse offenders. If so, they’re just letting you tie your own increased insurance rate noose by providing that option, for their own financial gain.

Oh, so that’s why Google is killing sideloading.

Then again, I could have accomplished the same thing by knocking off work for the day and going to the driving range.

Hey, look at the bright side, as long as you were chained to your desk instead, that’s all that matters.

uninformed for skeptical

Perhaps one begets the other.

The article is not fishy, you are just uninformed. They are powering the datacenter with turbines fueled by natural gas. You are right about the datacenter though, it’s beyond fishy, into crime territory. To top it all off, they have approval to run only a handful of turbines (after not even seeking approval in the first place, i.e. running them illegally), but they are running a ton of them.

*looks around* That’s a pretty big if.

I feel there’s a certain sad irony about the domain on that link.

I am having flashbacks to the scene in Idiocracy where the doctor is talking about his wife.

Autopilot hasn’t received any updates for years.

Like I said, demonstrates neglect.

If Kleenex were the only ones doing facial tissue, then this could be, “toilet paper vs. Kleenex”, and you’d be wondering “why isn’t this Charmin vs Kleenex?” while Charmin happened to be the TP brand they chose because they had access to it.

Tesla is the only one doing camera-only self driving, so there’s no point in delineating the two. Lidar you can expect from any other brand, so it’s a token choice in this instance, especially for an engineering entertainment video.

Autopilot is just adaptive cruise control that keeps the car in lane.

Anyone who watches the video in question knows this statement is misleading. Autopilot also stops when it detects an obstacle in the way (well, it’s supposed to, but the video demonstrates otherwise). Furthermore, decades old adaptive cruise from other brands will stop too because even they have classic radar or laser range-finding.

If even the most basic go no-go + steer operation based on computer vision can’t detect and stop before obstacles, why trust an even more complicated solution? If they don’t back-port some apparent detection upgrade from fsd to the basic case, that demonstrates even further neglect anyway.

The whole point that everyone is dancing around is that Tesla gambled that cheaping out by using only cameras would be fine, but it cannot even match decades-old technology for the basic case.

Did they test it against decades old adaptive cruise? No, that’s been solved, but they did test it against that technology’s next generation, and it ran circles around vision not backed by a human brain.

Sorry you are getting downvoted for being one of today’s 10,000

Wow, thanks for this. That is very helpful context. And thanks for your original post too, or I’d never have asked.

Basically, they aren’t hurting yet.

Exactly. You could reduce their wealth by a factor of 1000, and they would still have more than 90% of people. They will never be genuinely hurt by losses. Not like 99% of people would be.

The chart shouldn’t make anyone happy. The true horror of it should be realized; in reality it’s an accounting of how much they’re “spending” money to make money. They will continue to make more. The scales here are unfathomable to most people.

It’s borderline misinformation to not include their total wealth for context.

it is detectable […] server side, if you download the script [vs] pipe it into a shell

I presume you mean if you download the script in a browser, vs using curl to retrieve it, where presumably you are piping it to a shell. Because yeah, the user agent is going to reveal which tool downloaded it, of course. You can use curl to simply retrieve the file without executing it though.

Or are you suggesting that curl makes something different in its request to the server for the file, depending on whether it is saving the file to disk vs streaming it to a pipe?

Match owns all the patents

That’s great, thanks! I really appreciate the detailed response and the links.

The methodology IS cloud native

Ok great. Is it also fair to say that cloud native is the methodology? Or is cloud native a higher order concept that the methodology can fall into? I.e. rock is music, but music is not rock.

Dude, thank you for this. IMO reducing that down to simply “cloud native” is doing a disservice to how absolutely cool that methodology is.

I loved RancherOS in the server space, and always wished there could be a desktop version of it, but I realize that the isolation of docker on docker would be very difficult to deal with for desktop applications. From your description, I feel like Bazzite has done the next best thing.

If I may frame things in RancherOS terms and perspective briefly, given your description of what’s going on with Bazzite, the System Docker container image is being built in the cloud every day, and you could pull it down, reboot, and have the latest version of the OS running. The difference, I am gathering from context, is that while RancherOS “boots” the system image in docker, Bazzite simply abandons RancherOS’s hypervisor-esq system docker layer, and does something like simply mount the image layers at boot time (seeing as how the kernel is contained within the image), and boots the kernel and surrounding OS from that volume. The image is simultaneously a container volume and a bare metal volume. In the cloud, it’s a container volume for purposes of builds and updates, which greatly simplifies a bunch of things. Locally, the image is a bootable volume that is mounted and executed on bare metal. Delivery of updates is literally the equivalent of “docker pull” and a boot loader that can understand the local image registry, mount the image layer volumes appropriately, and then boot the kernel from there.

Do I have this roughly correct?