In 13th May 2020, finally Deno is out, after two years of its first release.
For all the years of my career always I heard about the end of one or...
For further actions, you may consider blocking this person and/or reporting abuse
Other predictions of the past.
Microsoft saying they would kill the mainframe.
Java would replace everything.
C++ was better than chewing gum.
C# would kill Java.
But, Cobol is still kicking after 50 years.
As for Deno, I think it's architecture looks great. Its on my radar , but until the market appears I'm not going to stress out on learning it.
The good news is that other frameworks like Angular etc. already incorporate the module system. This means that ramp up time should be small.
You left one. Javascript will take over the world as Python did
Good thinking! Thanks!
Very good observations on old predictions.
And really, Cobol is a great example of a long life. Impressive!
Thanks for sharing.
Let me add another...
Well, if Node was dead I guess that Deno wouldn't have used it for its website
Not really worth the time to build your own web deployment solution when you can focus on actual engineering for your newly GA'ed product.
twitter.com/luke_pighetti/status/1...
I can't agree more, not using Deno is a sensible engineering decision
It's a good point!
Well said: "it is, likely, the new Hype" ... that's what it is, a hype. Just wondering, if ever a future node.js version would support TS compilation and EcmaScript modules, then what would still be the advantages of Deno? The differences would become pretty marginal.
Yes, I agree with you!
Whenever a new hype arises, it also brings a lot of expectations.
Deno is really interesting and brings a lot of news, but his future is certainly still unknown.
Deno's future may be very promising, but it will depend on many factors, including what you mentioned about the Node that is already consolidated.
I think the question shouldn't be: is node dead? Or even: is deno going to kill node?
We all know about picking the right tool for the job, this is just another tool that will fit some job. Which is great. The more tools we have, the more we can mix and match to suit our needs!
Good idea!
Certainly, your suggestion would have been a good question for the title of this article.
Thank you for your cooperation.
As the world moves towards API Gateways and Lambda / Functions I see less need for many of the features Dino / Node provides. Many of the services provided by a framework will inevitably be pushed outside the endpoint.
I think Deno will definitely replace Node when it comes to running JavaScript applications on a server, as the developer experience is so much nicer. But Deno is a long way off replacing Node in terms of browser support, and it may never do so. So I think we can expect Node to be around for the foreseeable future.
Deno will produce some new stories!
But it can't override the nodejs stories...
I agree. I hope both produce good stories!
Thanks for your comment.
I don't think Deno would kill Node Js but It would be interesting to see how community and enterprise adopt Deno
In fact, I'm also looking forward to seeing what the adoption of Deno will look like.