1. 9
  1.  

  2. 10

    The Vue community hangs out on Discord, a chat designed for gamer communities. If you hit a roadblock the chat is probably your best bet since the official forums are a desolate land, and don’t you dare ask a question on Github.

    Chats are messy, but the main problem is that chat content can’t be indexed by search engines. The same questions (and its related discussions) are doomed to be repeated again and again and again.

    This trend of using chats for questions is plaguing open source projects and I think it needs to end. There is no collective learning anymore.

    This is a very good point that extends outside of this javascript community. The GH crowd seems to be very into tools like Gitter, Discord and Slack, which don’t provide the same persistent knowledge-base, are user-hostile, aren’t FOSS (if you care about that) and demand your attention – on both the contributor and user side. Reading through a chat or searching through the logs and trying to gain context from a past conversation doesn’t provide comparable value to a wiki, website, or even just reasonable documentation.

    1. 9

      After 2 years my experience with Vue has been positive. I’m still confident it was a good decision to move my team from React to Vue. Not because Vue is better, but because it is a better fit for us.

      Why though? These comparisons of libraries/frameworks that amount to “differences of technical details” are not worth writing. Did the author have some problem that couldn’t be solved with React and could be solved with Vue? That would be worth hearing about. I’m talking real business-value-added problem solving. Not “the syntax is nicer”. If I was employing this author and read this article, I would feel like the migration from React to Vue had been a waste of company resources.

      1. 1

        Well ultimately they are both Javascript frameworks, so what you can do in one you can do in another, the whole idea of a framework is the syntax in which you interact with it to the base language. As such, some things will be easier in framework X and other will be easier in framework Y. In my opinion you have the Angular way to solve JS “framework projects”, then the React way, Vue sits a bit in the middle (if not closer to React).

        1. 2

          what you can do in one you can do in another

          If I’m already using a tool that can do what I need it to do, why would I invest in a new tool? And I don’t mean to reduce things to “it’s all JavaScript so you don’t need a library”. React, Angular, Ember, Vue, etc., are compelling to me to the degree that they enable a developer/organization to deliver useful software. But if React and Vue are compelling to the same degree, I’m not sure there’s anything to talk about.

        2. 1

          Author here.

          The article was getting pretty long already and I didn’t want to get into those points.

          Did the author have some problem that couldn’t be solved with React and could be solved with Vue?

          There were 3 major paint points for us with React. That was in 2015-2016, at the end of 2016 we moved to Vue.

          1. JSX is ok for JS devs, but terrible for designers that work with HTML and CSS. We tried to solve that using a Wix library called react-templates but it introduced its own set of problems.

          2. React Router was cumbersome compared to Vue Router. For example if you need to access the router from a component you needed to create a HOC. We also hit a bug that could only be solved by using setTimeout() with 0 delay. We quickly found that the React Router team was not very welcoming to feature requests or bug reports, to put it mildly. Vue Router in comparison made a lot more sense and was much easier to deal with.

          3. Managing local state compared to Vue is tedious. We considered moving to MobX, which is what a lot of React guys are doing, but at that point I gave Vue a try and it was immediately clear that it was a better fit for us.

          If I was employing this author and read this article, I would feel like the migration from React to Vue had been a waste of company resources.

          We didn’t rewrite our React projects to Vue, if that’s what you are implying.