2 ms·

The real pros of vanilla are: - not having to update due to issues in dependencies of dependencies of dependencies - not having to rewrite it all because fram

The real pros of vanilla are: - not having to update due to issues in dependencies of dependencies of dependencies - not having to rewrite it all because framework maintainer decided to shift to a new paradigm and no longer maintain the old version - not having your massive framework generating weird request flow that isn't defined in any RFC and can't integrate with industry standards - not having to pay for specialised hosting because only one or two companies know how to properly host and scale a website built with your massive framework - being able to integrate or understand actual web technologies because you don't have a massive framework abstracting it all from you Some frameworks or libraries may have been designed with some of this in mind. If you want to scale and integrate with other stuff, pick wisely because your whole code base will end-up tied to that framework, especially if "full-stack". Tho I have to admit developper experience can be awesome.

austin-cheney 2y ago
For me it’s: * having code that is more than an order of magnitude smaller and even faster to build and execute. * working with developers that can actually program and aren’t super afraid of state management, APIs, DOM, measuring things, test automation, and so much more. I really get tired of hearing about reinventing wheels by people who cannot create wheels or drive cars.
- cryptonym 2y ago
  I can relate to working with devs who actual knows about web technologies and are not afraid to learn about stuff outside of their framework-provided comfort zone.
swaggyBoatswain 2y ago
Im in this phase right now, I used gatsbyJS and netlify in my last projects and things became unmaintainable and difficult to upgrade after a few years, am in the process of just doing a complete rewrite where I have more granular control over everything regardless of framework / business corporatization

austin-cheney 2y ago

For me it’s: * having code that is more than an order of magnitude smaller and even faster to build and execute. * working with developers that can actually program and aren’t super afraid of state management, APIs, DOM, measuring things, test automation, and so much more. I really get tired of hearing about reinventing wheels by people who cannot create wheels or drive cars.

cryptonym 2y ago
I can relate to working with devs who actual knows about web technologies and are not afraid to learn about stuff outside of their framework-provided comfort zone.

swaggyBoatswain 2y ago

Im in this phase right now, I used gatsbyJS and netlify in my last projects and things became unmaintainable and difficult to upgrade after a few years, am in the process of just doing a complete rewrite where I have more granular control over everything regardless of framework / business corporatization