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

81–90 of 159 posts

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

#81

Post by [deleted] »

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…

[deleted]

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

#82

Post by seanwilson »

You can use JSX with Vue but you miss out on some of the template features. Two way binding is one I think but there's add-ons that write the boiler plate for that for you. Either way, it feels uncomfortable working with Vue in a less standard way in the event you run into problems.

JSX + Vue + TypeScript is pretty nice.

HTML templates + Vue + TypeScript is not so nice because you get lots of bugs coming from the untyped templates.

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

#83

Post by acemarke »

philliphaydon wrote: post #72
ilovecaching wrote: post #61

Earlier quoted context omitted.

Have you been on the React discord channel? Acemarke is like 20 people masquerading as a single person. I've never had a bad experience with the React community. Case in point, any whiff of dissatisfaction and Dan Abramov will comment on your post. Literally can't get any better service than that.

Thanks. I had no idea react had discord, I believe I used gitter? at the time. I may have just had a bad apple but it just left a bad taste in my mouth, something I haven't experienced with Vue.

Yeah, the Reactiflux community has been on Discord since late 2015 (we were on Slack before that). Don't think this group was ever on Gitter - perhaps there was some other group besides Reactiflux?

There's an invite link at https://www.reactiflux.com . Please come by and say hi! We've always got a bunch of folks hanging around happy to help answer questions.

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

#84

Post by philliphaydon »

acemarke wrote: post #83
philliphaydon wrote: post #72

Earlier quoted context omitted.

Thanks. I had no idea react had discord, I believe I used gitter? at the time. I may have just had a bad apple but it just left a bad taste in my mouth, something I haven't experienced with Vue.

Yeah, the Reactiflux community has been on Discord since late 2015 (we were on Slack before that). Don't think this group was ever on Gitter - perhaps there was some other group besides Reactiflux? There's an invite link at https://www.reactiflux.com . Please come by and say hi! We've always got a bunch of folks hanging around happy to help answer questions.

Joined!

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

#85

Post by BigJono »

ergothus wrote: post #50
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.

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…

I've been using it for 6 months now, and I still can't wait to go back to React, for the exact same reason you mentioned. I'm 'fluent' in Vue now, and it hasn't grown on me in the slightest.

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

#86

Post by koboll »

keyle wrote: post #38
kbody wrote: post #20

Earlier quoted context omitted.

Have you tried React in a similar setting? Personally I couldn't bear it and it's massive adoption on frontend pushed me away from following that route much. Vue on the other hand certainly looks more "logical" to my eyes.

Yes I've used React. React was ok, but I had to think React and work the React way. With Vue, I work my way with minimal conformance.

Weird, I came away with just the opposite impression. Vue forces you to organize everything in a certain way: data goes in data, computed properties go in computed, methods in method... it all felt very Rails to me.

React sort of used to have this problem, too, when you had to rely on classes for state, but the hooks era is a breath of fresh air. Everything is just a function. It feels freeing.

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

#87

Post by toastal »

seanwilson wrote: post #82

You can use JSX with Vue but you miss out on some of the template features. Two way binding is one I think but there's add-ons that write the boiler plate for that for you. Either way, it feels uncomfortable working with Vue in a less standard way in the event you run into problems. JSX + Vue + TypeScript is pretty nice. HTML templates + Vue + TypeScript is not so nice because you get lots of bugs coming from the unt…

Two-way binding isn't so much a 'feature' so much as it is the bug that caused the front-end framework churn to finally steady as frameworks migrated to a more predictable model of one-way binding.

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

#88

Post by yughurt »

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…

Use JSX in your Vue. It's supported just fine.

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

#89

Post by zachwood »

ilovecaching wrote: post #53
jaequery wrote: post #47

Earlier quoted context omitted.

2 things for me: 1) 2-way bindings. i used to hate the concept of it as it was a form of black magic and had hard to debug performance issues ala Angular. but in Vue, it is actually fast and straightforward, it's essentially a light boilerplate around getter/setter methods. it took me a while to convert to this way of thinking but once i did, i never looked back. 2) @click, @submit, @emit, :some_property. at first gl…

Yeah, I've heard this before. It really makes no sense why you'd want to use getters and setters when FPR is so exceedingly powerful and easy to reason about, which circles back to my point about people not understanding FPR and the benefits thereof.

What is FPR you keep referring to?

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

#90

Post by seanwilson »

toastal wrote: post #87
seanwilson wrote: post #82

You can use JSX with Vue but you miss out on some of the template features. Two way binding is one I think but there's add-ons that write the boiler plate for that for you. Either way, it feels uncomfortable working with Vue in a less standard way in the event you run into problems. JSX + Vue + TypeScript is pretty nice. HTML templates + Vue + TypeScript is not so nice because you get lots of bugs coming from the unt…

Two-way binding isn't so much a 'feature' so much as it is the bug that caused the front-end framework churn to finally steady as frameworks migrated to a more predictable model of one-way binding.

Vue is much more limited in the way it uses two way bindings compared to Angular v1 which you're probably referring to i.e. between form input elements and data, not between components.
Post reply on HN