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

Vue.js 1.0.0

vuejs.org

Post reply on HN
Print view View original

51–60 of 89 posts

Re: Vue.js 1.0.0

#51

Post by RobertoG »

girvo wrote: post #38
andrewray wrote: post #23

I've always heard good things about Vue from its users. I have to compare all Javascript frameworks to React, because to me React feels like the first framework that got it "right." The API of React is surprisingly thin. Looking at Vue templates, the syntax seems quite alien, halfway between Django and Angular: And the API seems to needlessly separate HTML and Javascript, with some strange (to a newcomer) API calls:…

I've written large apps in both; interestingly, I've built the same app twice as well: once in Vue.js and once in React. I'm also in the process of building another very large front-end in Vue.js at the moment. The big thing is that while I personally adore React, it does require ceremony to get stock-standard behaviour. We recently onboarded a new developer (a friend of mine), and teaching him React + Flux (Alt.js)…

"and teaching him React + Flux (Alt.js) "

Can I ask what do you use for routing and if you have good results with that mix?

Re: Vue.js 1.0.0

#53

Post by xixixao »

twsted wrote: post #37

I like it. In fact I like it more than React, which I am not using (still a happy Backbone user). A thought that I share, from the guide: "API-wise, one issue with React (or JSX) is that the render function often involves a lot of logic, and ends up looking more like a piece of program (which in fact it is) rather than a visual representation of the interface. For some developers this is a bonus, but for designer/dev…

It is a trade off. It is easy to implement any logic with React. Simple databinding works well until you need that logic.

Re: Vue.js 1.0.0

#54

Post by mercer »

oweiler wrote: post #52

This one looks very similar to Ractive http://www.ractivejs.org/ Which isn't a bad thing :).

Could someone tell me a bit about how the two differ? I've built a decently-sized app with Ractive.js and really like it, and I might be working on an app soon where either Ractive.js or Vue.js seem like a good option.

From what I've gathered so far, Vue seems like it is basically a better Ractive, and it makes more sense to use it for my next project. But perhaps I'm missing some important differences between the two?

Re: Vue.js 1.0.0

#55

Post by girvo »

RobertoG wrote: post #51
girvo wrote: post #38

Earlier quoted context omitted.

I've written large apps in both; interestingly, I've built the same app twice as well: once in Vue.js and once in React. I'm also in the process of building another very large front-end in Vue.js at the moment. The big thing is that while I personally adore React, it does require ceremony to get stock-standard behaviour. We recently onboarded a new developer (a friend of mine), and teaching him React + Flux (Alt.js)…

"and teaching him React + Flux (Alt.js) " Can I ask what do you use for routing and if you have good results with that mix?

Interestingly, we're using our "own" router that I wrote in a fit of frustration; it's tiny, not particularly well documented and has the interesting design choice of handing the route matching on to the user of the library; give each component a name and have your route matcher callback return that name and you're good to go.

The reason why I went down that route (pun intended) was that we built a rather large, isomorphic/universal web application that for SEO reasons had to act like a website vs a web app most of the time; until it started up the client side JS anyway. "react-router-component" was so close to what we wanted, but because it used React's somewhat undocumented "context" feature, it didn't play nicely with our Flux implementation at the time (Flummox).

For that reason, my tiny router came into being, and for some reason it keeps sticking around despite my best efforts...

https://github.com/studionone/react-isorouter

Ps. I just found out that the README links to non-existent documentation, I really should fix that...

Re: Vue.js 1.0.0

#56

Post by e12e »

andrewray wrote: post #23

I've always heard good things about Vue from its users. I have to compare all Javascript frameworks to React, because to me React feels like the first framework that got it "right." The API of React is surprisingly thin. Looking at Vue templates, the syntax seems quite alien, halfway between Django and Angular: And the API seems to needlessly separate HTML and Javascript, with some strange (to a newcomer) API calls:…

> I have to compare all Javascript frameworks to React, because to me React feels like the first framework that got it "right."

Have you looked at riot.js?

[r] http://riotjs.com/

Re: Vue.js 1.0.0

#57

Post by girvo »

girvo wrote: post #38
andrewray wrote: post #23

I've always heard good things about Vue from its users. I have to compare all Javascript frameworks to React, because to me React feels like the first framework that got it "right." The API of React is surprisingly thin. Looking at Vue templates, the syntax seems quite alien, halfway between Django and Angular: And the API seems to needlessly separate HTML and Javascript, with some strange (to a newcomer) API calls:…

I've written large apps in both; interestingly, I've built the same app twice as well: once in Vue.js and once in React. I'm also in the process of building another very large front-end in Vue.js at the moment. The big thing is that while I personally adore React, it does require ceremony to get stock-standard behaviour. We recently onboarded a new developer (a friend of mine), and teaching him React + Flux (Alt.js)…

Apologies for the formatting, I forgot about the rather greedy behaviour of italics on HN!

Re: Vue.js 1.0.0

#58

Post by muraiki »

piotrkaminski wrote: post #25

I'd love to see a comparison of Vue.js with Aurelia ( http://aurelia.io/ ). In my mind, Vue.js and Aurelia are the two front-runners for the next "right-weight" framework (whereas React is the lightweight champion, and Angular 2 likely to be the heavyweight winner by default).

I'd also like to see this comparison. Last year I came close to using React, but picked Knockout because React was fairly immature at the time. I'd like something a bit more "right-weight" and am interested to see what Aurelia's author has done (he made a larger framework based on Knockout). I really like that Aurelia is embracing upcoming standards like web components, and it looks like Vue is also doing the same. Aurelia also seems to be designed with TypeScript in mind, which is a big draw for me as sometimes some common Javascript patterns are awkward to deal with in TS.

Also, by "right-weight" I think this is meant in terms of API and features, not file size. Sorry, but I don't think that bringing up the file size of various other frameworks is that productive of an addition to this thread.

Re: Vue.js 1.0.0

#59

Post by nailer »

mercer wrote: post #54
oweiler wrote: post #52

This one looks very similar to Ractive http://www.ractivejs.org/ Which isn't a bad thing :).

Could someone tell me a bit about how the two differ? I've built a decently-sized app with Ractive.js and really like it, and I might be working on an app soon where either Ractive.js or Vue.js seem like a good option. From what I've gathered so far, Vue seems like it is basically a better Ractive, and it makes more sense to use it for my next project. But perhaps I'm missing some important differences between the tw…

Ractive uses mustache templates, which I prefer as

- nearly every web developer already knows mustache

- mustache distinguishes what's HTML and what's not

I also like ractive because it has two way bindings, and promises for when DOM changes, but maybe Vue also has those.

Post reply on HN