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

81–89 of 89 posts

Re: Vue.js 1.0.0

#82

Post by mambodog »

fuzionmonkey wrote: post #45
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).

React 0.14 is 132KB minified [1]. I wouldn't exactly consider React "lightweight," especially compared to other frameworks like Mercury [2], Mithril [3], and Riot [4], which are a fraction of the size of React but still have their own virtual DOM implementations. [1] https://fb.me/react-0.14.0.min.js [2] https://github.com/Raynos/mercury [3] http://mithril.js.org [4] http://riotjs.com/

People usually compare the 'size over the wire', eg. gzipped size. In these terms:

- React 0.14 is 55kb

- jQuery 1.11 is 38kb

- Backbone + Underscore (dependency) are 15kb

Re: Vue.js 1.0.0

#83

Post by gedy »

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…

I've wondered the same, as I really like Ractive. Briefly what I found is:

Vue seems using "magic mode" vs the Ractive.get/Ractive.set. Ractive uses virtual DOM, Vue does not.

Re: Vue.js 1.0.0

#84

Post by girvo »

lhorie wrote: post #71
girvo wrote: post #39

Earlier quoted context omitted.

Mithril runs in IE8+, currently, though that will be changing in the future.

Huh, where did you hear that? I wasn't planning on dropping support for IE8 in Mithril, if possible.

Oh apologies, I read in the Bucket List that it was happening but I just checked and it's only mooted at this point!

https://github.com/lhorie/mithril.js/issues/802

Re: Vue.js 1.0.0

#85

Post by girvo »

RobertoG wrote: post #68
girvo wrote: post #55

Earlier quoted context omitted.

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, isom…

Thanks. I'm trying to find my way around flux but until now has been a little frustrating experience. I wish something like Elm was mature enough.

> I wish something like Elm was mature enough.

So do I :)

If you're not 100% up on Flux, I recommend having a play with Hoverboard[0] -- it's a tiny implementation of the Flux architecture, with some interesting choices itself. It's a single function, too, which is pretty neat!

I've been using it to implement the "Flux Challenge" in combination with domChanger[1] instead of React: https://github.com/girvo/domchanger-hoverboard-flux-challeng...

And here's a partial TodoMVC implementation I wrote in Hoverboard and domChanger: https://github.com/studionone/todomvc-domchanger-hoverboard

---

[0] https://github.com/jesseskinner/hoverboard

[1] https://github.com/creationix/domchanger

Re: Vue.js 1.0.0

#86

Post by hardwaresofton »

piotrkaminski wrote: post #35
hardwaresofton wrote: post #27

Earlier quoted context omitted.

Vue's got a much longer track record, correct? Aurelia was only recently spawned (at least it feels like yesterday), and they still do not have a production release out. Also, I would crown knockout the light-weight champion (both in function, and concept), and ember the heavy-weight champion

You're right, Vue's been around longer, but Aurelia's release appears to be just around the corner and they have a team behind it, so I'd call it even. I'm mostly interested a comparison of the technical approaches since I think it's too early as yet to properly assess their communities.

While I don't have any experience with Vuze, I do have high hopes for Aurelia. I've worked with the beta versions, and found the API to be pretty workable/clean.

I personally like the background of the main dev(s?) behind Aurelia. IIRC, they worked on knockout->durandal->angular->aurelia, and I think the apps they stopped-by in before conceiving Aurelia have just the right concepts and features to make for a really compelling large-ish framework.

A little dissapointed about how hard it is to bootstrap it though, I really like to start projects from scratch (empty folder), and found it a little difficult to just pull together easily (without downloading their starter-zip or whatever).

Re: Vue.js 1.0.0

#87

Post by hardwaresofton »

jiaweihli wrote: post #34
hardwaresofton wrote: post #27

Earlier quoted context omitted.

Vue's got a much longer track record, correct? Aurelia was only recently spawned (at least it feels like yesterday), and they still do not have a production release out. Also, I would crown knockout the light-weight champion (both in function, and concept), and ember the heavy-weight champion

Rivets[1] is an even lighter light-weight champion. [1] http://rivetsjs.com/

Wow, thanks for posting this! At first I tried to find reasons why knockout was still the light-weight champion, but ended up taking a look through Rivet's usage and info, it looks pretty amazing, and crazy lightweight.

Only thing missing is a capable router, and I think you'd be off to the races with this thing, awesome.

Re: Vue.js 1.0.0

#89

Post by aug-riedinger »

lemevi wrote: post #10
EvanYou wrote: post #2

Author here - thanks for the submission, I was actually planning to do it tomorrow :) Anyway, for those of you who are not familiar with Vue, here's a blog post explaining why it's worth taking a look at: http://blog.evanyou.me/2015/10/25/vuejs-re-introduction/

> More importantly, there’s no need to worry about calling $apply in a timeout, or calling setState(), or listening to store events Calling `setState` is not a big deal and neither is dealing with stores. It's very simple and you keep your state separate from your HTML. At this point I probably can't do web development without JSX and not be miserable. The days of separate templates are hopefully forever behind me. N…

I actually don't understand how vue is different from react since the data flows the same way (besides different syntax and less jsx sugar, but preprocessable templates). More details on this from the author would be nice ! :) Good job anyway !
Post reply on HN