Really impressed with Deno's overall vision and execution. They are taking the slow and steady road. I remember everyone criticizing them for not supporting npm at the start but I was sure at some pint it has to happen. You can't live without the npm ecosystem if you are writing code in javascript.
I am still not using Deno as my main production runtime but at some point I might make the switch.
Personally I'll use Deno if I can use it with Next.js which with this npm development I can see Next.js support coming soon. Next.js and Deno are both focused on executing code on the edge so it's just natural for it to happen.
Great work Deno team! You deserve all the credits!
I'm wondering if Vercel itself has interest in Deno, given their focus on the edge (and generally being at the forefront of JS tech). I hope they don't try and purchase it or anything, but first-party Next.js support for Deno would be awesome
if anything the alliances in the "battle for the edge" have already lined up - vercel with cloudflare workers, netlify with deno. it'd take a lot now to break those alliances
I don't really see the war analogy as useful... All of these companies want to be wherever the developers and the industry are. It's in their best interest to support (and be close to) whichever technologies prove valuable and/or popular. It doesn't have to be either/or unless there's prohibitive effort required to support both
Seems like Deno's answer to Next.js is Fresh. Wouldnt it be on Next.js to make themselves compatible on Deno? Either way, it doesnt seem like either party has too much incentive to make this work.
I am not sure if Fresh would be a direct competitor since it does not and will not[0] support client side routing. In every company I worked for in the last few years white flashes on page navigations were absolutely unacceptable.
I still like the framework, but it probably targets a more specific segment of the market. I think aleph.js[1] is more like next and then there is the esoteric ultra.js[2] which kind of tries to do something similar and be super bleeding edge.
Fresh is nice. So is Deno without npm. But it's always about the ecosystem. If Deno wants adoption they should invest in making Deno an option for new Next.js projects
I am still not using Deno as my main production runtime but at some point I might make the switch.
Personally I'll use Deno if I can use it with Next.js which with this npm development I can see Next.js support coming soon. Next.js and Deno are both focused on executing code on the edge so it's just natural for it to happen.
Great work Deno team! You deserve all the credits!