Since he bought Twitter, Tesla is down ~30%. The other automakers are about even. He's spending all his time on Twitter, while Tesla is on a backburner (with increasing numbers of recalls, WAY up compared to a couple of years ago). And no one I know would now want to work there. He'd be lucky if his $44B investment was now worth even half that if he tried to sell it (maybe far less than that).

By his own narrative, it wasn't creating PowerShell specifically that got him demoted. It was doing "unassigned" work during work hours.

He details that it was specifically that Microsoft did/does not have the 80/20 type thing some competitors have, where you get some time to free range random concepts and ideas, so some pissy middle manager got mad that he wasn't going through the whole project approval (you know, the let everyone comment on the color of the shed stage) and he got demerits.

*What is YOUR source for this. Do you even have one?*

THE PAPER THAT WAS SUBMITTED. They are very open about the *incredibly* narrow known threat model (basically ASLR pointer obscuring *in the same process*), albeit -- as all papers do -- opining that maybe there is something worse that could be done. These sorts of security papers come out by the dozen per year, and generally no, there isn't any further risk, and the latent risk is negligible to irrelevant.

To be clear, when security researchers are pitching a novel vulnerability, the foundation of their claim is a proof of concept, because the chasm between "well it could...." and the actual can be enormous. No proof of concept. Not even a vague inclination of the knowledge of how to make a proof of concept. And this issue has been very widely disseminated, every hacker group pounding on Augury -- theoretically it is trivial to exploit on an array of pointers -- and no one else has a proof of concept yet. Weird, right?

ROFL. Classic Slashdot. Good god.

"No bias there at all."

Because I have an M1 Mac I have a "bias"? Yeah, not really. I'm typing this on an Intel box. I have servers on AMD, Graviton 2, among many others. That's a modern life.

"Sources are people in the security industry in which I work."

ROFL. Yeah, no you don't. You are claiming ridiculous things.

These sorts of "you know it *could* hypothetically be exploited" (in a profoundly narrow sense) security papers come up by the dozens per month. The overwhelming majority have no real impact whatsoever. This one is particularly spurious.

The "amateur hour" bit in your comment was particularly hilarious, and betrayed that you're just some guy saying dumb stuff.

What source says it's "impossible to mitigate this"? Do you have even one?

Because the notion is preposterous. Not only is this largely a theoretical attack (I'm being generous by not calling it a fully theoretical attack), with extremely little real world consequences, mitigations are *trivial* if it were something real.

"I really want Arm on the workstation and server to succeed."

You seem to know literally nothing about security or chip design, and decided to post some tosser, laugahble anti-Apple screed. Me, I'll keep using my M1 Mac, and have been using ARM on the server for half a decade now. Hurrr.

They're using a payment processor. Meaning a third-party is converting cryptocoins to real money, and the real money is transmitted to Newegg.

Bitpay added dogecoin a month ago, so now they can milk this with every retailer that has Bitpay as an option.

This is a good point. That situation already exists for night workers, but would be a pain if extended to the general population. This would affect Alaska, Hawaii, Pacific islands, the eastern half of Australia, Japan, North and South Korea, parts of Indonesia, and northeastern Russia.

Why do we need for working hours to be (more or less) from 0800 to 1700? What difference does it make if working hours in a region or a state are more or less between hour zero and 0900?

" People usually have lunch around noon, so that means everywhere you go, you'll have to learn when lunch time is."

When the sun is highest in the sky is generally when people have lunch. Or, once you know that lunch is generally around the hours of 0300-0400, I don't think that would be difficult to remember.

"If I want to call someone in India from the US, I can check the time in their timezone and if it's something like 3AM, that's not a good time to setup a call, but if I don't have timezones, I know that 16:00 UTC works for me, but is that a good time for people in India?"

Finding out what time would be convenient to hold a call is something you generally do by negotating with the other party. If you're using global UTC, you can at least talk about the time in absolute terms, rather than having to do arithmetic to figure out how local time relates to remote time.

"Last time I checked the public statistics, it's actually already doing that."

Tesla's stats on this are incredibly deceptive.

Firstly, the only place where Tesla drivers engage autopilot is on highways. The accident rate on highways is dramatically lower than city streets and aren't separated out, yet Tesla compares their autopilot numbers of that overall number. Highway driving is the baby first steps of self driving.

Secondly, Tesla drivers already are significantly less likely to be in accidents minus any of the aids. 1 accident per 1.82 million miles for Tesla drivers, versus 1 accident per 479,000 miles for the average vehicle. Again, this is with zero of the assists or safety aids in the Tesla. This is courtesy, presumably, of newer cars (older vehicles are in far more accidents) and perhaps a more enthusiast owner who is more attuned to the world.

Elon Musk has been pitching full self driving for years, increasingly trying to get buyers to pay for a product they aren't actually getting. And I'm sure Elon is looking at the progress and thinking "wow, we're at 95%...only the last little bit left", but in realms like this that last 5% takes 5000% of the time and effort.

Ah, the death certificate claim. This is an argument presented by two types of people-

a) Liars and people who just want to see the world burn
b) The gullible who have been misled by a) and just don't realize it

The CDC gets death certificates often with MONTHS of delay. If you track their counts in real time, past periods will continually percolate up as death certificates from all causes eventually make their way to the CDC.

https://www.cdc.gov/nchs/data/...

The CDC gets COVID-19 data very rapidly because it's a pandemic. They get data on every other cause of death much more slowly.

It's remarkable how virtually any topic gets exploited and misdirected by people who just like trolling the world.

Currently the deaths / known cases (positive tests) = 5% CFR

If 10x more people have had COVID-19 than known (e.g. 25 million rather than 2.5 million), that would make the CFR 0.5%. Which would still be terrible, as an aside.

If we assumed 100X more people had it than known, that would still be a CFR of 0.05%, which would still be quite bad for a highly viral disease. But given the spreading patterns of the virus, that is clearly and obviously not even remotely possible.

The current CFR in the US is >5%. 10x less deadly (0.5% CFR) for a super-virulent respiratory is still incredibly bad.

I mean...are the deniers still doing the no biggie thing? Amazing.

Not really, friend. At this point it's clear discussion with a fanatic is futile.