Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How we do Vue: one year later (2017)

about.gitlab.com

Post reply on HN
Print view View original

61–70 of 159 posts

Re: How we do Vue: one year later (2017)

#61

Post by ilovecaching »

philliphaydon wrote: post #56
ilovecaching wrote: post #42

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…

#1 reason for me? The community. Hands down the community. Vue has such a better community than react or angular by a Long shot. If you ever end up needing help and jump into the discord channel. No matter how annoying you are the entire community is always patient polite and helpful. I can’t say my experience has been close to the same in react or angular.

Have you been on the React discord channel? Acemarke is like 20 people masquerading as a single person. I've never had a bad experience with the React community.

Case in point, any whiff of dissatisfaction and Dan Abramov will comment on your post. Literally can't get any better service than that.

Re: How we do Vue: one year later (2017)

#62

Post by ilovecaching »

Jarwain wrote: post #60
ilovecaching wrote: post #42

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…

The #1 reason for me was how easy it was to pick up vue and start building something quickly. Which probably just has to do with my own background experience working with knockout and html/css/js. It's an easier stepping stone, a more natural progression for me. I think it'd be a lot easier to pick up react now that I'm proficient with Vue.

I felt the same way coming to React from Angular. It's basically just writing functions:

function HelloWorld(props) { return Hello World from {props.name}; }

function App() { return ( ); }

ReactDOM.render( , document.getElementById('root') );

That's pretty much the whole thing.

Re: How we do Vue: one year later (2017)

#63

Post by michaelgof »

Let's be honest Vue is a temporary blimp in web frameworks like all the others. I've been doing mobile dev the last 2 years and React was the hot thing. Then a year before that it was Angular. These things change and Vue is temporary like the others

Re: How we do Vue: one year later (2017)

#65

Post by enraged_camel »

parthdesai wrote: post #32
asdffdsa wrote: post #25

The revolving door of front-end frameworks is somewhat irritating; spending a nontrivial amount of time in Angular (1), then React, and now Vue. I wonder what the next one will be

React and Vue have 6.25 and 1.01 weekly downloads respectively. As of now, they are not even in the same league.

Comparing weekly downloads to measure the popularity of frameworks is like counting lines of code to measure the productivity of developers.

Re: How we do Vue: one year later (2017)

#66

Post by airstrike »

koboll wrote: post #30
keyle wrote: post #14

I write Vue every day, in a large application. Only small bits use VueX. Of all the frameworks I've used, it's brilliant because it hardly takes any thinking away from the business logic, so I'm not bogged down, it stays OUT of my way, and it's rock solid. I HIGHLY recommend it, and this is from someone doing web since 1997.

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/

Re: How we do Vue: one year later (2017)

#68

Post by Rapzid »

koboll wrote: post #30
keyle wrote: post #14

I write Vue every day, in a large application. Only small bits use VueX. Of all the frameworks I've used, it's brilliant because it hardly takes any thinking away from the business logic, so I'm not bogged down, it stays OUT of my way, and it's rock solid. I HIGHLY recommend it, and this is from someone doing web since 1997.

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…

My least favorite part of Vue. Proper intelisense/checking for the templates never materialized either. A start-and-stop effort or two languishing in the Github issues..

I have a feeling after Vue 3 hits and in a couple years JSX will be the defacto way to work with Vue.

Re: How we do Vue: one year later (2017)

#69

Post by geektips »

parthdesai wrote: post #57
KaoruAoiShiho wrote: post #51

Earlier quoted context omitted.

Using NPM stats is just not correct. I believe React to be about 2.5x larger than Vue rather than 6x.

And why would that not be correct, and what are the sources of your number?

Most probably because Vue is enormously popular in China and npm mirrors are mostly used in china.

Re: How we do Vue: one year later (2017)

#70

Post by philliphaydon »

danabramov wrote: post #58
philliphaydon wrote: post #56

Earlier quoted context omitted.

#1 reason for me? The community. Hands down the community. Vue has such a better community than react or angular by a Long shot. If you ever end up needing help and jump into the discord channel. No matter how annoying you are the entire community is always patient polite and helpful. I can’t say my experience has been close to the same in react or angular.

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 "stupid" and "don't do it like that" even tho that's how the documentation showed how to do it, and "you shouldn't be using Angular because you don't know what you're doing". (I was eventually helped in a private chat by someone and resolved the performance issues just changing a few things, but this was driving force to ditch Angular and move to React)

Edit: Also for you to reply with concern does give me more faith that the community may be better than I thought. I appreciate your time to read my comment and reply.

Post reply on HN