I think it's time we start considering our options the next time we are starting new projects. Too often I see projects going with React because "it has the most job listings, so it must be the best choice". Maybe there is a better solution out there π
I totally agree. Someone once told me, βcompanies like React, developers like Vueβ which is quite interesting. I love Vue for its clear separation between HTML, CSS, and JS in projects. I canβt go back to React anymore with JSX π
Haha, that's a funny and interesting take on it π Because of this I'm doing Vue in my free time and React at work. There's a lot of debate about state management and how to deal with CSS which wouldn't be necessary in Vue because of the composition API and scoped CSS. I totally agree with you!
Luckily I am the UI architect at our company and I was able to choose Vue. When I first started using Vue I found it harder than React since the ecosystem was smaller and it was harder to find things like a good data grid. But now I can find everything I need. The speed of development, ease of use, and collaboration benefits were what convinced me. We can have the graphic designers write HTML code and then grab their code and convert it to components easily without a JSX conversion step. I can honestly say we have had zero complaints with the Vue apps. They work flawlessly even in IE11. Looking forward to migrating apps away from mixins and towards using the composition API for cleaner and more manageable code.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think it's time we start considering our options the next time we are starting new projects. Too often I see projects going with React because "it has the most job listings, so it must be the best choice". Maybe there is a better solution out there π
I totally agree. Someone once told me, βcompanies like React, developers like Vueβ which is quite interesting. I love Vue for its clear separation between HTML, CSS, and JS in projects. I canβt go back to React anymore with JSX π
Haha, that's a funny and interesting take on it π Because of this I'm doing Vue in my free time and React at work. There's a lot of debate about state management and how to deal with CSS which wouldn't be necessary in Vue because of the composition API and scoped CSS. I totally agree with you!
Luckily I am the UI architect at our company and I was able to choose Vue. When I first started using Vue I found it harder than React since the ecosystem was smaller and it was harder to find things like a good data grid. But now I can find everything I need. The speed of development, ease of use, and collaboration benefits were what convinced me. We can have the graphic designers write HTML code and then grab their code and convert it to components easily without a JSX conversion step. I can honestly say we have had zero complaints with the Vue apps. They work flawlessly even in IE11. Looking forward to migrating apps away from mixins and towards using the composition API for cleaner and more manageable code.