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

91–100 of 126 posts

Re: Vue.js 2.1 Released

#91

Post by chrisbraddock »

St-Clock wrote: post #31
myf01d wrote: 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…

In vue.js, SEO is taken care of with with server side rendering[1]. This assumes that you are using node.js as your backend though. [1] https://vuejs.org/v2/guide/ssr.html#SEO

Only that node can talk to your backend right?

Re: Vue.js 2.1 Released

#93

Post by edoceo »

vitomd wrote: post #89

I don´t know why Riot.js (another js framework) don't attract more people. I used it and it´s awesome. Today they launched the 3.0.0 version http://riotjs.com/release-notes/ . Here is a quick introduction http://vitomd.com/blog/coding/hello-riot-js-quick-tutorial-a... I highly recommend it.

I also love Riot. It makes custom tags. It's easy to author and debug w/o so many additional tools. Serverside or client-side rendering. Was a snap to plug Riot in to replace jQuery "components" in a mostly PHP driven app.

Re: Vue.js 2.1 Released

#94

Post by markharris99 »

afghanPower wrote: post #81
no1youknowz wrote: post #77

Earlier quoted context omitted.

Thanks. With this coupon "CNETBF2016" it's now just $10 and I bought it at that price!

Guessing that's an affiliate promotion code?

To the OP: I also purchased this at $10, thank you!

-------

I did a search for coupon codes and I found the exact coupon code from [1].

Can I ask, what would the problem be if the code was affiliated with an affiliate promotion?

The end user pays $10, which I think we can both agree on. It's a "NET" benefit for HN users to learn something new very cheaply.

If couponkoo negotiated with the vendor of the product, so that they can advertise a coupon and get some kick back, you know because they too have to keep the lights on.

Is that such a big deal now on HN? Can you please explain yourself because I don't see an issue here personally!

[1]: http://www.couponkoo.com/coupon/95-off-vue-js-2---the-comple...

Re: Vue.js 2.1 Released

#95

Post by od14 »

CharlesW wrote: post #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…

I just finished watching the entire 16+ hours of the course. It's pretty good, but it doesn't go too deep (or at all) into the new concepts in Vue 2.x like render functions, virtual dom, server side rendering and more.

I think the docs are very good and more than enough not only just to get started, but also to keep you going.

Re: Vue.js 2.1 Released

#96

Post by mixedCase »

jaequery wrote: post #87

I really miss 1.0's inline way of writing javascript anywhere inside the dom (attributes) via {{ execute_raw_js_code() }} as well as the ability to run filters on it. Is there anyway to get them back on Vue 2? I have to admit, this was a major step back for me when upgrading to Vue 2 from Vue 1. I also really loved the Vue 1's way of handling transitions. Now having them inside it's own wrapper really diminishes the…

Yes. Use computed properties.

Re: Vue.js 2.1 Released

#98

Post by mixedCase »

nkg wrote: post #73

I still wonder why they moved the events from the constructor to the instance... Before 2.0: new Vue({ el: "#el", data: someData, events: { myevent: function(){} } }); after 2.0 : vm.$on('myevent', function () {})

Events in Vue 2 are now supposed to be used only for child -> parent component communication. If your needs are more complex then you're supposed to use Vuex.

Re: Vue.js 2.1 Released

#99

Post by od14 »

I'm really excited about the scoped slots feature. Finally it's really easy to create components that can be customized by the user from the outside. For example, it's now really easy to create a data table (with features like filters and sort), and with each row showing not only the data text, but also any other feature you might want to embed in it (like attach click listeners to each row, or popup some menu on hover).

I believe there was a way (probably a complicated hacky way) to achieve this previously too, but I never investigated it too much. Now it's really easy.

Kudos to the Vue team for this release!

Re: Vue.js 2.1 Released

#100

Post by solidr53 »

revskill wrote: post #84

I've been a long time React and Angular user, but is still sick to implement correctly enough SSR for my projects. And VueJS just did it elegantly ! I must say, thank all React + Angular folks as the pioneer for better CHANGES. This is THE time for us to change. Really.

What is a correctly enough SSR? We use react in most of our projects with server side rendering without any problems at all.

https://github.com/ueno-llc/starter-kit

Post reply on HN