Why you Shouldn't use NODE JS in 2023

Why developers should say NO to Node JS. Why? Because Node unfortunately breaks a fundamental rule of software development: don't be brittle! #nodejs #javascript #unclestef

🔥 STEF'S DEVELOPER BOOTCAMP AND MENTORING PROGRAM

🔥 JOIN STEF'S 'CODER'S CAREER PATHS' NEWSLETTER:

🔥 FREE: LIZARD WIZARD KOMODO - TRANSFORMATIONAL MIND TRAINING:

*************

WEB HOST PAYS FOR YOUR WEB DESIGN TRAINING IN 2023:

POPULAR & EASY CODING COURSES:

*************

🦎 Lizard Wizard Course:

📚 BOOKS TO READ:
… Complements Studioweb courses on HTML5, CSS3 and JavaScript.

The Naked Ape:

✉️ STAY IN CONTACT:
Stef's social links:

Stef's business channel:

👉 GOOGLE REVIEW:
Leave a Google review about Stef.

MY MOUSE & KEYBOARD:

SUPPLEMENTS THAT WORK AMAZING FOR ME:

Protein Essentials Beef Gelatine Powder:

... Healed my very bad knee. If you have joint problems, this *could do miracles for you.

Webber Naturals 88862 Glucosamine Chondroitin

MY CAMERA GEAR:
Canon EOS C70 Cinema Camera

Thanks!

Stef

#mentoring #codecourses #unclestef #codingcoach

[StefanMischook]

I misspoke in the video: OOP was invented to make code less brittle.

[nikilk]

The whole idea of not using Node because packages break your code, can be fixed by deciding what version of the package you want in package.json. When you want to upgrade packages you then change the version, run your tests against the new package and your good.

[Self-learner-iccr]

For novice programmers, the choice may not be entirely theirs, as many web development resources predominantly focus on teaching Node.js. The prevalence of Node.js in these learning materials often leads beginners towards its adoption.

[MasterHernan]

To be fair, PHP composer packages can also mess up your project.

[ZlatanYU]

Node JS is invented to write JS on a server side. It's not Node's fault that you adopted it as JQuery and using bundle of dependencies and frameworks instead of writing own functions. So it's the same thing as if you would use only Laravel and blame PHP for your packages breaking. Become real JS developers instead of framework and module operators.

[alan-overthenet]

I started a long time ago with one of Stef's early courses. Over the years I wandered off and tried to learn just about everything - I have, honest!
I'm not your typical learner. I don't want to work for a big company. I don't want a full-time job, and I'm not after a big income. All I want to do is make a modest income as a Freelancer.
I have now come full circle and realised I can do what I want with HTML, CSS, JS and PHP. So it's timely - a coincidence - that Stef posted this.
One size doesn't fit all.
Good luck all.

[JabariHunt]

🙄 Keep in mind, that comment came from a junior dev. I've been developing on PHP for 20+ years, alongside Node for the last 4 1/2 years. Just as you stated PHP of today (7 & 8) isn't the PHP of old (<= 5), NPM of today isn't what it was either. If you're committing a package-lock.json file it's a non issue... Literally as stable as Composer. I havent had a stability issue with NPM in years. What I have had is a tremendous increase in the number of requests our APIs complete per second. I love PHP, but the performance is not in the same class as Node, not even close. The performance gains of Node far outweigh the learning curve for proper NPM usage. Then there's Bun...

[ardapeker]

The package updates in npm can be a real pain in the neck. Over the last few months, I've been trying to learn Next.js v13, only to find out they've rolled out v14. Learning something new in the JavaScript ecosystem can feel nearly impossible sometimes. After wrestling with Next.js, I've decided to steer clear of learning and using Node.js for backend development.

[ukaszzbrozek]

Now modern Front End took a turn into SSR. Next, Nuxt and so on are Full Stack JS/TS frameworks using node under the hood. The ship is sailing in node js direction. I don’t know if it is a good a thing but it is a fact.

[coolemur]

Question:

1. Why you state that in nodejs dependencies can be changed ? If you are using same versions, it will not change unless you'll upgrade packages.
2. How about all functionality that community creates? I doubt PHP has so much library options.

[JoseHenrique-xglp]

No wonder Go is going so well (no pun intended). It has a vast first-party library. The frameworks around it are very minimalistic

[Sergeant_Camacho]

I just use JavaScript for frontend purposes. The real fun is happening in the backend, server PHP stuff.

[pmsanthosh]

Issue occurs when you use less used npm packages for very small use cases. One should select and use any third party libraries consciously

[DB]

I kinda take issue with the title of this video. So really it's only if you use NPM to leverage already pre-existing code to solve your problems. And that is often found more when NodeJs is used as a basis of front end development like with Angular which relies very heavily on NPM packages. If you use just vanilla Node JS like in AWS Lambdas where there is not often a need to use NPM packages because much of what you need in a server environment like the File System is already in vanilla.

[twd]

If just about breaking Apps, just use a specific version of "Node" that is compatible with your code and external "libraries, packages", and put them in a container, it will work forever!!!

[SlodkiFistah]

Love your videos, appreciate your experience and deep insight into programming world.
I have used javascript and Node for the most time.
Since september I am working on a website build in PHP many years ago, it was a huge pain at the beginning, but now i must admit… i begin to like it ;)

[MojoTojoChannel]

I tried node for a bit and coming from a strong PHP background, I couldn't believe why people couldn't see through the hype and why people want to add so much complexities to their environments. I'm glad I didnt waste any more time on it. Stuck w/ PHP since, it's not the prettiest but damnit, everything just works with it.

[autopop]

With correct use of package-lock.json, is node package instability still such an issue?

[nykytakudrya]

I don't have much experience, but it seems to me that if you use just a few well established packages you should be fine. I think the main reason why people upgrade their packages on the backend is because of security reasons, you shouldn't be running outdated version of node or your framework. If you just use nextjs with prisma orm and don't install an additional package every time you need something simple(for example number is even), i think you can avoid most of the nightmare described.

[andrewfurnevel]

I loved CodeIgnitor back in the day. It taught me so much about frameworks and how OOP works. I'm currently building an OOP framework loosely based on CodeIgnitor that turns the cluster fuck that is Express.js into an organized OOP framework. So thank you CodeIgnitor, you rock!