Live data from Hacker News

Vue.js 2.1 Released

github.com

111–120 of 126 posts

Re: Vue.js 2.1 Released

#112

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.

Yeah you can use that but still you lose the liberated feeling of being able to execute js anywhere directly on the dom, which I actually appreciated quite a bit.

Re: Vue.js 2.1 Released

#113
I am always looking for the fastest way to build a complete app. Brought me to Rails. Then to Meteor/React (which was mixed). Then some Rails/React which is ok.

Vue looks really appealing on the simplicity and completeness side.

I would like to know from people using Vue what backends you're using. In order to complete the loop - the simplest stack overall Vue+???.

Re: Vue.js 2.1 Released

#114
I'm currently using (and enjoying) my first Vue project. I have to say the camelcase support for JSX events feels like a step backwards. The `on-` prefix had a nice semantic way of telling you that thing is an event (either DOM or $emit from component). Now there's just this implicit `onFoo` which could be an event, or could be a prop, maybe component will invoke it directly like in React, maybe it will $emit, who knows?

Re: Vue.js 2.1 Released

#115
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 more that many many frameworks imitate Handlebars, or accept that Handlebars is good enough and it's not worth inventing new syntax.

If it's your opinion, as it is mine, that HTML frameworks should deal with HTML, instead of abstracting it away, then this isn't a bad thing.

Re: Vue.js 2.1 Released

#116
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…

Google will index sites that render their pages through Javascript. There are two caveats to be aware of: 1. It drops out if it takes more than 5 seconds to complete its operation and uses whatever is render then. 2. Indexing with HTML happens in near-realtime. Indexing with JS to HTML is delayed by about 1-5 days depending on the popularity of the site. So if you're serious about it; you ought to heavily include met…

Proof?

Re: Vue.js 2.1 Released

#117

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…

It is scary that everyone is hyped and the site just shows off a series of syntax combinations.

Re: Vue.js 2.1 Released

#118

I am always looking for the fastest way to build a complete app. Brought me to Rails. Then to Meteor/React (which was mixed). Then some Rails/React which is ok. Vue looks really appealing on the simplicity and completeness side. I would like to know from people using Vue what backends you're using. In order to complete the loop - the simplest stack overall Vue+???.

I've used Vue w/ Rails so far and it's been pretty good. The one real complaint is that I really wish is that I could use Vue components (.vue files) in a better integrated way with the Rails asset pipeline.

react-rails does this really well, making JSX transformation a drop-in gem, vs. having to set up some kind of front end task runner of sorts and constantly having to commit compiled files and such.

Beyond that, Vue has been amazing, and I really love it.

Re: Vue.js 2.1 Released

#119

Earlier quoted context omitted.

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?

I haven't heard of Laravel getting SSR yet, so yeah.

Re: Vue.js 2.1 Released

#120

I am always looking for the fastest way to build a complete app. Brought me to Rails. Then to Meteor/React (which was mixed). Then some Rails/React which is ok. Vue looks really appealing on the simplicity and completeness side. I would like to know from people using Vue what backends you're using. In order to complete the loop - the simplest stack overall Vue+???.

I'm thinking to rewrite my templates in vuejs then put a nodejs+vuejs SSR layer in front of my non-nodejs backend. I'm wondering how Laravel expects me to handle this situation.
Post reply on HN