This misses a bigger issue with a baby bust: population composition. When birth rates decline sharply all at once, as is happening here, populations skew older and older. More elderly people being supported by fewer young people is also not a recipe for sustainability, in fact it is quite the opposite. The people who will be burdened with caring for the elderly are also the people who will need to have children in order to stabilize the population. This isn't an easy leveling-off of a population, its the beginning of a collapse.
That's a bold claim. Calories as a concept can be derived from the principals of Thermodynamics, to which the human body adheres. The conception of calories does however ignore the body's natural response to calorie restriction, and is therefore incomplete.
Many people complain about how good individual producers, but few talk about effective front-line managers being moved to where they are less effective. In organizations it's often assumed that the best managers need to be near the top of the org chart to spread their effectiveness as far as possible, but I contend that these great managers might be better off near producers in critical areas.
Vendor lock-in is just the price of using a vendor, and one which is often overwhelmingly worth paying. What you are saying is true, but it's not really enough of a detraction to justify building everything in-house.
Low inflation, yes, but not stability. Many people in their 20s now watched a parent lose their job during the 2008 housing crisis. Just because they didn't see the 70s don't mean they haven't seen macroeconomic calamity affect their parents microeconomic reality.
If this is your criterion for working at a startup, then you are too conservative to work at one. Every job carries risk, and looking to eradicate it is pointless.
From the perspective of an email receiver, I WANT things to be difficult for this group. Truly free email available to all would be unusable owing to spam. Oligopoly, I believe, results in the best experience for everyone.
Shorter trains are better because they are lighter and easier to control. The additional cars don't just make derailment worse, it causes the derailments to happen at all.
The ad-hoc solutions you're talking about are often highly usable, a virtue often forgotten by software evangelists. Nix's learning curve will keep away people who are disciplined in avoiding yak-shaving, as the language specific version enables productivity now. Maybe adding a layer on top of Nix, like create-react-app is to webpack, can make it a better option for immediate productivity oriented developers.
The Swiss government pays for it's citizens' healthcare, which is likely cheaper than damages paid in international tribunal. Also, these laws are typically very popular, even amongst smokers. Pursuing these laws is a no brainer for the lawmakers.
Roblox sells classes as a type of tech education after school activity, where they teach kids to build stuff in their game engine. Parents like it because they are often worried that regular school curriculums don't prepare their kids for a tech centric economy. HOWEVER, the material for these classes are entirely un-subtle about the prospect of making money.
Even worse, the game will guide you to spend in game currency advertising your game.
It's using the same dynamic as a multilevel marketing scheme on children.
Go solves this with problem with embedding. If a type is imbedded inside of a struct and has its own methods, those methods are implicitly available on the new struct.
I keep seeing this comment on HN, but I never really get it. In the world of platform as a service, launching a database instance is far easier than managing disk based storage yourself. It also has a very obvious route to horizontally scaling the web process. Deployment is easier too with an external database, there's no data on the disk of the machine running the web process that needs to be carried over.
More lines is generally less good, but I hesitate to really give out this advice. Classes are useful because they make great nucleation sites for future complexity, and often, more simpler lines of code is easier to read (and change). Not all additional lines of code are equally bad.
Scientists often think about one topic at length, and therefore tend to overestimate it's importance. This is a bias that needs to be corrected for. Thinking that a topic with which one isn't familiar is simpler than it really is is another unrelated bias.
Influencer marketing done well is scary effective because audiences often have a parasocial relationship with these influencers. The main downside with influencer marketing is that you have less control over how your brand is presented. That is why influencer marketing works best with small brands that can easily track the effects of their marketing. Naturally, this is a good fit for the mobile app (games) market and small e-commerce brands.
I'm not really convinced by "John Carmack doesn't think it's a bad deal, so it's probably ok". He might very well be an incredibly talented game developer, but he also hasn't been in the position of being unknown in the space since the 90s. He also isn't an economist. However, I do think he makes a good point about accessibility. I also think that similar arguments are commonly used to defend MLM companies, which many rightfully still dislike.
Have you considered just turning it off? Or adding a requirement for API keys and disabling any that they hand out to their customers. It would be pretty embarrassing for a large company that had a service go down because they refused to pay for it.
The landscape has changed. Most typical, everyday user have browsers that update themselves to the latest version. Supporting ancient technology (like IE6) doesn't provide a benefit that really justifies the enormous amount of work required. Just let the old browsers die already.
Large standard libraries are good. The more things are in the standard library for a language, the more likely it is that other 3rd party libraries play nice together.