Why is Javascript so advanced yet behind?

👨‍💻 Learn Test-Driven Development with Laravel!
tddwithlaravel...
Sign up to 30 Days of Laravel 👉🏻 30daysoflarave...
👨‍💻 Sign up to my newsletter and receive PHP, JS and Laravel news in a weekly-basis:
subscribe.mate...
🎉 Party up:
/ mateusjatenee
/ mateusjatenee
/ mateusguimaraes
Thanks for watching!

[@derelicts9503]

I think this is a correct view Mateus. I work with JS mostly (React + Next), but we have Django on the backend. Everything on the frontend is mostly cobbled together from various little packages. I thought JS backend frameworks were like Django - but it's the same thing, everything is fragmented, I think only AdonisJS and NestJS are batteries included frameworks, and they are FAR behind Django. The Node community, in fact JS community in general has the mentality of "I don't want opinionated frameworks, I WANT to cobble up solutions by myself". This leads to massive overhead in maintenance, code quality and delivery time for projects. Hope the pizza was good, now I'm hungry lol.

The pizza was really good! You should order one!

[@neverything]

Great video Mateus, I had this thought over and over again and never figured out why the JS world is like that or if I’m missing something.

[@stevebauman]

You've hit the nail on the head imo, there wasn't a single thing I disagreed with!

[@binaryfire]

100% agree. But for some reason most JS devs prefer the bits-and-pieces approach to a full-stack framework. This is a comment from a Reddit thread asking why Adonis isn't more popular: "It's a mistake to provide built-in features like authentication, ORM, security, etc, because framework has no idea about project requirements and developer preferences. Even project structure and file naming should be comfortable." That's the total opposite mindset to us. Personally I think it's because most JS devs haven't used a *well written* modern full-stack framework (whether it's written in JS, PHP, Ruby or whatever). Once they do, they're often blown away by the difference.

Damn. That Reddit comment doesn't resonate with me at all!

[@lassestube]

I just talked about this last week.

[@wilsonwg]

I think it's just a different way of doing things. While Laravel is convenient, it's sometimes hard to twig things and there are many configs are not mentioned or explained on the Laravel's official doc. While it's true node frameworks do take more time to setup, but I have learned more fundamental concepts and the ways of things work. And Symfony is also quite different from Laravel and more similar to non-opinionated frameworks. The start project file structure of Symfony is very small. You add more modules or components as the project grow like many other js frameworks or Go frameworks.

I don't fully disagree with you, but I guess my point is it's less about the framework being opinionated (which I think that for the average project is a good thing!) and more about too much friction within an ecosystem. Symfony is, before a framework, a collection of components -- but they're still cohesive within a first-party or even a third-party level. They have e.g bridges.

[@clickstudiosdigital]

Bro i just discovered your channel. You are really cool, dont stop. Cheers!

Welcome aboard!

[@sonoftroy8572]

Agreed