Recursion is natural and easy to understand when the argument of the function is a recursive data structure, and the cases are patterns on the constructors. These are natural and useful cases, much better than the alternative. Starting with misguided examples like factorial is demotivating.
Even if the Moore's law is not dead, single-thread performance and clock frequency have plateaued 10 years ago. This is the key factor. Because of heating even if you squeeze more transistors onto a chip you need to reduce the clock, so even if you may get higher computational throughput the latency will go down. And this is another argument for chiplets or any other alternative computational architectures.
"The consumption of electricity in everyday life was limited (it was forbidden to use a refrigerator during the winter, and the use of a vacuum cleaner was banned all year round), hot water was supplied to apartments twice a week,"
> 3. While the size of any one conference has to be fixed, tech has made it infinitely easier to create new conferences and journals with other focus areas. They may not start with the prestige of a larger journal, but if the papers published start to have an impact, it can catalyze an entire subfield of work.
Does it though? The largest conferences I go to as a CS academic have hundreds of people. There are academic areas where 10x people participate. The size limitation is a self-imposed excuse to keep acceptance low. I have been PC chair of two conferences and my attempts to expand the conference numbers were shot down by the steering committee precisely for this reason, not because we couldn't find a larger room.
> For example, in Sri Lanka, there is no way for someone to accept payments or send money through PayPal or Stripe. However, people will be able to send money through the blockchain and bypass these restrictions if more people begin to trust crypto.
If Sri Lanka blocks PayPal and Stripe are you sure they will not block commercial entities from converting between rupees and crypto-assets? Individual and small scale operators might still do it, flying under the radar, but that is not a scalable proposition.
At the airport I don't merely sit and wait. I catch up on email and paperwork, maybe start watching a movie. It's not wasted time so I don't mind being there 30 mins extra for safety.
You don't seem to understand what the previous poster said: all of this can be achieved with a database that allows some open access. You don't need a consensus protocol on a distributed system.
The article makes some specific points, which you fail to address. Your objection is a generic "never mind that, just give it more time". You can do better.
Everything about fancy hotel bathrooms is a usability nightmare. Sometimes there are two showers (hand-held and ceiling-mounted) operated by a single lever which sets temperature, pressure, and which of the two showers is active. The risk of giving yourself a too hot or too cold burst is significant. I usually cower into a corner while sloooooowly messing with that lever.
For an extra bonus: You usually have three identical looking small bottles with 'shampoo', 'conditioner', and 'shower gel' only distinguished by a tiny label, something like black-on-brown or yellow-on-white. Good luck if you are wearing glasses.