This is a very broad question, but the most straightforward answer is to use a popular full stack framework like Ruby on Rails. It'll give you most of what you need out of the box, and there's 3rd party packages for the rest.
They were mostly closed prior to the huge price spike, the spike was caused by retail buying, probably thinking they were causing a squeeze. You can read the details in the SEC report on the topic (note the massive drop in short interest in Figure 5).
Doesn’t closing positions cause a price spike in the first place? It seems to me that they kicked the can down the road waiting for a better opportunity to do so.
It did cause some price spiking, but the FOMO caused a much bigger spike and eclipsed the effects of the squeeze. Why do you think they "kicked the can down the road"? Short interest is still around 1%, down from over 100% in January. The hedge funds in question realized huge losses in Q1.
await won't block Node from handling other requests but it will block the thread that is awaiting. For example, these will execute one after the other (the "bad way"):
await slowThingOne();
await slowThingTwo();
but these execute in parallel, awaiting until both are finished (the "good way"):
Minor clarification, the latter example will only await until both have resolved *or* one rejects. To await the resolution of all promises, you should use the truly gamechanging `Promise.allSettled` , though you will have to transpile it if it's not supported by your target environments.
The article actually kind of addressed this with the shades, and I think that's what a lot of non-designers miss; having several shades of the same color adds a lot of variety without looking cluttered ("feels like few" as you said).
But I don't understand the point of the shades, then. Why not go for the real thing? Why not use the exact same color, and it will not only "feel like few"? What's the actual advantage of using different shades (besides making the work of the web designer seem more difficult).
It lets you display more granular information. You can have light blue buttons with dark blue text, as well as solid blue buttons, to convey "primary" and "secondary" CTAs for instance.
You could try to display the same amount of info in less color, or even black and white (maybe outlined buttons, bold/regular fonts in the text), but color variation looks "good" to the majority of eyeballs.
The author is one of the creators of Tailwind CSS, which gives you a predefined color palate but no components, and is intentionally opposed to the Bootstrap ideas. The recognizable part of Bootstrap isn't the fact that errors are red, it's the shape of the buttons, inputs, etc., and the fact that all errors are the exact same red as other Bootstrap sites.
At the end of the day "good" UI doesn't have a lot of room to be different -- it actually needs to be recognizable -- but you don't need to change much to avoid being generic. Using different shade(s) of red for errors is one way.
The irony is that you can now often recognize sites being designed with Tailwind the exact same way. They tend to use a certain font, they tend to slightly overuse the card metaphor with a rather specific corner radius and box shadow...
When looking at this site I immediately though: aha, this guy has been using TailwindCSS to design the website... (until I realized that in fact yes, it was designed with Tailwind and the author is also the author of tailwind itself.)
So I guess it's the same as bootstrap at the end of the day. Both provide you with options to customize them. Most people don't.
That being said: Working with tailwind is amazing!
