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

Vue.js 2.1 Released

github.com

Post reply on HN
Print view View original

21–30 of 126 posts

Re: Vue.js 2.1 Released

#21

Post by bmoresbest55 »

ohstopitu wrote: post #6
w0utert wrote: post #3

So far my Vue.js experience has been great. Even though I don't particularly enjoy front-end development and the tools and techniques I'm supposed to use for them, Vue.js has been a breath of fresh air between my frustrations with HTML, Javascript, npm, CSS, HTTP and all the other things that are needed to stitch everything together. It really is a great framework. The one thing that does still bug me these days is t…

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.

Re: Vue.js 2.1 Released

#23

Post by aikah »

Nice, I love Vue.js it is light weight yet fulfill 90% of the needs of a large SPA without a third party language, some bureaucratic dependency injection and without getting in the developer's way by mandating this or that build tool. But competition is good so I'm glad there is a front end framework for everyone out there.

Re: Vue.js 2.1 Released

#24

Post by AtticusTheGreat »

I've been using Vue.js for a new project and it is a breath of fresh air after using React. It has all the benefits of Knockoutjs (which was my gateway into these types of frameworks), but much nicer in-code organization (I'm looking at you ko.observable).

Re: Vue.js 2.1 Released

#25

Post by Touche »

k__ wrote: post #20
meathook wrote: post #19

Earlier quoted context omitted.

You can use JSX to write your render functions in Vue [0]. It's opt-in as the Vue community views them as overkill in the usual case. Personally, I appreciate having the intuitive approach for templating as the default for people who don't share my encyclopedic knowledge of web development. They can more easily follow along and contribute. [0] https://vuejs.org/v2/guide/render-function#JSX

I see :) > I appreciate having the intuitive approach for templating as the default for people who don't share my encyclopedic knowledge of web development I always saw it the other way around, haha :) Why should I learn some template language, when JS can do the job and I already know it.

JSX is not JavaScript. If its not in a spec that is ever going to be implemented by a JS runtime, like a browser or Node.js, then it's not JavaScript. It's a superset of JavaScript.

If you admit that JSX is a superset of JS then the downsides become readily apparent. Many will still choose JSX and there's nothing wrong with that, but the argument isn't "why would I use X when Y is better".

Re: Vue.js 2.1 Released

#26

Post by Diederich »

thewhitetulip wrote: post #10
w0utert wrote: post #3

So far my Vue.js experience has been great. Even though I don't particularly enjoy front-end development and the tools and techniques I'm supposed to use for them, Vue.js has been a breath of fresh air between my frustrations with HTML, Javascript, npm, CSS, HTTP and all the other things that are needed to stitch everything together. It really is a great framework. The one thing that does still bug me these days is t…

I'm writing an easy to understand tutorial with vuejs2 here https://github.com/thewhitetulip/intro-to-vuejs

Thank you!

Re: Vue.js 2.1 Released

#27

Post by blitzo »

aikah wrote: post #23

Nice, I love Vue.js it is light weight yet fulfill 90% of the needs of a large SPA without a third party language, some bureaucratic dependency injection and without getting in the developer's way by mandating this or that build tool. But competition is good so I'm glad there is a front end framework for everyone out there.

The sentiment 'competition is good' in the context of Javascript universe is a bit ironic since that's what led us to the recent fatigue grievance.

Re: Vue.js 2.1 Released

#28

Post by myf01d »

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 rendering to custom HTML elements like in Vue.js components? is it okay or affects SEO?

Re: Vue.js 2.1 Released

#29

Post by k__ »

Touche wrote: post #25
k__ wrote: post #20

Earlier quoted context omitted.

I see :) > I appreciate having the intuitive approach for templating as the default for people who don't share my encyclopedic knowledge of web development I always saw it the other way around, haha :) Why should I learn some template language, when JS can do the job and I already know it.

JSX is not JavaScript. If its not in a spec that is ever going to be implemented by a JS runtime, like a browser or Node.js, then it's not JavaScript. It's a superset of JavaScript. If you admit that JSX is a superset of JS then the downsides become readily apparent. Many will still choose JSX and there's nothing wrong with that, but the argument isn't "why would I use X when Y is better".

The whole point wasn't about this syntax, but about the fact that React templates are just simple nested function. But maybe this would have been more obvious if I used hyperscript instead of JSX as an example.

Re: Vue.js 2.1 Released

#30

Post by aikah »

blitzo wrote: post #27
aikah wrote: post #23

Nice, I love Vue.js it is light weight yet fulfill 90% of the needs of a large SPA without a third party language, some bureaucratic dependency injection and without getting in the developer's way by mandating this or that build tool. But competition is good so I'm glad there is a front end framework for everyone out there.

The sentiment 'competition is good' in the context of Javascript universe is a bit ironic since that's what led us to the recent fatigue grievance.

People have different requirements, there is not a single framework that would make everybody happy. The issue isn't the the number of frameworks by the way but the complexity of the build tools in the context of Nodejs. Grunt,Gulp,Babel transpilers and co, they are not frameworks, they merely transform assets, yet they make JS development extremely complex and bureaucratic.
Post reply on HN