Besides the uselessness, let's not ignore the awful downsides. They're a huge boon for randsomeware. Oh and they're an environmental disaster.
Frankly I'm not really sad to see this stuff collapse, because when you get rid of speculation there's not much good about crypto.
I do think we need some sort of crypto currency in the future. I believe in the _idea_ of it. But the current implementation is ridiculous and awful. It needs to function as an actual currency, that you would be willing to spend, not as some sort of incomprehensible "investment" vehicle.
What we're seeing now is akin to the the dotcom boom / bust in the late 90s and early 2000s. A new technology has appeared on the scene which leads to two things:
1) People get ahead of themselves. In the late 90s, people could envision all the cool things the internet would unlock and tried to start businesses to realize the potential. Many of those business ideas would be viable today, but the tech wasn't there at the time leading to a lot of empty promises being sold. Today, people can envision how the blockchain will lead to the securitization of everything, but the tech isn't quite there to make the transition yet.
2) As with any optimism boom, there will always be crooks ready to separate a fool from their money.
In fact, the NYT outsources their ads to Amazon's advertising business.
[0]: https://www.sec.gov/Archives/edgar/data/1652044/000165204422...
The NYT is in the "providing content to lure people to advertisers" business. They don't sell ads to third parties. They could be very symbiotic with Google, for example. If Google was searching their content, bringing readers in, and supplying ads. But, instead, Google scrapes their content and helps people never visit their site at all.
What does that mean? The NYT sells ads, i.e. you can pay the NYT to have your advertisement shown in the NYT. Google sells ads, i.e. you can pay Google to have your advertisement shown in Google results. The NYT and Google sell the same thing. They are competitors.
int sfd = socket(domain, socktype, 0);
int optval = 1;
setsockopt(sfd, SOL_SOCKET, SO_REUSEPORT, &optval, sizeof(optval));
bind(sfd, (struct sockaddr *) &addr, addrlen);
In Go, you can use syscall.SetsockoptInt. Most languages have a way of setting this option. You have to create the socket yourself and pass it into your HTTP server in most cases, but it depends on the library.Edit: oh sorry, you meant when systemd is opening the port for you. It looks like you can set ReusePort=yes in your configuration? https://www.freedesktop.org/software/systemd/man/systemd.soc...
However, my main gripe with Deno is that it's tied to one company and it won't solve issues that it doesn't have. As an example of this, a version of nodes cluster module is not supported so there is no way of running one deno process per cpu which is very bad if you're hosting it yourself and want to utilize the full potential of your hardware.
It also means that if your app is bound to some CPU heavy action, like generating a large excel-file or similar, your app will go down since no requests will be processed due to the single thread nature. Of course, such actions can be solved with a web worker but what if you make a coding mistake which renders an unhandled exception? In this case the app would probably go down and if the end user for example does the same action over and over again (which end users tend to do in frustration), the app will go down again and again.
Deno as a company has probably little interest in solving this as the solution is to run it on their paid service. You could of course have several servers hosting the app, but that gets expensive real quick especially if you are a small shop. Another example is to run the entire app process as web workers but then you need to spin up many processes that all have their own ports which you need to add a load balancer in front of it. This is kind of advanced and adds unnecessary complexity to the app IMO.
Also, if Deno the company company fails, what then will happen to Deno the project?
This option is also quite good for deployments as you can have instances stop reading from the port while client traffic is still being served from other instances on the port. This works well for HTTP requests, but less so for something like gRPC.
I can't believe they seriously held that much of their total value in their own issued token. That's just preposterous. Imagine if JP Morgan Chase's entire value was in JP Morgan Chase stock, and they just reported that as their value in cash. It's like recursive valuation.