Live data from Hacker News

Why we chose Vue.js

about.gitlab.com

261–270 of 282 posts

Re: Why we chose Vue.js

#261

Earlier quoted context omitted.

Could you expand on what you mean by ceremony and state management tricks ? From my use of Redux there is a bit of set up cost in making the types and actions and getting the store into the components that need it, is that what you're referring to ?

Yeah that and then also the stuff you have to do to get async working like redux-thunk and redux-saga. I haven't actually built anything with these yet so maybe in practice it's ok but it definitely looks ugly.

Abstractions should be chosen carefully. Too little and devs step all over each other. Too much and the cognitive load and ceremony get in the way of progress. When your team will never be more than 2-3 people, redux may be a little too much ceremony (especially for applications smaller than 10-20K lines of code). When there are more people, it seems like the perfect amount of boilerplate to keep people out of each others way while its opinionated flow makes it easy to find bugs in code you've never even seen before (another large team problem).

It's been my experience that learning redux without a teacher takes some time if you aren't familiar with the one-way data flow mindset. If you have someone to pair with for a couple days, you'll be off to the races very quickly.

That said, I think redux itself is too barebones. EVERY redux app uses the thunk middleware (even the official docs spend a long time on it) and most find themselves recreating a multiple dispatch one too. If 95+% of your users need the same extension, then it's not really an extension (and in this case, both together are less than 15 lines of code).

Re: Why we chose Vue.js

#262
post #191

Earlier quoted context omitted.

Could you expand more on how these hordes of idiots sinks framework by using it? I've never come across a theory about this that's quite so tantalizingly bad before and I'd love you to expound further.

> I've never come across a theory about this that's quite so tantalizingly bad before With some projects, it's both obvious and simple. Similar to eternal summer. Democracy means that all of us get to be dumber than any of us.

You most likely meant "Eternal September".

Re: Why we chose Vue.js

#263
post #191

Earlier quoted context omitted.

> I've never come across a theory about this that's quite so tantalizingly bad before With some projects, it's both obvious and simple. Similar to eternal summer. Democracy means that all of us get to be dumber than any of us.

You most likely meant "Eternal September".

Yes. But longer. Because it starts even before the kids get back to school...

Re: Why we chose Vue.js

#264

Earlier quoted context omitted.

> Did you use MSX with Mithril? No, because it was green-field and I was trying to keep it as simple as possible; having to have a build step to run the MSX tooling was not really worth the complexity. > What thoughts do you hear from people who work on the ember app regularly? Mostly frustration, honestly. The main developer (who spends most of his time in Ember, though wasn't part of the team when it was originally…

For MSX projects where you don't have a build step just load MSXTransformer.js (122 KB). It isn't that big a runtime cost.

For development that makes it a bit easier, I'd hate to add an unnecessary 122kb in production, though.

Re: Why we chose Vue.js

#265

How does Vue.js handle high latency issues? With Angular 1.x I've always had issues where the GUI will "flash" while the HTML is loading and the angular.js has not yet finished loading on a slow connection (so you might briefly see all of these {{message1}} {{message2}} etc on the page). I'm curious how Vue.js handles that case or if it has the same problem.

[deleted]

Re: Why we chose Vue.js

#266

Earlier quoted context omitted.

I want to learn Angular2, but am struggling to find a good source, I want to also build real-time web UI, albeit not for visualization. The problem of documentation is very real. Thank you for the feedback on Vue! I will look at it now.

The Angular 2 documentation is actually really good IMO. Have you looked at the tutorial ( https://angular.io/docs/ts/latest/tutorial/ )?

I found the docs hard to understand. Maybe it is just that the component based concept is difficult to understand for me as a newbie. Anyways, between vue.js and angular, which one do you think is recommended for a newbie to the front-end world?

Re: Why we chose Vue.js

#267
post #105

Earlier quoted context omitted.

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.

Why aren't you using create-react-app?

Primarily because we're gonna need webpack anyway (using it as build tool in the project) and started before create-react-app started. It's been quite a while but I still don't fully grasp webpack yet.

Re: Why we chose Vue.js

#269

Earlier quoted context omitted.

The Angular 2 documentation is actually really good IMO. Have you looked at the tutorial ( https://angular.io/docs/ts/latest/tutorial/ )?

I found the docs hard to understand. Maybe it is just that the component based concept is difficult to understand for me as a newbie. Anyways, between vue.js and angular, which one do you think is recommended for a newbie to the front-end world?

Angular is more for the entrprise/large apps, if I were you I'd start from the vue.js, it's a relatively small tool, but powerful, not so complex and has a great docs. I've an extensive Angular v1 dev experience and I don't recommend it. Angular v2 is a complex thing, it has many dependencies (it fetches many npm packages) and dev env is more complicated.

Re: Why we chose Vue.js

#270

Earlier quoted context omitted.

I found the docs hard to understand. Maybe it is just that the component based concept is difficult to understand for me as a newbie. Anyways, between vue.js and angular, which one do you think is recommended for a newbie to the front-end world?

Angular is more for the entrprise/large apps, if I were you I'd start from the vue.js, it's a relatively small tool, but powerful, not so complex and has a great docs. I've an extensive Angular v1 dev experience and I don't recommend it. Angular v2 is a complex thing, it has many dependencies (it fetches many npm packages) and dev env is more complicated.

Yes, exactly. Angular is difficult to understand. I'll give vue a shot, it seems their documentation is excellent
Post reply on HN