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

Why we chose Vue.js

about.gitlab.com

Post reply on HN
Print view View original

61–70 of 282 posts

Re: Why we chose Vue.js

#61

Post by rtpg »

greyskull wrote: post #12

There's something that irks me about incorporating logic into templates. UI development is hard enough without having to bounce between js and templates to figure out how a component is actually going to behave. I haven't used Vue or React, so this is all just my gut speaking, but at least with React all the logic is there in front of you. In my mind, if there's a loop or a conditional or whatever piece of logic that…

If you're thinking about the difference between data and presentation, then you can usually limit the damage caused by "logic in templates"

Though you might want to precompute some values in your data to make the presentation code cleaner, of course.

It's also important to make things as "component"-y as possible. This is an instinct we don't have when doing HTML stuff by default, because the language itself isn't really used like that in "normal" development.

So you have your data, and then your template ends up being pretty minimal in logic, leaving just some core bits that are purely presentational.

For example:

    
 Your Transactions 


    
      
    
    
      
 Please configure your transactions here

Re: Why we chose Vue.js

#62

Post by j1436go »

megalomanu wrote: post #51
kimshibal wrote: post #13

Earlier quoted context omitted.

Our company migrated to vue.js, 4 months ago. Our complex app is messy with JSX, router, and new dev can't keep up with code. Now we start every new app with Vue.js. The gap between junior dev and senior dev comes closer. They can collaborate with less bugs, less problems and less time to develop.

New React projects are today much simpler, thanks to new libraries to manage state like Mobx, or efficient starter kits. So without denying the benefits you encounter with the migration to Vue.js, I think that a full rewrite of you React app in "modern React" would have been a good thing too.

And how long until the next "modern React" will land? That's what drove me away from React.

Re: Why we chose Vue.js

#63

Post by thegeekpirate »

lossolo wrote: post #31
gregmac wrote: post #11

I do very little web these days, mostly working on backend data processing, network I/O and distributed comms. A bit over a year ago, I wanted a real-time web UI to visualize some of the data I had on server-side, which I was trying to do using SignalR. I went back through some of the popular frameworks, with a pretty simple mindset of "Can I read the 'getting started', and get something basic working in about 15 min…

I have almost the same experience as you. I am maintaining big Ember app and have exactly the same problems as you described with it.I am interested in Vue lately also because it's so lightweight, easy, well structured, documentation is excellent, ecosystem around it is excellent and i have so much more freedom than in Ember. Author really cares about it, issues on github shows that, only 50 open and 3000 closed.

50 open, but only 9 of them are actual bugs!

Re: Why we chose Vue.js

#64

Post by thegeekpirate »

pjungwir wrote: post #57

Can anyone compare Vue with Knockout? In the early days of Angular etc I saw a lot of people saying they chose Knockout, and were much happier than with one of the heavier frameworks. I found its simplicity very appealing too, but it seems clear now that it's not a mainstream choice. It feels to me like a dead end. The last time I looked (a year ago?) the semi-official data mapping extension had lost its maintainer.…

https://vuejs.org/guide/comparison.html#Knockout

Re: Why we chose Vue.js

#65

Post by [deleted] »

pjungwir wrote: post #57

Can anyone compare Vue with Knockout? In the early days of Angular etc I saw a lot of people saying they chose Knockout, and were much happier than with one of the heavier frameworks. I found its simplicity very appealing too, but it seems clear now that it's not a mainstream choice. It feels to me like a dead end. The last time I looked (a year ago?) the semi-official data mapping extension had lost its maintainer.…

[deleted]

Re: Why we chose Vue.js

#66

Post by ggregoire »

kentor wrote: post #32

After using React, I am firmly in the #nevertemplates camp. I don't ever want to learn a template DSL again when I could be using the full power of javascript.

Same here. In my opinion JSX is one of the best thing happened in the front-end world.

Let's not forget how horrible Angular templating was:

    
        
            {{::item.name}}

Re: Why we chose Vue.js

#68

Post by megalomanu »

j1436go wrote: post #62
megalomanu wrote: post #51

Earlier quoted context omitted.

New React projects are today much simpler, thanks to new libraries to manage state like Mobx, or efficient starter kits. So without denying the benefits you encounter with the migration to Vue.js, I think that a full rewrite of you React app in "modern React" would have been a good thing too.

And how long until the next "modern React" will land? That's what drove me away from React.

Before, React projects evolved because they have to. They became too complex, to clumsy, etc. But now ? React is stable, the way to develop apps is well known, etc.

Re: Why we chose Vue.js

#69

Post by nailer »

kentor wrote: post #48
Yaggo wrote: post #39

Earlier quoted context omitted.

So what is JSX if not DSL? (Yeah, you can use React without JSX, but still.)

You can think of it as sugar for `React.createElement()`, and some other stuff (like spread) but that's it. It's really easy to translate into javascript in your head. Why is this good? 1. Let's say I want to stick a debugger in my template or render function. How would you do it in Vue? Angular? I don't know, gotta look it up, not even sure if possible. How would you do it in React? I don't have to look anything up,…

I use ractive, which uses a virtual DOM and simple mustache templates. I'd use a ractive expression to do the debugging.

People seem to think using a familiar templating language excludes using the full power of JavaScript. It doesn't.

Re: Why we chose Vue.js

#70

Post by pvorb »

megalomanu wrote: post #58

As a primarly backend dev, I'm very comfortable with React and I don't particularly want to switch to Vue.js. React says me : learn the HTML basics and then deal with abstractions (proof: React Native !). Vue.js says me : deal with HTML templates, everytime, everywhere. Although we even end to deal with HTML in React, I think it's easier for a backend dev with no front experience at all to grasp it. I showed React to…

I keep hearing React reminds Java devs of JSF. But I've never heard it as a compliment.
Post reply on HN