snoshy
You have completely ignored the fact that this is literally the opposite of what has (likely) happened in this case, and is provably almost the norm in countless other cases like this. There was an opportunity to make things right by the leadership. They did not choose to do so. At every step along the way.
Even assuming that these were honest mistakes (I don't believe so), the actions taken by leadership in most of these situations tend to wring the complainant out of the system. If there's a "free market" way to resolve these problems, this certainly ain't it, which calls for regulations. If those regulations aren't strong enough to coerce the intended result (if you find out one of your employees acted in this manner, immediately contact law enforcement and let them figure it out, otherwise you're in trouble as well), then you are actively encouraging an extrajudicial mechanism for resolving these matters. Specifically, you're encouraging civil remedies vs. criminal ones.
Failure to report isn't the problem here. It's that the failure to report has no consequences on people with adequate power, who get to create their own kangaroo court of dispute and certainly resolve cases to their own benefit.
Before 2000, we had software running our systems, yes. But it was not as distributed, and not as ubiquitous, and not as deeply ingrained into human culture as it is today. This proliferation will obviously continue past today, and while hardware and low-level OS/software mitigations (as well as a herculean effort to clean up the mess) will make up the gap, it's not hard to see that this is likely to be much more impactful upon failure because of the "embeddedness" of these systems.
A box that has just been doing its thing for 40-50-60 years and all of a sudden fails, is likely to be more impactful than one that was 20-30 years old even.
Edit to add: if the authorship of the submitters is as above reproach as we are led to assume, why can that not be the case for the NIST decision panel itself?
Edit 2: answered already elsewhere: https://news.ycombinator.com/item?id=31993896
I appreciate the point about trust in the authorship of those presenting these algorithms, and I personally do accept it, but there's a lack of trust broadly (in the very community that these standards are intended for) in the process that your comments don't account for in this instance.
I have no doubt about Elon's intentions about what he plans to fix about Twitter the product, but I certainly don't expect things to go smoothly with wrangling Twitter the organization to actually achieve those results.
Tesla and SpaceX were built from the ground up with his personal principles in mind, and I think it will be quite the roller coaster for him to bring in the same sense of passion, discipline, and efficiency to Twitter. Twitter's inability to address many of its own longstanding issues is surely caused by a lack of will to do so. Turning around this ship will be no easy feat.
About 15 years ago, while working on Windows at Microsoft, a test machine sitting at my desk hit a kernel panic (BSOD). As was standard working on the test team, the machine was already setup for kernel debugging, and so I set out to debug it a bit in order to file a decent bug report.
Hours later, I couldn't make sense of it (I wasn't super experienced at this point). A few of the nearby devs couldn't either, and a small troop of us curious enough about the puzzler eventually escalated to the resident wizard, Raymond Chen[1]. Within 15 minutes of checking our work and poking at the machine, he traced the root cause down to a bit flip.
Ray's condition indeed. :)
I highly doubt it's gonna do anything for call systems in general though. They've burned enough faith to last a long time.
I'd wager there's a rather large number of folks like GP intending to minimize the effort required to do drone-ish tasks rather than eliminate them. I don't deny that it's only a logical next step to eliminate them entirely, but that seems a step too far for social conventions. After all, culture defies logic rather often.
Where did you see this? Best I can tell, 4 new models (Cybertruck, Roadster, Semi, Unannounced) are in development but only one more gigafactory (TBD) is in the works. Perhaps you misread things?
Agree though, astounding rate of growth at this scale.
Code should be written to be understood by humans first and foremost. The person who can understand such deliberate garbage clearly and explain it well to those who don't understand, well, those people are the perfect human debuggers, in my opinion.
Why not treat the exception as the exception? Appliances might consume disproportionately more power, but they're much more static compared to the variety of devices frequently plugged in and out of a home's sockets, most of which have to lug around an inefficient rectifier with them.
If solar and local generation are thrown in the mix, they bypass the converter and directly power the home circuit.
Why wouldn't this be more globally optimal?
edit: derped the converter
[1] https://forum.nasaspaceflight.com/index.php?action=dlattach;... [2] https://twitter.com/TerminalCount/status/1367261799293272068
Given these two limitations, Starship currently carries very little fuel. Think of it like a mostly empty soda can with a few sips sloshing about the bottom. Adding 3 Raptor engines to such a tank makes them way too powerful to run at 100% thrust the whole time.
On the launchpad, all 3 Raptors start off at full thrust until well clear of the pad. At that point, one engine at a time starts throttling down gradually, so as not to go supersonic or exceed the 10 km flight plan. A throttled engine does not burn as cleanly or efficiently, which is what results in the orange exhaust plume. Same as your campfire, blue flame is hotter than orange/red flame, and the bluer exhaust engine is therefore burning hotter and providing more thrust.
As Starship gets closer to the 10 km peak, it shuts off one engine at a time, and finally throttles the final Raptor down as low as it can go. Note that Raptor engines have a minimum throttle that is ~20% of max thrust, below which the only option is to shut down.
It basically means that you can't compare a pizza made from the basic ingredients that you and I might normally expect to the contents of a hot pocket. Even comparing apples-to-apples, the ingredient list of a DiGiorno's frozen pizza would be wildly different from the basics of a pizza you could make yourself.
Fearmongering over these subjects never helps, but it is fair to raise concern over the unknown effects of the things you consume.
> In this case maybe the analogy is that Apple/Google is supplying water - for money - but this oppressive regime uses it to waterboard people.
I mean no, that's definitely not the analogy. When Google/Apple remove these apps from their stores, they're directly taking action to further the oppression. It's not some innocent bystander thing, they literally have to write code or take other actions to make this happen. Remember, the status quo is that the apps stay in the store today. An explicit action is required to change that.
Make no mistake, it is monetary greed that drives the choice to assent to this.