DEV Community

Discussion on: How is it like to work with GatsbyJS as a Nuxt.js developer?

View post
Collapse
 
triloworld profile image
Patryk Padus • • Edited

We use NUXT as main engine. Why and what const and pros we have from our point of view?

  • one guy that is hero and won't change license in midnight. React changed one time license and back-up but we see what's going on ;/ I can sleep well.
  • old code and approach is removed, not same as react and gatsby is older and thus having some quirks. Hooks, lifecycle and Composition API. Most plugins have high level of quality thx to poa and other core memebers. All because component are less prone to error. Use all what you need from nuxt as API is new and fully featured.
  • component can be mixed like utility (React like) but have some ground level setup requirements (standards) - Like Angular. Not fully MVC but have some minimal structure what gives quality and code coherence. So you can take Vue and add everywhere easily and have same base standard like in nuxt. This for our company help so much :) I don't like to switch between Gatsby and some project that are on PHP/ASP (check this one for vue 3 - dev.to/webdeasy/how-to-build-a-vue...)
  • You have some pros and cons of all libraries. What is most important in future is who and how maintain your website. In Nuxt/Vue component way we can onboard in less than 6 month person. Great documentation and less wiring. Maybe not everybody see problem when they hit hard on "staff required" issue. This is MAIN original point to use Nuxt - It supercharge Developer eXperience (DX) in way what Gatsby won't ever do because of complex wiring in background.
  • documentation. I like to add Polish version too. Just need time. We all see difference between Nuxt and Gatsby. Community isn't the main point. When using something I need fully documented engine. Some quirks and errors need to have solution. All have issue or documentation - that's huge benefit that You stick with nuxt in long rune. 3 Persons work on 5 different scenarios in one company and can have one standard way of "doing it" is our chance to success and have less bugs in front of clients. That's my 5 cents :)