4 ms·
Anyone using Demo in production? If yes, what's your experience has been as compared to, say, Next.js?
by jatins 3y ago
Anyone using Demo in production? If yes, what's your experience has been as compared to, say, Next.js?
- frou_dh 3y agoThe equivalent of Next.js would be Deno + their "Fresh" web framework. https://fresh.deno.dev/ https://fresh.deno.dev/ My impression of Fresh is that it's neat technology but basically a barebones MVP at this stage. They haven't done much development on it since v1 last year, presumably because the team has been busy with other stuff like what's described in the article.
- presentation 3y agoYeah I tried it out but it’s clearly just a demo and not at all production ready. Maybe they should be prioritizing some this as a killer app that would bring people over, or else achieving full compat with the industry incumbents.
- re-thc 3y agoIt uses Preact other the hood which often has edge cases vs React and its ecosystem, which makes adoption harder.
- gorbypark 3y agoI am using Supabase in production (small DAU app for a large company), which uses Deno Deploy as their function provider. So far no issues and it works well. It’s also quite easy coming from a nodejs / browser js background to pick up, as it’s just JavaScript after all.
- presentation 3y agoSeems like Deno is having an SEO problem with all the people autocorrecting its name to Demo lol
- vbezhenar 3y agoI wrote tiny script which reloads kube deployments when GitHub CI finishes. I liked the fact that I did it with zero dependencies. Standard library is good enough, and I even had to use some crypto. Zero effort configuration is superb, I hate when I need to configure node for all the things, it easily takes few hours. I disliked the fact that this script constantly eats few percent of CPU despite being idle 99.999% of the time. Not a big deal but a sign of bad engineering.