that's a good point, when playing a bit with rust last year I found that the libraries that deal with "async stuff" (like http clients, db clients etc) are mostly split, some use tokio and some use async-std, and they were incompatible. Not sure if the situation has improved now but it looked like an ecosystem split at the time.
didn't the customers notice that they were given bad execution prices ? or would that be very hard to notice in practice ? (I'm not a trading expert obviously)
But when funding dries up for startups and companies have to shutter, then all of their digital operation overseas is cut loose. And the people who lose their jobs go into cybercrime. They think, “There's no other options for me. So sure. Let's do it. Lock and load.”
this section is just nonsense. So the crisis happens then devs in "developing countries" become cybercriminals ? total bs ...
I don't think this is going to happen. Hotwire-like technologies have existed for a long time with turbo-links, adoption is low and it's very unpractical to work with compared to a split backend api + frontend (framework or not as you prefer).
I think Netlify's success has got nothing to do with "microservices". The new (not so new now actually) trend that allowed it to prosper is when people started splitting up backend-rendered webapps (where the backend was effectively rendering most of the html, classic mvc/rails style) into a static frontend/single page app making api calls to an api backend (or multiple but it doesn't really matter here)
255 MiB of memory for machines with less than 1 GB of memory
25% of the first 4GB of memory
20% of the next 4GB of memory (up to 8GB)
10% of the next 8GB of memory (up to 16GB)
6% of the next 112GB of memory (up to 128GB)
2% of any memory above 128GB
For CPU resources, GKE reserves the following:
6% of the first core
1% of the next core (up to 2 cores)
0.5% of the next 2 cores (up to 4 cores)
0.25% of any cores above 4 cores
I agree, I tried go modules a couple of months ago but the VSCode tools were much slower and cpu usage increased when using go mod extensions. I reverted back to not using go modules at the time, will try again soon to see if it improved. I still like go modules.