4 ms·
This can be the killer app that Deno needs. As of now there is no specific reason for most of the people to try Deno as Node with its plethora of frameworks wor
by pritambarhate 4y ago
This can be the killer app that Deno needs. As of now there is no specific reason for most of the people to try Deno as Node with its plethora of frameworks works and every one can choose their stack as per their taste. But if they can make Fresh sufficiently better (more cohesive and/or performant on both client and server side) and more feature rich on the backend (ORM + Workers/Queuing) with instant deploy then more people might consider switching.
- andruby 4y agoI didn’t find a mention id this Fresh framework could also run on Node. In other words: is it relying on anything deno-specific?
- pxeger1 4y agoDeno and Node are not generally compatible: - their module/packaging systems are totally different - their APIs for interacting with the system are different
- ecares 4y agoIt took a friend and I 2 days last year to build a compatibility layer that allowed to run all the tests of Deno on Node.
- threatofrain 4y agoHow far along is the story of cross compilation for the two ecosystems?
- lucacasonato 4y agoNode -> Deno: https://esm.sh https://esm.sh Deno -> Node: https://github.com/denoland/dnt https://github.com/denoland/dnt
- Already__Taken 4y agoI had no joy trying to get a node JIRA library to run under deno with the various platforms. So still some way to go. Didn't seem far off. IIRC axios was the problem.