Why I don't use node.js

I talk about my reasons for not using node and why you might want to consider Rails, Django, or Laravel instead.

[@srikarakella7955]

Perfectly articulated man!!! This is the reason why I am moving to something more stable like SpringBoot or Go. I started working with Express a month ago and found out every single tutorial is either outdated or in fact I could not find any latest express tutorials that solved some problems, rather youtube/medium is filled with Next.js, Nextjs doesnt have as many openings as Express. Then comes typescript integration, every single module has to be in types and few middleware do not compile as the type is not recognized. Javascript was better than Typescript in Express. In fact, people now are saying Express and Passport.js are kinda outdated and suggest to pick something else. There is not a single architecture or approach or in fact a library for auth or a library for REST API at this point, every day something is brought new and the old ones are constantly marked outdated.

[@GringoDotDev]

Completely correct! Here today, gone tomorrow in that ecosystem.

[@pmrebel2733]

You speak the truth man, this generation devs are so in love with complexity. Js is not great for backend

[@GringoDotDev]

I agree!

[@MrBrady95]

"The JS ecosystem moves so fast that it can't form a foundation." Exactly what I notice.

[@GringoDotDev]

Yup. :)

[@santaigoavilezdev]

Really good rant man. Im starting my carrer as a freelance developer, and i feel in my soul those issues that you ponted in the video. I think the npm dependency hell and the auth vendor lock is bad. But i dont like writing php anymore, even when in collegue i used only php. When i used laravel i hated the amount of files and directories. But its full stack and with livewire is super cool. Anyways I think the best tool is the one you like the most or feel the most confortable to write code without figuring so much stuff. Good video man keep going!

[@GringoDotDev]

Thank you so much for the thoughtful comment! I totally hear you man, and also agree that the best tool for you is the one that you're most productive in. Out of curiosity, what do you use for new projects now? I don't mean to evangelize Laravel (for real - I really don't get attached to tools) but if your biggest issue with it was the number of files and directories, you might want to check out Laravel Folio and Volt which just came out the other week. Here's the announcement: kzbin.info/www/bejne/Z4GWqH-vaZ6naMU

[@GringoDotDev]

and also, I wish you very good luck with your new freelance career!

[@santaigoavilezdev]

@@GringoDotDev Thanks for sharing! I will look into it, my team has worked with Laravel before and maybe later with another project I will give Laravel a chance. Currently, I'm building an app for an early startup with the t3 stack (Next 13 but with pages' router, Tailwind, tRPC and typescript) But most of the time I use Next.js, with a CMS if the client needs a dashboard to manage the content (ecommerce, or blogs). And Astro for static sites, If Astro grows enough I'm looking into switch from Next to Astro because of the island architecture and how much the sites are optimized.

[@santaigoavilezdev]

@@GringoDotDev Thanks! I'm indeed lucky to have found my first client so fast. I already subscribed to your Chanel, keep with the good content! ¡Saludos desde argentina!

[@GringoDotDev]

Y un abrazote de México amigo!

[@phpcoderusa]

Cool Keep Going!!

[@GringoDotDev]

thank you!! I will :)

[@iamvalenci4]

great content!

[@GringoDotDev]

thanks so much! I enjoyed putting it together!

[@Shyam_Mahanta]

Your points are valid but i love nodejs. Django is also very very good but you know it actually constraints some staff i guess but yeah its also good and very reliable but in node im like open to do whatever i want theres no pattern to follow

[@GringoDotDev]

Yeah, the downside of an opinionated framework is that you may not like the opinions, and in those cases an express-style microframework will shine because you can pick your own tools and conventions top to bottom. I have to say though, in those cases I would personally just use vanilla or close-to-vanilla Go to keep my dependency risk surface small. Thank you for the comment!

[@josephp.3341]

Go > node

[@GringoDotDev]

You’re not wrong lol

[@azaamabubacker]

NodeJS 💪

[@GringoDotDev]

;)

[@user-of6ls2ng5l]

Use Bun bro

[@GringoDotDev]

I’m keeping a close eye on it as it matures. The module resolution and perf seem like a big improvement over node at minimum.

[@GrasslandHerbivore]

Where to start? The ecosystem is a mess. Even when you limit it to the frontend where it belongs, the latest garbage fails in the least graceful way. NextJS: "A client-side application error occurred" Give me something sane. Prefer Java or Rust on the backend. Typescript is just more duct tape over a bad design. You have to use some JS in the browser, but it shouldn't break your project. Most of the functionality you need is provided by the browser API. Rely upon that instead of some insane SPA framework. We're at a point where jr. webdevs don't know basic HTML.

[@GringoDotDev]

Preach!!