Live data from Hacker News

Vue.js 2.1 Released

github.com

61–70 of 126 posts

Re: Vue.js 2.1 Released

#61

I'm looking to move a few projects from Angular 1. What do developers think of migrating to Angular 2 vs Vue for this? I've played with Angular 2 but can't shake the feeling that it's overly complex.

Angular2 has a huge surface area, conceptually. You might need that surface area. But it's daunting. Angular2 also expects you to teleport into a very modern future of tooling and development practices. That said, it's a safe choice...everything you might want to do has been done and complained about on StackOverflow. [wink]

Re: Vue.js 2.1 Released

#62
For folks who haven't tried Vue yet, I just completed my first project with it and I'm really excited about using it more.

Specifically, I used learning Vue as an opportunity to upgrade a simple jQuery-based SPA (with a PHP backend) to ES6, JS modules and Vue. It was a little hairy to bite off all of that stuff at once, but the Vue community was really helpful. In contrast to more monolithic frameworks I didn't have to port everything at once, and the re-implementation of the bits I did port are sooo much cleaner.

FWIW, there's a highly-rated Vue.js 2/Vuex Udemy course on sale for an impulse price of $14 (normally $190) as I type this. With the caveat that I just bought the course myself, at that price it seems like a useful resource even if you only have a cursory interest in Vue.

https://www.udemy.com/vuejs-2-the-complete-guide/

Re: Vue.js 2.1 Released

#63
post #42
post #35

Earlier quoted context omitted.

From personal experience for general web-sites like blogs, etc. it's better to do them old way, you don't need to worry much about seo, caching, precompilation, etc. But business apps huge community-like ones, and big shops benefit a lot from frameworks like that. But you should always base your decision on cost of implementation, support, etc.

Thanks, I am more interested in developing social websites with modern look and more performance, I mean like the design of medium.com or hashnode.com, I think they do render the first page fully canonical HTML, and then every subsequent request is rendered using the js framework GETing some JSON which gives more space to the server to do other work. I am really interested in this approach but I fear about the SEO an…

If you fear about the SEO, start with Turbolinks.

Re: Vue.js 2.1 Released

#64
post #2

Is this looking a lot like Angular 1.x to anyone else? I've heard it's actually more similar to React but I'm not seeing it... ?

It's like Angular in that they use a similar templating language, and it's like React in that they're using a component-based declarative DOM API.

Angular also has a component-based declarative DOM API. Always had, but since version 1.5 it's more explicit.

Re: Vue.js 2.1 Released

#65

I'm looking to move a few projects from Angular 1. What do developers think of migrating to Angular 2 vs Vue for this? I've played with Angular 2 but can't shake the feeling that it's overly complex.

Well, it might help if you said why you're looking to move from Angular 1. What problems do you have with it? How many developers are working on the project? Do you use libraries like angular-material? ...

There are a thousand factors why you'd chose one above the other. I would just be very wary of comments like: "Definitely framework X".

Re: Vue.js 2.1 Released

#66

I'm looking to move a few projects from Angular 1. What do developers think of migrating to Angular 2 vs Vue for this? I've played with Angular 2 but can't shake the feeling that it's overly complex.

You may want to check out Aurelia too. One of Angulars main devs left the Angular Team because of its direction and build Aurelia the way Angular should have been.

I played with it a bit and what's awesome about it that you just write plain JS most of the time. No weird stuff like JSX and whatever. Docs arn't that great tho

Re: Vue.js 2.1 Released

#67

Earlier quoted context omitted.

are there any tutorials that would help a beginner start on that front?

Another Vue.js 2.x tutorial that I am currently finishing is https://jayway.github.io/vue-js-workshop/ . It is a nice intro into all the important pieces of Vue.js.

Does the guide include state management? As a newbie I face that problem. I was able to figure out how to use vue-resource, rendering, components, the next step in my learning cycle is to understand how to interact with a JWT server, set tokens and do state management. I don't even understand anything by the words state management :D

Re: Vue.js 2.1 Released

#68
post #28

I am sorry if this sounds too ignorant, are frameworks like Vue.js (I actually read the guide and understood some wonderful things about its philosophy since I am actually developing backend mainly) or React, etc.. reasonable to use in websites in general (instead of jquery or taking some tasks from it) or they actually only reasonable for mobile web applications and SPAs? What about the SEO and search engine renderi…

I can't speak to Vue, but React is overkill for many sites. The virtual DOM etc is incredibly useful for sites that update the page very frequently, but if the only thing you're making is a static site and a contact form, you don't need React.

That said, I do like the React model of creating components (and suspect this is why so many people use it when it's unnecessary). I'm looking forward to browsers implementing custom elements so that we can all compinentise this way without the overhead of a large JS framework.

Re: Vue.js 2.1 Released

#69
post #41

I tried to use Vue 2 for a pet project but couldn't get the routing to work. It seems the router was lagging behind in versions and there were no guides on "router 2.0". Does this version have a routing guide and production ready routing solution? That's pretty important.

We're using Vue and its router in production since 1.x, so I'm not sure where you got that impression...

I would like to know more about your use of Vue and the router in production. Tips/best case guidelines?

Re: Vue.js 2.1 Released

#70
post #57
post #52

Earlier quoted context omitted.

Transpiling is complexity. You don't have to transpile if you just use web technologies (JavaScript, HTML, CSS).

Of course it is, but saying it's "a ton of complexity" to use JSX, while not saying the same for transpiling current and future ECMA-262 syntax into what browsers support right now is disingenuous.

No it's not, transpiling future ECMA-262 is not within the scope of this discussion. We are compared browser-native language features JS (non transpiled), HTML, CSS, to non-native features, namely JSX.
Post reply on HN