If you mean the clones, that's not exactly what I'm suggesting. I want Apple to continue building computers, but to use industry standard form factors, and to use as many commodity components as possible.
They could get such a product out faster than 2019 and it would be better than whatever they will end up announcing. Instead we have to wait a year for Apple to figure out how to make a computer that is 'pretty' and 'innovative' enough for Apple, even when their professional customers don't give a toss how pretty or innovative it is.
I wish Apple would just make their own ATX case (or any other standard *TX form factor), their own ATX motherboard with their TPM on it, and then use commodity components for everything else. I'd pay a huge premium for that product, but Apple is so far up their own ass trying to imitate themselves they can't see what their customers really need.
People are naive and easy to manipulate. Often (in history) they are manipulated into killing other people against their own interests. Few people are wilfully "good" or "bad".
You say that but people will happily drive at 50+ down a narrow country road. I think the "narrow = slower" only works for a limited period of time before people get normalised to it.
A high rate of road deaths isn't a fait accompli. Musk would have us believe that technology is the only answer.
The UK has the 2nd-lowest rate of road deaths in the world (after Sweden).
The roads in the UK are not intrinsically safe, they are very narrow both in urban and rural areas which means there are more hazards and less time to avoid them.
However, the UK has strict driver education programme. It is not easy to pass the driving test, with some people failing multiple times. It means that people only get a license when they are ready for it. Drink-driving will also get you a prison sentence and a driving ban.
It's not comparable with Python, which broke correct code to the point where even `print "Hello world"` was broken! This mootools issue only affects a very small number of users.
It amounts to a denial-of-service attack against the language, if you author a popular enough JS library you can screw things up for everybody in perpetuity. That isn't a healthy way to design a language.
Most people just don't care about the voice assistant on their phones, despite the efforts of Google, Apple and Samsung to make them care. Using a voice assistant in a public place still marks you out as some kind of weirdo. Siri is great for setting timers, that's all that matters really.
In the past, "nutrition" meant "getting enough calories", as in the opposite of malnutrition. Grains are plentiful, cheap calories and so they are "nutritious".
Of course if you cut them out of your diet and still eat the same amounts of everything else you will lose weight, that's just thermodynamics!
If your coworkers are so bad, wouldn't you rather get a nice message in your console when they forget to handle an error? With callbacks, error handling is entirely on the honor system.
There may well be some situations where callbacks are tolerable, but any time you have to converse with an external synchronous resource like a filesystem, database or REST API, it's just painful. Making a new function (named or otherwise) for each line of code is not good style, in any language.
They could make a Linux distro, a "yellow box" for Linux. I know it sounds totally ridiculous, but if Apple really doesn't want to make computers for software engineers, it doesn't stop them making an OS for software engineers.
Anybody who has used node.js for more than 10 minutes knows that the callback style makes code completely unreadable. Unreadable code is a breeding ground for bugs.
Back in 2009, that was an acceptable trade-off, because there were advantages to JavaScript, such as sharing code between client and server.
Now we have promises and we don't have to put up with callbacks anymore (eventually!). FWIW async/await is the syntax, and promises are the runtime, they are not competing features.
What made Whatsapp popular is that it worked just like SMS. Users are identified by phone numbers, so you can use your existing contact list.
However unlike SMS it didn't cost eye-watering amounts of money to use. Whatsapp never became popular in the USA because most people on pay-monthly contracts received large SMS allowances.
In the rest of the world, networks felt threatened by SMS -- if texts were too cheap then people would stop making phone calls! So it was universally crippled with ridiculous limits and fees. Even in 2018 it costs me a lot of money to send an SMS, and I don't know anybody under the age of 35 who uses it.
So? Let them be confused and frustrated. The world's not going to end. Big corporations have enough advantages without giving them rights that ordinary folk don't have.
Say that I am a mediocre violin player. But I happen to own a rare Stradivarius. A rich and successful violinist writes to me and asks to buy my violin. I refuse his offer. So he sues me, and says to the court that because he is so famous and so technically adept, the violin should rightfully belong to him. Is that fair?
Does someone know what the differences are between the final version and the draft that Chrome and Firefox enabled in Feb 2017? How much did they have to change for the middleboxes?
If you want error-free software you need a blameless culture based around process, not individual ownership of code. It should not even be possible for an error to be one individual's mistake, because by the time it hits the road it should have gone through endless code review and testing cycles.