I'm primarily focused on backend development with FastAPI and AI research, but I've come to realize that I need a solid understanding of frontend development as well. This will help me create decent user interfaces, effectively use AI tools for frontend setups, and not get stalled when working on product ideas. I'm not aiming to be a frontend expert, but I'd like to become comfortable with a stack that includes Next.js, TypeScript, and TailwindCSS, which seems like a good blend of modern technologies.
My main confusion revolves around the runtimes:
- **Node.js**: It's the default choice with a vast ecosystem, but sometimes it feels a bit cluttered to set up.
- **Deno**: I really like its Jupyter notebook-like features and how developer-friendly it seems.
- **Bun**: It appears to be fast and modern, but I'm uncertain about how mature its ecosystem is.
So my question is: If my priority is product building and not extensive frontend development, will choosing Deno or Bun really impact my developer experience significantly? Or should I just stick with Node.js since it's what most frontend tools are designed for? I'd appreciate insights from anyone who's made a similar transition from backend or AI to having basic but solid frontend capabilities. Thanks!
3 Answers
Bun is gaining popularity and seems to be attracting more developers lately, which might be a good sign if you're looking for something modern. However, if you're more concerned about marketable skills, sticking with Node might be safer since it's well-established and widely used in many companies.
Good to know! I'll keep that in mind.
Here in Brazil, Next.js is more of a hype train. While startups are using it, I haven't seen many larger companies adopting it at a rapid rate. Just keep that in mind as you choose your stack!
I'd recommend sticking with Node.js until you really understand what its drawbacks are. It's the standard for a reason, and you might find that it meets your needs well enough for now. Plus, you'll have more resources available to help you out!
That sounds like solid advice, thanks!
Totally agree! Most issues come from the brain-developer interface, not Node itself.
Definitely worth considering the job market while you learn!