As a React developer I have yet to hear a compelling reason to use Vue. Most of the time it seems like the Vue defender was just looking for the next hot thing and would have used literally anything else, didn’t understand that React is just a library and conflated it with the React ecosystem, or couldn’t wrap their head around FRP. From a business standpoint I can’t understand why you’d put anything on Vue unless th…
How we do Vue: one year later (2017)
111–120 of 159 posts
Re: How we do Vue: one year later (2017)
#112Earlier quoted context omitted.
Sorry to hear you've had troubles in React community! Do you have any examples of places where people haven't been polite or helpful? Your feedback is appreciated.
This is quite a while ago now. I have no examples because it was a 1 off thing when I was learning and it just left a sour taste in my mouth, I believe it was in gitter. I didn't know react has discord now though. So I'll have to join that as we've got a new react project at work (even tho I wish we were using Vue). The angular gitter is worse. On their gitter I asked about some performance issues and was told I was…
If there’s negative behavior from those communities or if they’re not moderated well we’d love to be alerted so that we stop sending people there. What you went through with that gitter chat sounds horrible!
Re: How we do Vue: one year later (2017)
#113Earlier quoted context omitted.
I've always found Redux to be an overcomplicated mess, whereas Vuex is quite simple and has a nice, logical flow. For those who think it's still too complex, I've heard that Pathify https://davestewart.github.io/vuex-pathify is a great solution.
I regret every line of Redux boilerplate I ever wrote before discovering MobX. MobX is now even more fantastic with the new proxy based implementation. Reading up on VueX.. Not really looking forward to having to use it over MobX.
Re: How we do Vue: one year later (2017)
#114Earlier quoted context omitted.
Vue's templating engine, honestly, seems somewhat poorly thought-out. The usual way of writing it errs on the side of HTML over JS, using quote marks awkwardly to enclose a statement rather than JSX's more sensible curly brackets. It makes it harder to visually parse, and it's sometimes annoying to not be able to use one type of quote marks unescaped within the statement. Overall, this is one of many ways in which Vu…
> rather than JSX's more sensible curly brackets I'm still waiting for the 2019 equivalent of http://haml.info/
Some examples here: https://reagent-project.github.io/
It's not haml, but I'd argue it's awesome.
Re: How we do Vue: one year later (2017)
#115Earlier quoted context omitted.
You say "revolving" as if users have been forced to move from one to the other, but all three are current and legitimate choices, no?
angular.js is not a viable choice anymore (no clear statements of how long it's going to be supported), causing huge migration costs for everyone involved.
Re: How we do Vue: one year later (2017)
#116I echo the issues with the attribute syntax. I found marshalling data from the server into components to be painful. I ended up with the following:
For enhancing existing server-rendered apps, is there a better story for passing data into components?Re: How we do Vue: one year later (2017)
#117Re: How we do Vue: one year later (2017)
#118While Vue has a big ecosystem, it's still a fraction of React's. And this is probably the most important thing about React: The ecosystem is so huge, that you have choice, strong competition between lib authors and at the end of the day often or usually superior products. You hate redux? Me too, but there are literally dozens of competitors or wrappers out there + React's own Context and Hooks which bring you quite far. You want a UI lib? There was guy on Reddit testing 40 UI kits for React. Animation? A dozen good ones plus one major one. E.g. I was looking for a page-transition lib for Vue for cross-fading page transitions (real cross-fading where pages blend into each other), I found nothing, just one which can do page-transitions but not real cross-fading (fade-out and then fade-in of the new page). Not that just that vast amount of libs makes life easier, there are so many people you can ask, React got the lingua franca of frontend.
Another thing I like is the actual (small) API of React. It's low-level and if you are stuck, you know quickly what the problem is. React shines also re maintainability , if I enter my biggest and quite complex React app after months I still know where to go and how things work.
Finally, the React team and how they manage issues is amazing. Their thoughts, their chosen architecture, their communication is far beyond many other maintainers on Github. You ask stupid questions in an issue, often Dan answers himself, always super friendly and helping out.
Once you passed the first weeks, I realized what smart architecture React has, that it never stands in my way. Just the fact that I am always and 100% in JS makes things so much easier.
Re: How we do Vue: one year later (2017)
#119I wrote this article back in 2017. A lot has changed since then. If anyone has any questions I'd be happy to answer them. We now use Vue in our data science startup meltano.com.
Have you done any work with Vue and Typescript? We're just starting out with Vue. But my understanding was that TypeScript is a first class citizen in the new version of Vue.
Re: How we do Vue: one year later (2017)
#120Earlier quoted context omitted.
Have you done any work with Vue and Typescript? We're just starting out with Vue. But my understanding was that TypeScript is a first class citizen in the new version of Vue.
You just need 2 libraries, then it becomes really good: vue-class-components and vuex-module-decorators.