My father believed that truly great restaurants don't do this, because they KNOW their food is perfect.
Practically speaking, though, dpeck is right... shortly after the food is dropped, the waiter should confirm the meal is to the customer's expectations. This is also the chance for customers to ask for condiments, get a replacement fork for the one they dropped, etc. Nothing worse than sitting in front of a hot meal you can't eat and being unable to get the waiter's attention.
It's the internet... we're all unknown to each other, and many modern web apps are running a huge stack of unvetted code.
Honestly, a problem like this is overdue, especially for the NPM ecosystem with its propensity for a huge number of transitive dependencies, but also for all other major repos (nuget, cargo, CPAN, Docker, etc.). OS-based repos (Debian, Ubuntu, FreeBSD) might feel a little safer because it's harder to become a publisher, but it's not at all impossible. Perhaps the only reason it hasn't been a target before now is because there are easier avenues for cybercrime.
Perhaps the rhetoric of free-market-can-solve-everything Libertarians, the get-the-government-out-of-my-health-care Republicans, and the healthcare-is-a-human-right Democrats are all co-opted by America's crony capitalism and we get... this.
Perhaps their true market will be for industrial IOT devices that need to connect from all over the world.
If I'm selling large HVAC units with cloud monitoring functionality, it'd be attractive to ship units that are pre-connected to SpaceX's satellite network. I wouldn't have to worry about setting up agreements with multiple cellular providers or having to depend on site-provided Wifi/ethernet.
The point is, those devices could very lucrative for SpaceX without requiring as much bandwidth (no need to stream Netflix).
Right. Everybody's pointing out the race-to-the-bottom for cities, but another bad side effect is that it's unfair to competitors (particularly small and medium businesses that don't have the same sway).
I feel many fluent API's are guilty of something similar. You gain terse, one-line magic statements that accomplish a lot; you lose discoverability and meaningful object-oriented class names.
For example, ElasticSearch's NEST API client uses a fluent-style API to setup configuration and mappings. It started out well, but then I got lost in a forest of nested callbacks on various mystery objects. It was a bizarre way to build what should have been a tree of strongly-typed POCO's that have a 1-to-1 correlation with the server-side concepts. Worse, I didn't see a way to dynamically manipulate the (hidden) result. Better to use the low-level API and a little reflection to compose the required JSON manually.
[On the other hand, I can think of successful fluent API's: .NET's StringBuilder works because it is super simple (only returning instances of itself). The IEnumerable extension methods (created to support LINQ) work because their broad-applicability justifies the effort to learn.]
> I sat with a whole table of them and watched them fall for a simple social engineering attack one minute after being told they were going to fall for the attack.
That falls under a number of strategies for Solar Radiation Management [https://en.wikipedia.org/wiki/Solar_radiation_management], which, as you say, doesn't address the core CO2 concentration problem, but it might buy us time.
Personally, I like the idea of Marine Cloud Brightening. Getting 1 or 2 thousand ships spraying seawater into the air seems tractable, if not trivial.
OP (Mengkudulangsat ) expressed problems with sharia finance in terms of investing fundamentals (risk, complexity, etc.).
stealthcat objected to OP raising these points and appealed to authority (variously, Islamic leaders/theologians, foundational religious texts, and God). stealthcat questioned OP's intentions and religious commitment, implying he might not be a Real Muslim(TM) and exhorting him to defend orthodox teachings.
To stealthcat, I would challenge him to consider that many religions are plagued by convoluted rules, to which people come up with hokey workarounds. Orthodox Jews have sabbat elevators; Amish use pay telephones; Sikhs have kirpans (knives) that are impossible to unholster. projectramo's comment about sharia finance obfuscating the principle of interest seems very on-point here.