I’m the founder writing code (but not the only technical person) for my three person startup. In October I started migrating our MVP from server side templates to Vue, given we had direction and traction on a product line that justified the time investment. It’s turned out to be a great decision (although likely one that could have been made with react as the choice as well). My “success story” is how Vue helped me t…
What is a turbolink?
Vue.js vs. React: what happened in 2017
21–30 of 177 posts
Re: Vue.js vs. React: what happened in 2017
#22I write ClojureScript
A good indicator of if a technology is going to explode, is if emerging language users are excited about it, as good ideas tend to trickle down from the more advanced/research-y ecosystems which aren't as constrained by legacy. So for example React was built by a user of OCaml.
ClojureScript early adopted React.js through the Om project in 2013 and there is a growing number of competing React adapters, Clojure rewrites etc. I first saw virtual-dom in ClojureScript in 2012 (eight months before React came out).
Number of ClojureScript projects with traction that are based on vue? Zero, that I am aware of.
Re: Vue.js vs. React: what happened in 2017
#23I’m the founder writing code (but not the only technical person) for my three person startup. In October I started migrating our MVP from server side templates to Vue, given we had direction and traction on a product line that justified the time investment. It’s turned out to be a great decision (although likely one that could have been made with react as the choice as well). My “success story” is how Vue helped me t…
What is a turbolink?
Haven't used it, but it seems to avoid a full page reload but still does a round trip:
Re: Vue.js vs. React: what happened in 2017
#24I think both of them are awesome and have great communities. Especially seeing as webpack has stabilized.
If you're a startup, it's tempting for many founders to go in headfirst with a Vue or React. In my opinion, it's rarely necessary, and in the end a lot of the stuff has to be thrown out if underlying foundations change. I see it as web development's version of premature optimization.
On the other hand, when I kept all my work in django templates, erb, blade, etc. and just script JS by hand, there's less of a penalty when the data flow changes. When I was using a JS framework, the refactoring was so painful I seriously considered throwing the whole thing out and starting from scratch. Heh, I'd have been better off not buying in so early on.
As a stop-gap, I'm using pjax. (https://github.com/defunkt/jquery-pjax)
My plan is after stuff is solid and in production and the product/service/business is moving forward, taking an incremental approach to moving to vue/react/etc.
P.S. kudos to react for removing the patent stuff in v16.
Re: Vue.js vs. React: what happened in 2017
#25I'm afraid React is eventually turning into Angular. At some point, I felt that Angular is somebody's PhD work exploring arcane computer science concepts, not a piece of software for practical use. React gets closer to that with each year.
Can you mention a few examples?
Re: Vue.js vs. React: what happened in 2017
#26I'm afraid React is eventually turning into Angular. At some point, I felt that Angular is somebody's PhD work exploring arcane computer science concepts, not a piece of software for practical use. React gets closer to that with each year.
Can you clarify that comment? What aspects of React's development are you concerned with?
First, probably was their approach to implicitly require use of Observable objects everywhere.
Second, use of arcane CS lingo and authors writing 10 pages long pages on every known MVC model, FLUX, SCHMUX and etc with weekly regularity.
Third, during transition to Fiber, they went on gigantic increase of complexity by introducing a lot of what can be said to be heuristic rules, and all for non-guaranteed, minor performance gain.
Re: Vue.js vs. React: what happened in 2017
#27[deleted]
Re: Vue.js vs. React: what happened in 2017
#28I see a lot of commits from the Vue team into the core repo that are meant to support use in native. Likely, we can expect something comprehensive for native this year. I also believe it's a smart strategy to avoid Facebook codebases because they are all meant to somehow benefit FB in some (usually dubious) way. Also the Vue approach is 1000% cleaner in practice than React, just doesn't have the bandwagon effect goin…
My typical use case doesn't need native apps - a PWA is good enough for me. I will not comment on speculation about the compile-to-native feature because personally it is irrelevant. I can say that as you I prefer Vue over React and some of my personal reasons are: * I like opinionated frameworks * I don't like to mix Javascript and HTML - I can handle a Vue template to any designer but I would not trust a JSX file t…
PWA is not good enough for us due to heavy usage of mobile device camera and picture resizing (client side) for package receiving process in the warehouse. PWA fails to provide consistent performance in such conditions, and issues with bluetooth scanners in Safari/PWA on iOS devices add up. Other than that, I agree Vue.js is superior to React in a lot of use cases, especially for web.
Re: Vue.js vs. React: what happened in 2017
#29When it comes to UI need to start thinking past Framework A vs Framework B.
There is already a browser-native compatibility layer known as the Web Components API that allow components rendered by different frameworks to work together, so we won't ever have to be stuck in Framework A or Framework B and can migrate in agile manner (one component at a time) from one to the other or whatever new framework may come next year. I agree Web Components have some major warts and DX issues but libraries like SkateJS and others help smooth those out.
Copying from Readme my WIP project that uses Skate:
"SkateJS allows us to export components rendered by React, Angular 2, 4, Vue, and other modern composition-oriented frameworks as W3C Custom Elements and compose those Custom Elements into higher order Custom Elements with data flowing from parent to descendants and so on.
With SkateJS we can have an Angular 4-rendered Form custom element composing Angular 2-rendered input and selection custom elements, or the other way around with Angular 2-rendered Form custom element composing Angular 5 --and Angular 4-- rendered input and selection custom elements.
SkateJS also provides a Router that is framework agnostic. Only the rendering part of any framework (Angular, React, Preact, Vue, et al) is ever used.
This way we can build SkateJS-based reusable component libraries using any version of Angular (> 2), React, Vue et al and be able to use those components in our SkateJs-based site together, including via composition, and be able to upgrade our app (when a new version of React, Angular or Vue et al comes out) one component at a time, in piecemeal fashion as in iterative agile development, as opposed to having to do it all at once, as in waterfall development, which is almost always an unrealistic approach. This works because our components are essentially all custom elements regardless of rendering library we use (different versions of Angular, React, Preact, Vue, et al)"
Re: Vue.js vs. React: what happened in 2017
#30I see a lot of commits from the Vue team into the core repo that are meant to support use in native. Likely, we can expect something comprehensive for native this year. I also believe it's a smart strategy to avoid Facebook codebases because they are all meant to somehow benefit FB in some (usually dubious) way. Also the Vue approach is 1000% cleaner in practice than React, just doesn't have the bandwagon effect goin…
My typical use case doesn't need native apps - a PWA is good enough for me. I will not comment on speculation about the compile-to-native feature because personally it is irrelevant. I can say that as you I prefer Vue over React and some of my personal reasons are: * I like opinionated frameworks * I don't like to mix Javascript and HTML - I can handle a Vue template to any designer but I would not trust a JSX file t…
The one reason why I favor Vue more than React is:
* Vue downscales. If you have a single scripted component in a page, you will get a simple page, with a small amount of Vue added.