Why we chose Vue.js over React • Hacker News Board

Re: Why we chose Vue.js over React

#151

Post by floriferous » Sun, Dec 11, 2016, 8:52 PM UTC

guntars wrote: post #65

The arguments against JSX and React requiring many small components are very surface level and sound like "we couldn't figure out how to make it work for us so it must be impossible". 1. This was mentioned already, but, yes, you can use ternaries and boolean logic for simple conditionals (loggedIn && Logout || Login ) 2. When you need more markup, put them in an if-else statement in the same render function. render()…

Not sure I understand your 3rd pattern, what does const {LoginForm} = this; do?

Re: Why we chose Vue.js over React

#152

Post by rukuu001 » Sun, Dec 11, 2016, 8:53 PM UTC

jolux wrote: post #43

I hope I don't get downvoted for asking this but is React going out of fashion already? A lot of the talk about it was "React is here to stay" or "React is as permanent as JS itself" but now this is the second or third time people seem to be going for Vue instead. What happened?

Facebook is heavily invested in React, so even if the JS fashion industry moves on from it, React isn't going anywhere.

Re: Why we chose Vue.js over React

#153

Post by shams93 » Sun, Dec 11, 2016, 8:55 PM UTC

welanes wrote: post #11

One of the most impressive thing about Vue.js was the ability of the framework to enter a field saturated with dozens of options, that was becoming dominated by a well-resourced oligopoly (Angular, React), and still win over developers jaded from Javascript-fatigue. The give-a-shit factor from Evan (the creator) is extremely high and was key to its success. Inspiration for anyone building a product in an established…

He also has wonderful documentation, and the framework itself makes it easy to move code over from angular 1.x. The give a shit factor is huge when you look at the quality of documentation and the website organization. Just telling people to "read the code" doesn't cut it, Even hit a home run with the quality of his project website and documentation.

Re: Why we chose Vue.js over React

#154

Post by mateuszf » Sun, Dec 11, 2016, 8:57 PM UTC

SonicSoul wrote: post #139

dismantlethesun wrote: post #128

Earlier quoted context omitted.

I think what he means is that control statements don't exist in JSX. You have to write Javascript to do if-statements, looping, etc. In React, there is no 'direction' of binding---its all one way, just like in vanilla Javascript, and in fact no binding on anything except low level elements' like divs. Components only receive props, which do not do anything at all until you write code that reads them and runs operatio…

i don't see how sprinkling if-statements in your html is cleaner than "magical attributes" but thats just me :)

if statement is one of the most basic concepts of programming and is opposite to magic

Re: Why we chose Vue.js over React

#155

Post by Ralfp » Sun, Dec 11, 2016, 8:59 PM UTC

irrational wrote: post #125

danabramov wrote: post #92

Earlier quoted context omitted.

I wouldn’t say React is “hacked together”. Perhaps you are referring to the React ecosystem? Facebook doesn’t build single-page apps with React, so naturally it doesn’t provide solutions for routing and similar concerns, so there is more churn as people are figuring this out together.

Wait, do people use React for non-SPA websites?

Yep! I find myself using React.js for complex forms/wizards on non-SPA websites far more often than using it to build SPAs.

Re: Why we chose Vue.js over React

#156

Post by codegeek » Sun, Dec 11, 2016, 9:01 PM UTC

rmason wrote: post #149

One small point to add here. Evan You is a pretty amazing individual, but he is no longer alone. There is a core team of six members. I know because the guy who got me interested in Vue.js, Chris V. Fritz, lives in the Lansing, Michigan area and is responsible for the excellent docs on Vue. I haven't been able to locate a list online but I know there's a core member in Paris and another one in Japan.

Other than Evan, could this be the list ?

https://github.com/orgs/vuejs/people

Re: Why we chose Vue.js over React

#157

Post by phpnode » Sun, Dec 11, 2016, 9:02 PM UTC

irrational wrote: post #125

danabramov wrote: post #92

Earlier quoted context omitted.

I wouldn’t say React is “hacked together”. Perhaps you are referring to the React ecosystem? Facebook doesn’t build single-page apps with React, so naturally it doesn’t provide solutions for routing and similar concerns, so there is more churn as people are figuring this out together.

Wait, do people use React for non-SPA websites?

Of course, hence the focus on server-side rendering. It is quite difficult to do properly though. Facebook itself is not a single page application.

Re: Why we chose Vue.js over React

#158

Post by pacnw » Sun, Dec 11, 2016, 9:03 PM UTC

agumonkey wrote: post #147

pacnw wrote: post #54

I've used Vue pretty much daily over the last year in a fairly complex app (some 150+ components, Vuex store with 100+ actions, full client side router navigation) and it has been pretty pleasant. I even contribute a nominal amount to the Patreon campaign. However, the upgrade path from v1 to v2 is not a quick undertaking. Certain changes require a revisit to practically all components (e.g. change of 'ready' to 'mou…

I just heard about vuex, any curated resources about it ?

The main Vuex docs are quite good, with the included shopping cart example. https://vuex.vuejs.org/en/

Re: Why we chose Vue.js over React

#159

Post by s_kilk » Sun, Dec 11, 2016, 9:04 PM UTC

jolux wrote: post #43

I hope I don't get downvoted for asking this but is React going out of fashion already? A lot of the talk about it was "React is here to stay" or "React is as permanent as JS itself" but now this is the second or third time people seem to be going for Vue instead. What happened?

We've already been through this in the last few years with Angular.

Anyone who believes their current hot framework is "as permanent as JS itself" is kidding themselves.

Re: Why we chose Vue.js over React

#160

Post by orange888 » Sun, Dec 11, 2016, 9:05 PM UTC

mos_basik wrote: post #138

lilactown wrote: post #109

Earlier quoted context omitted.

I think that, similar to how everyone realized that jQuery wasn't the right tool for certain problems, people are coming to the conclusion that Angular and React+[Flux/Redux/MobX/etc.] isn't always the right tool for certain problems as well. And I think that Vue.js fills the needs for those problems very well. The truth is, the majority of the work I've done in React for my job on the web would have been much better…

You are On. The. Money. When I first started dabbling in web programming a few years ago, I quickly learned about jQuery from SO while looking up common patterns to create the behaviors I wanted in the browser. But even accounting for my unfamiliarity with the browser paradigm, jQuery always rubbed me the wrong way because of how loosely structured it allowed you to be and the amount of leaky scope it encouraged. I f…

Vue is a frontend framework. jQuery is a library, with a very specific goal (DOM access)

What happened when you were using jQuery, is you created your own homegrown "framework" on top of it. Thats what you should be comparing Vue with, not jQuery.