I don't find design patterns very compelling unless you're stuck with underpowered statically-typed languages like Java. There, they serve somewhat as a way out of the straight jacket. In more powerful languages there are better, simpler ways to design your systems.
But some many online payment companies had already tried and failed at "traditional" growth. PayPal crossed the chasm by essentially bad faith gamesmanship. Nothing illegal, mind you; but I would consider it highly unethical. Not to mention difficult to stop if you're EBay.
What about the PayPal way? They took a certain amount of VC money and used it to buy and sell on EBay and demand to pay/sell using only PayPal. It basically acted as a parasite on EBay until they reached critical mass. I call it "gamification of established platform". Diabolical but effective. PayPal's company mascot should be the Sea Lamprey.
All education will be biased toward people who have had more resources from early childhood on. But what has been revealed is kids that go to elite colleges but have fewer resources growing up and get worse grades actually do about as well as their better trained and supported counterparts.
So the conclusion is that there's probably a cultural bias going on for kids who are underprivileged that goes away once they enter the workforce if given the opportunities.
The 12-14 days is crucial here, I think: The US Army tested battle readiness and effectiveness off and on since WWII and found that you can keep a unit working well for a couple of weeks with about 4.5 hours a night. After that, they start to have serious problems. Less than 4.5 hours a night and the problems start a lot sooner.
And remember: metadata is everything. It makes the actual content of the communication discoverable and indexable. The information of what you're saying and doing is not actionable without being able to find it / categorize it at scale.
If you're not familiar with the JVM, I think this is a big ask for most people as far as ease is concerned. I have created a template on my github to use clojurescript with your typical NPM setup that would allow you to get started right away. I know of no equivalent in the JVM world mostly because of how tightly Oracle controls the download experience of the JDK.
If this is all about online expression, why borrow something from advertising with this horrid neologism, then? We can use regular english, like "persona". We don't need this, and I think it's harmful.
Furthermore, we have 75k dead. If we think we've peaked, this means we lose another 75k on the way down. And of course nobody with any opinion worth considering thinks we have peaked. So it looks like we could easily break 200k... If people weren't spending money out before, it'll be twice as worse.
TL;DR If you don't fix the biology, you will not get the economy sorted. This will just make everything worse. Totally backfire.
Can we agree this idea of a "personal brand" is both harmful and oxymoronic? You are a person, not a product. You have a reputation. This is like adding fuel to the idea that management should look upon the people who work for them as "resources".
DI/IoC is just another way of expressing global variables. The global variables exist because of the constraint of class-orientation getting in the way, among other things. Spring exists because of the relative weakness of the Java language. You won't see this kind of technology emerging in more powerful languages.
I read that you're supposed to work on / research / carefully understand the problem that needs solving and stay away from a solution for a long as possible. The problem has to pass a number of tests before going the next step of how you will reach people and get them to pay for a solution (often called the "go to market" strategy). Only after you've nailed this are you supposed to consider how to implement a solution.
State in the context of concurrent programming is not a "garden variety implementation detail." It's the Great White Whale of our industry. No language does it especially well. I have my favorites in this arena, but it's still hunting a large sea mammal with a harpoon. What you're suggesting is essentially avoiding hunting it altogether. We're not there yet.
What you're saying is exactly what I'm saying, except we disagree what a "better language" is. I find the approach Java has taken causes people to fetishize complexity with it. It's not so much about "my language has more features than Java therefore it's better" (the hoarder reference) it's "my language is simpler than Java therefore it achieves what Java does with less in multiple dimensions." And I don't mean Scala, either. That's just piling on more of what Java is.
The JVM world has Graal for AoT, FWIW. I would argue that await/async is really settling for the mediocre still. Many languages, even JVM languages offer more powerful abstractions and concepts for solving that problem. Clojure's implementation comes to mind.
I don't think you can compare V8 with the JVM. For starters, last time I checked, V8 is still single threaded, isn't it? Also it seems like future versions of JS are embracing things that make it look like they're envying Java, which seems like it's going in the wrong direction.
Looooong after the other languages have done it, Java comes around to doing it. Seriously, the best thing about Java is the JVM where you can choose a better language than Java to program with it and get all the benefits of the JVM.
I cannot agree more: I worked at a company where we went from a monolith deployed on IaaS with a couple handful of engineers to Docker containers deployed on ECS with over 200 engineers. The main reason we did it was because Docker+ECS was cheaper than a bunch of EC2 instances and you can't effectively use 200+ engineers with a single monolith.
After 2 years we had over 450 microservices while keeping our AWS bill flat or slightly decreasing.
One of the things I love about ClojureScript's Reagent library is that I will never need something like Redux because Clojure has was Redux does "for free." Reactive state management is baked in at the language level.
Absolutely 100% agree; Reactive programming environments become easily unmanageable unless they are Functional Reactive Programming for the exact reason you state. Hooks are a way to manage that complexity from an imperative perspective with the illusion of a declarative veneer.
Working complex systems develop from working simple systems. This is trying to get a working complex system by creating another initial working complex system. If only ruby didn't have that darned assignment operator...
Clojure doesn't really have frameworks, though. Every once in a while a framework-like-thing emerges but it quickly decomposes into a few libraries. The level of composition tends to be functions not objects, so there aren't any "taxonomy traps" associated with monolithic things in the OO world.