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

How we do Vue: one year later (2017)

about.gitlab.com

Post reply on HN
Print view View original

131–140 of 159 posts

Re: How we do Vue: one year later (2017)

#131

Post by have_faith »

javitury wrote: post #109
ergothus wrote: post #50

Earlier quoted context omitted.

I'm too inexperienced to have a definitive opinion, but I'm not nearly so positive and wanted to toss out a contrasting opinion to the current comments. After a few years of using React and some past experience with various other templating/view systems (webdev of one sort or another since '99) I started picking up a little Vue. So far it's been easy enough, but it is highly confusing compared to most other systems I…

One thing I love about Vue is flexibility. If you want to use pure javascript, you can create the render function directly and forget about templates. Most of vuetify components are pure javascript. Also vue has support for JSX if you prefer that.

This is the same for React. Not sure about Angular it's been a while since I've used it.

Re: How we do Vue: one year later (2017)

#132

Post by Halluxfboy009 »

I suspect most of the issues u face exist in other frameworks too. The comparison with scala isnt too right. They are probably 2 ends of the spectrurm for moment i saw scala, i knew its crap. Vue however has a certain beauty in its design, which really isnt too different from react/angular2, but much better syntax. most probably u guys have too many inexperienced developers.

Re: How we do Vue: one year later (2017)

#133

Post by konart »

dmitriid wrote: post #102
philliphaydon wrote: post #54

Earlier quoted context omitted.

I have the opposite feeling to you. The template feels like HTML to me and the syntax is clear and concise. React for me gets confusing with it all muddled together. But each to their own.

Compared to React (and React’s JSX) Vue’s syntax is orders of magnitude more complex and is very inconsistent: https://news.ycombinator.com/item?id=19199423

I feel that this baybe the case when you know js very well and it's just easier for you to write 'custom-js' that will be transpiled to regular one.

I'm working on backend most of the time and relatively recently I needed to do switch to frontend part of our service. For me Vue seems much easier and less confusing. You just have your plain html template and a few 'hooks' to make it work with your js script.

>magnitude more complex and is very inconsistent:

Just as the other guy said - it is very intuitive. You don't even have to learn much of js to make it work perfectly.

Re: How we do Vue: one year later (2017)

#134

Post by pbowyer »

kangoo1707 wrote: post #123
pbowyer wrote: post #116

I'm doing my first proper project with VueJS, enhancing a traditional web app with components. I picked Vue because a year ago when I first started experimenting it seemed much easier than React to enhance parts of existing pages with. That story has changed since, and the React docs are beter about how to use components within pages. I echo the issues with the attribute syntax. I found marshalling data from the serv…

If you mix server-side rendered apps with Vue, this is the most common way. Second method is to push the data to a window.__data.staffMemberOptions = "{{ foo }}" and use it in Vue.

Thanks, good to hear. Elsewhere I've added something similar, and populate the data this way:

    var vue = new Vue({
        el: '#app',
        created: function () {
            for (var key in __app.dataForVue) {
                this[key] = __app.dataForVue[key];
            }
        },
        // ...
    };

Re: How we do Vue: one year later (2017)

#135

Post by scottlecrab »

jmull3n wrote: post #104
geektips wrote: post #69

Earlier quoted context omitted.

Most probably because Vue is enormously popular in China and npm mirrors are mostly used in china.

Vue can also be used from a CDN and doesn't require NPM.

React can be used from a CDN as well, including using it with JSX. Although using JSX from CDN scripts is a bad idea in production because it's slower.

Re: How we do Vue: one year later (2017)

#136

Post by dmitriid »

konart wrote: post #133
dmitriid wrote: post #102

Earlier quoted context omitted.

Compared to React (and React’s JSX) Vue’s syntax is orders of magnitude more complex and is very inconsistent: https://news.ycombinator.com/item?id=19199423

I feel that this baybe the case when you know js very well and it's just easier for you to write 'custom-js' that will be transpiled to regular one. I'm working on backend most of the time and relatively recently I needed to do switch to frontend part of our service. For me Vue seems much easier and less confusing. You just have your plain html template and a few 'hooks' to make it work with your js script. >magnitud…

Thank you! That is the best explanation I’ve seen on how people may perceive Vue vs React vs other frameworks. Never thought of it this way.

Re: How we do Vue: one year later (2017)

#137

Post by valerij »

awinter-py wrote: post #41

Of the big 3 frameworks (vue angular react) vue feels to me the most like what HTML custom components should be I could see vue-like syntax and features supported natively in the browser in a utopian future; have never felt that way about react or the ancient version of angular I had to touch.

i would too really welcome DOM2 modelled after Vue. current way of reimplementing the DOM stack with JS feels like putting a new engine into cars trunk and hacking the transmission around instead of replacing the old engine that's occupying the front.

Re: How we do Vue: one year later (2017)

#138

Post by bpicolo »

dmitriid wrote: post #102
philliphaydon wrote: post #54

Earlier quoted context omitted.

I have the opposite feeling to you. The template feels like HTML to me and the syntax is clear and concise. React for me gets confusing with it all muddled together. But each to their own.

Compared to React (and React’s JSX) Vue’s syntax is orders of magnitude more complex and is very inconsistent: https://news.ycombinator.com/item?id=19199423

You can use JSX in Vue if you so choose (https://vuejs.org/v2/guide/render-function.html). I personally prefer the templates, and I enjoy the usage of HTML attributes for loops / conditionals, but the option is there, and there's no one correct answer here that everybody can agree on (which is fine).

Re: How we do Vue: one year later (2017)

#139

Post by furicane »

koboll wrote: post #30
keyle wrote: post #14

I write Vue every day, in a large application. Only small bits use VueX. Of all the frameworks I've used, it's brilliant because it hardly takes any thinking away from the business logic, so I'm not bogged down, it stays OUT of my way, and it's rock solid. I HIGHLY recommend it, and this is from someone doing web since 1997.

Vue's templating engine, honestly, seems somewhat poorly thought-out. The usual way of writing it errs on the side of HTML over JS, using quote marks awkwardly to enclose a statement rather than JSX's more sensible curly brackets. It makes it harder to visually parse, and it's sometimes annoying to not be able to use one type of quote marks unescaped within the statement. Overall, this is one of many ways in which Vu…

Basically, what irks you is that Vue separates presentation (visual) from the logic via and , reusing components via HTML elements is poorly thought out and binding values to attributes is bad because hey, you can actually use JS to compute the value.

Naturally, even though you can disregard the templating and resort to idiomatic JS, like one in React, you managed to develop an opinion after not using the features you like.

This just makes no sense honestly. I'm all for people having opinion to the point where you can blatantly say "I hate Vue because I like React more", there's literally no need for justification.

But spewing nonsense just to justify your preference is just bad. Are you a junior dev by any chance?

I've used both extensively and I can recommend Vue over React because React is a pile of mental manure. I never understood React hype, but then again - IT is a fashion business, and when "leaders" invent crap - flies tend to follow.

Re: How we do Vue: one year later (2017)

#140

Post by KaoruAoiShiho »

parthdesai wrote: post #57
KaoruAoiShiho wrote: post #51

Earlier quoted context omitted.

Using NPM stats is just not correct. I believe React to be about 2.5x larger than Vue rather than 6x.

And why would that not be correct, and what are the sources of your number?

Builds bias npm stats. You can also look at github activity and stackoverflow activity as proxies.
Post reply on HN