How we do Vue: one year later (2017) • Hacker News Board

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

#11

Post by nerdwaller » Mon, Mar 18, 2019, 10:25 PM UTC

Tade0 wrote: post #10

Kiro wrote: post #4

> Just use VueX That's the problem with large-scale Vue apps. Vue is awesome until you need to use VueX, after which it just becomes an inferior version of React + Redux.

Inferior? How exactly? I found Redux to be highly over-engineered in contrast to Vuex which is a lot like MobX - easy to use, yet powerful.

This is my thought as well, adding that it feels like way less boilerplate due to the integration with the underlying framework

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

#12

Post by bargl » Mon, Mar 18, 2019, 10:29 PM UTC

jakecodes wrote: post #9

I wrote this article back in 2017. A lot has changed since then. If anyone has any questions I'd be happy to answer them. We now use Vue in our data science startup meltano.com.

Have you done any work with Vue and Typescript? We're just starting out with Vue. But my understanding was that TypeScript is a first class citizen in the new version of Vue.

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

#13

Post by arendtio » Mon, Mar 18, 2019, 10:33 PM UTC

I used riot.js for a few years and was quite happy with it. Sadly it had a few misconceptions (e.g. the parent.parent.parent... problem) which could have been changed easily. But as the lead dev wasn't very cooperative I switched to the closest alternative: Vue. I don't have enough experience with Vue yet to judge it, but given how similar Vue and riot.js are I hope that it gives me the same productivity without those broken bits and hopefully a better community interaction.

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

#14

Post by keyle » Mon, Mar 18, 2019, 10:38 PM UTC

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.

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

#15

Post by jakecodes » Mon, Mar 18, 2019, 10:40 PM UTC

bargl wrote: post #12

jakecodes wrote: post #9

I wrote this article back in 2017. A lot has changed since then. If anyone has any questions I'd be happy to answer them. We now use Vue in our data science startup meltano.com.

Have you done any work with Vue and Typescript? We're just starting out with Vue. But my understanding was that TypeScript is a first class citizen in the new version of Vue.

I haven't done much with TypeScript. But I always hear great things.

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

#16

Post by bartq » Mon, Mar 18, 2019, 10:45 PM UTC

jakecodes wrote: post #9

I wrote this article back in 2017. A lot has changed since then. If anyone has any questions I'd be happy to answer them. We now use Vue in our data science startup meltano.com.

what are worst parts of vue for you?

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

#17

Post by wishinghand » Mon, Mar 18, 2019, 10:50 PM UTC

Kiro wrote: post #4

> Just use VueX That's the problem with large-scale Vue apps. Vue is awesome until you need to use VueX, after which it just becomes an inferior version of React + Redux.

I've always found Redux to be an overcomplicated mess, whereas Vuex is quite simple and has a nice, logical flow. For those who think it's still too complex, I've heard that Pathify https://davestewart.github.io/vuex-pathify is a great solution.

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

#18

Post by m_fayer » Mon, Mar 18, 2019, 10:53 PM UTC

bargl wrote: post #12

jakecodes wrote: post #9

I wrote this article back in 2017. A lot has changed since then. If anyone has any questions I'd be happy to answer them. We now use Vue in our data science startup meltano.com.

Have you done any work with Vue and Typescript? We're just starting out with Vue. But my understanding was that TypeScript is a first class citizen in the new version of Vue.

TS isn't a first-class citizen in 2.x, and you'll need to go through a couple of awkward maneuvers to prevent Vue from negating many of the benefits of TS, but it can absolutely be done. This sample project sums it up nicely: https://github.com/Armour/vue-typescript-admin-template

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

#19

Post by odorousrex » Mon, Mar 18, 2019, 10:53 PM UTC

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 HIGHLY recommend it, and this is from someone doing web since 1997.

I started in 97 as well, and cannot recommend Vue enough. I've done React, Angular 1 & 2, and I keep coming back to Vue.

I always feel like with React/Angular I'm conforming to work how they want me to work. (Esp. Angular - React is more forgiving). Whereas Vue is just a complement to the way I already work. I can use as much or as little of it as I wish.

A hearty endorsement indeed.

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

#20

Post by kbody » Mon, Mar 18, 2019, 10:54 PM UTC

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.

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.