121–130 of 177 posts
Good assessment. To summarize the argument, Vue.js is just as good and some would argue better than React for web development, but the React ecosystem really puts it over the top, especially React Native.
Having used both React (with Typescript and Redux) and the latest Vue (with es6 and Vuex) I prefer React, and I don't even use React Native. Vue is better for onboarding people more in tune with "classic" html + js development; and that's where the advantages end as far as I'm concerned. This might be a big win for some people. The way I reason about it is that React is simple, Vue is easy. When you take into account…
[0] https://github.com/NetCoreTemplates/vue-spa
[1] https://github.com/NetFrameworkTemplates/vue-spa-netfx
Vue is also currently our most popular .NET Core 2.0 SPA Template, followed by React.
Earlier quoted context omitted.
Speaking as someone who writes ClojureScript themselves, ClojureScript is definitely in the category of technologies that show no sign of explosion whatsoever. React and Vue are both great technologies, but with Teact the template syntax is optional, and no lisp user wants another syntax...
I picked up ClojureScript at the end of 2013. I was a C++ developer then in a small firm and was tasked to write a web frontend. Outsourcing that project had failed before (2 times iirc), so my boss bet on me to do it. I knew HTML and had written probably Last year I had another look at ClojureScript and it felt like a ghost town. This saddens me. There are a few inspiring talks now and then, but nothing I found wort…
Earlier quoted context omitted.
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 perfo…
1) I've been using React for 4 years and never used observables, what do you mean? 2) Please clarify what you mean by this. 3) By all accounts, the fiber codebase is much simpler than the stack codebase, performs similarly and opens up some exciting new possibilities.
Personally, I am super jealous of angular for having observables. I work with React and would love some Rx in our app too, but we aren't using it. Ditto for typescript - our app is mostly untyped javascript with sprinkles of Flow, while angular would have enforced typescript.
Earlier quoted context omitted.
vue wouldn't even exist if react had not paved the way first
Not true - Ractive is a library much like vue on the surface that came out _before_ React. It's all about timing, promotion and hitting a feature sweet spot.
MVVM was a thing for like that six month period in 2012 when backbone.js was causing callback hell and React.js hadn't come out yet, MVVM is an attempt to abstract over the callbacks.
Having used both React (with Typescript and Redux) and the latest Vue (with es6 and Vuex) I prefer React, and I don't even use React Native. Vue is better for onboarding people more in tune with "classic" html + js development; and that's where the advantages end as far as I'm concerned. This might be a big win for some people. The way I reason about it is that React is simple, Vue is easy. When you take into account…
This is a positive thing imo. It's a declaration of your data schema. You can reference it to remember what kind of data you're working with. This gets rid of unproductive moments like "What was the name of this property again? Is this property an object or an array? Is it nested inside this object or that object?"
I guess it is just how my "programming mind" thinks about problems. I am sure developers who approach problems differently may enjoy React more, but for me, I guess I am a lot more old fashioned and 'structured' in the way I see things.
React changing their license probably saved them. My web dev office was going to transition from them until they changed it.
- In 2016:
React - 91% satisfaction
Vue - 91% satisfaction
Angular 2 - 65% satisfaction
No framework - 65% satisfaction
Ember - 50% satisfaction
Angular - 40% satisfaction
Backbone - 31% satisfaction
- In 2017:
React - 93% satisfaction
Vue - 91% satisfaction
Angular 2 - 66% satisfaction
No framework - 65% satisfaction
Aurelia - 56% satisfaction
Polymer - 53% satisfaction
Ember - 41% satisfaction
Angular - 33% satisfaction
Backbone - 23% satisfaction
It's especially interesting that many of the frameworks have a lower satisfaction percentage than using "no framework". Of course this could be largely attributed to who is using no framework. I have encountered a minority of developers (usually backend devs) who think front-end frameworks are nonsense and prefer to just write a bunch of jQuery. Also, if you are working on Wordpress sites, then frameworks are often not necessary.
I've written production code in some of these frameworks (Backbone, Angular 1, Ember, and React) and I would have to say these results are more or less consistent with my experience. I love React and don't feel the need to try anything else.
Earlier quoted context omitted.
What is a turbolink?
Yes, sorry for just tossing this one in there. Our product is build on top of rails 5.x, and rails has support for turbolinks. They make your server-side rendered application 'Feel' more SPA, by only refreshing the parts of the page that have actually changed upon server response. It still requires a massive payload to be sent across the wire, as well as a full render on the server, so it's not the "king of efficienc…
I'm learning Rails and haven't gotten to that stuff yet, but I'm wondering whether I should even waste my time learning them if something like Vue is just superior and just as easy to implement.