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

Why we chose Vue.js

about.gitlab.com

Post reply on HN
Print view View original

141–150 of 282 posts

Re: Why we chose Vue.js

#141

Post by vladimir-y »

iotscale wrote: post #123
vladimir-y wrote: post #88

Earlier quoted context omitted.

JSX is just a way to render data, so think like it's a templater, you can integrate it with any tool. React istelf is also just an advanced templater actually, it has no built-in data reactivity despite the name. In my opinion React is not needed in general and JSX is a back to the old fashion PHP coding (Facebook returns to its roots).

React is not a templater, it's a differ. The only similarity between PHP and React is that you can have tags in ("around" in PHP's case) your code. Edit: After reading my comment again, I feel I must mention; even that similarity is not coming from React directly. It's JSX. Although they go like fish & chips together (Not a great analogy but I guess I'm hungry).

> React is not a templater, it's a differ.

It's a templater, read my message above - an advanced tempalter, which means it has some DOM rendering optimizations.

> The only similarity between PHP and React is that you can have tags in ("around" in PHP's case) your code.

Not just tags, but an entire "view" thing, a representation, so old fashion messy/sloppy/spaghetti-like PHP like code style.

Re: Why we chose Vue.js

#142

Post by slig »

shriek wrote: post #105
octref wrote: post #42

To me Vue is a great tool for side projects. In React I found myself struggling to figure out what libs to use and keep myself up to date with them. I also hated configuring webpack. With Vue, I have officially supported libraries like vuex and vue-router which work great with Vue out of the box. vue-cli also allows me to scaffold projects with these libraries very easily. But the thing I like most about Vue is it al…

Wait, Vue doesn't need to be transpiled to JS like JSX? I'm equally hating configuring webpack. It's lack of documentation isn't helping either.

After "wasting" a few hours watching webpack tutorials and reading tons os blogs about, I think I finally grasped it.

But then I discovered that there's already a new tool that's cooler than webpack: rollup [1].

[1]: http://rollupjs.org/

Re: Why we chose Vue.js

#143

Post by [deleted] »

k__ wrote: post #116
corobo wrote: post #113

Earlier quoted context omitted.

It's definitely hype. I'm honestly surprised nobody seems to be complaining about it breaking their noscript, accessibility, SEO, etc.

I read a writing about how SEO isn't an issue with SPAs. (can't find it at the moment) As far as I know, all major search engines are evaluating JavaScript client-side and index the resulting html, only a chinese one had problems with SPAs. There was even a site from Google, where you could enter a URL and see how Google sees the page.

[deleted]

Re: Why we chose Vue.js

#144

Post by macspoofing »

Svenskunganka wrote: post #134
k__ wrote: post #110

Earlier quoted context omitted.

Isn't Vue.js hype too? I mean if I look at the GitHub stars it seems pretty hyped to me. (It's between Angular/React and Ember)

I don't think it is. I've been closely keeping an eye on Vue since its first release, and it has really matured quite well and steadily since then. I like to reference Vue with the Crystal[1] programming language, which has looked closely on mainstream programming languages and adopted the good parts of them, like Go's concurrency model, Node's asynchronous I/O, Ruby's clean & straight-forward syntax and object-orien…

>I don't think it is.

You probably want to give it a bit more time. It takes 1 or 2 years after a js framework goes mainstream for the disillusionment and disappointment to set in. We are still in the Vue.js honeymoon phase.

Re: Why we chose Vue.js

#145

Post by ausjke »

Same here, using Vuejs, glad more people are using it.

It's amazing that a one-person-project(well, it's more than one person now but the core part is really just one guy) can develop such a beautiful system that actually feel better than angular2 and reactjs and who knows how many are behind those two projects.

Re: Why we chose Vue.js

#146

Post by awinder »

k__ wrote: post #116
corobo wrote: post #113

Earlier quoted context omitted.

It's definitely hype. I'm honestly surprised nobody seems to be complaining about it breaking their noscript, accessibility, SEO, etc.

I read a writing about how SEO isn't an issue with SPAs. (can't find it at the moment) As far as I know, all major search engines are evaluating JavaScript client-side and index the resulting html, only a chinese one had problems with SPAs. There was even a site from Google, where you could enter a URL and see how Google sees the page.

https://support.google.com/webmasters/answer/6066468?hl=en

Yeah there's a lot of FUD about how google indexer works, needlessly IMO

Re: Why we chose Vue.js

#148

Post by iotscale »

vladimir-y wrote: post #141
iotscale wrote: post #123

Earlier quoted context omitted.

React is not a templater, it's a differ. The only similarity between PHP and React is that you can have tags in ("around" in PHP's case) your code. Edit: After reading my comment again, I feel I must mention; even that similarity is not coming from React directly. It's JSX. Although they go like fish & chips together (Not a great analogy but I guess I'm hungry).

> React is not a templater, it's a differ. It's a templater, read my message above - an advanced tempalter, which means it has some DOM rendering optimizations. > The only similarity between PHP and React is that you can have tags in ("around" in PHP's case) your code. Not just tags, but an entire "view" thing, a representation, so old fashion messy/sloppy/spaghetti-like PHP like code style.

You give React a state, it diffs that and passes the outcome to the ReactDOM, which can render it on the DOM. At its core React doesn't know what a is. It just diffs objects and generates instructions to reach the next state (very generally speaking here). The stuff you pass to it is an object and can't be malformed like a string can. Main function of React is maybe loosely related with templating.

For PHP (in its traditional form), everything around the code is just strings, which is also the case for most of the templating engines.

You can't shout "spaghetti code" every time you see XML tags in code. Think Scala or VB.

Re: Why we chose Vue.js

#149

Post by rk06 »

haalcion3 wrote: post #125

I'd like to discuss the following comparison in: https://vuejs.org/guide/comparison.html#Angular-2 > Vue 2.0 seems to be ahead of Angular 2 according to this 3rd party benchmark. ( http://stefankrause.net/js-frameworks-benchmark4/webdriver-t... ) The latest benchmark provided is actually: https://rawgit.com/krausest/js-framework-benchmark/master/we... But, Angular 2 is v2.1.1 now, released 2016-10-20. Someone should…

>But, TypeScript is optional in [..] Angular2,

typescript is not optional. Just look at the official docs. the js version of docs are still incompelte even though 2.1 has been released.

>it's true that Google uses/develops Angular2

Google's major product is adwords. And adwords is built on angular2 dart version. While devs mostly use ts version.

Post reply on HN