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

Plans for the Next Iteration of Vue.js

medium.com

Post reply on HN
Print view View original

81–90 of 152 posts

Re: Plans for the Next Iteration of Vue.js

#81

Post by russellbeattie »

I'm really worried about the wholesale move to Typescript in so many projects. To me it's the new coffeescript combined with the verbosity of J2EE. Yes it's corporate sponsored, so hopefully will be maintained indefinitely - but I like JavaScript, and Typescript isn't JS.

What's worse is so many developers using their own slightly tweaked versions of JavaScript. I spent a solid day this week trying to get decorators and class fields to transpile reliably with as few dependencies as possible. It seems every project creates their own DSL that sorta-kinda is JS, then figures out a way to get it to compile and calls it a day. This sort of goes against the whole reason we have language standards in the first place.

Anyways, I admire Evan's desire to hold back on the need for decorators and class fields, but since he's developing the project in Typescript, I have little faith that any of the projects that use Vue will avoid them.

Re: Plans for the Next Iteration of Vue.js

#82

Post by Roritharr »

AltruisticGap wrote: post #58

Sounds great, but why bother with the added work supporting IE11 if Vue 2.x can be used with IE11? Especially that time continues to fly until 3.x is released, and IE11 is replaced with EDGE already. edit: I am guessing this has to do with having one codebase for projects that move to vue 3 and still need support for IE1.. makes sense. Hmm.

IE11 is still supported by Microsoft atleast up until 2021, possibly further. We bet on Vue and 5% of our enterprisey customers rely solely on IE11 for some reason or another and our competition supports it unflinchingly.

So, atleast we're very glad for this decision.

Re: Plans for the Next Iteration of Vue.js

#83

Post by Keyframe »

baybal2 wrote: post #22
another-cuppa wrote: post #15

I'd been out of the loop of frontend Web stuff for several years but I tried Vue.js because I read here and elsewhere that Angular was a mess. I just couldn't stand the weird hybrid html/css/js editing. At no point did I feel I had the slightest clue what was going on and it felt like I wasn't supposed to ask. React felt much more natural to me. Is there any way to do stuff differently with Vue or should I just stick…

>Is there any way to do stuff differently with Vue or should I just stick with React? On technical side, not much. But there are much more to it than just technical stuff. Angular was great for big, organized teams, with spec driven development. Separation of concerns and work was also great - having junior devs concentrate on templates and to spec written directives, while seniors deal with something more arcane. Bu…

In China, companies are reluctant to use React.

How come?

Re: Plans for the Next Iteration of Vue.js

#84

Post by jhoh »

IgorPartola wrote: post #55

Phew. After the Angular 2 disaster, I am traumatized by posts with this title format. It seems like the changes will be simple, useful, and mostly backwards compatible. I look forward to upgrading my current Vue projects to use 3.x. I am especially excited about not having to worry about missed observable mutations with arrays. That was annoying.

How was Angular 2 a disaster? I know it was basically a new Framework but I think they made it very clear and even did a rebranding (AngularJS -> Angular) and AngularJS is still being maintained.

Re: Plans for the Next Iteration of Vue.js

#85

Post by porsager »

another-cuppa wrote: post #62
porsager wrote: post #59

Earlier quoted context omitted.

You can skip both, and most of the churn by taking a look at https://mithril.js.org . It's one of the only frameworks I've seen that gets you 95% of the way while supporting you through the last 5% instead of getting in your way. It includes all the regular things you need (view, router, requests) while staying under 10kb and having better performance than those two. If you need any help at all, there's a super frien…

That looks really great. Bookmarked. Shame the site is one of the rather large group of sites that assume everyone's default CSS is black on white text, though.

Well I'd be happy to make a pull request to fix it. What is your setup?

Re: Plans for the Next Iteration of Vue.js

#86

Post by Lazare »

another-cuppa wrote: post #15

I'd been out of the loop of frontend Web stuff for several years but I tried Vue.js because I read here and elsewhere that Angular was a mess. I just couldn't stand the weird hybrid html/css/js editing. At no point did I feel I had the slightest clue what was going on and it felt like I wasn't supposed to ask. React felt much more natural to me. Is there any way to do stuff differently with Vue or should I just stick…

I'm honestly shocked to see someone say they found React natural, but felt Vue was confusing.

Re: Plans for the Next Iteration of Vue.js

#87

Post by nikkwong »

Wow, hats off to the vuejs team. Vue is already lightning fast and I've been able to pull off some pretty computationally intense state changes which render like butter whilst other frameworks lagged. A speed increase of 100% is almost unimaginable—but welcome!

Re: Plans for the Next Iteration of Vue.js

#88

Post by mo1ok »

russellbeattie wrote: post #81

I'm really worried about the wholesale move to Typescript in so many projects. To me it's the new coffeescript combined with the verbosity of J2EE. Yes it's corporate sponsored, so hopefully will be maintained indefinitely - but I like JavaScript, and Typescript isn't JS. What's worse is so many developers using their own slightly tweaked versions of JavaScript. I spent a solid day this week trying to get decorators…

Yep, this is a huge problem in the ecosystem right now. The irony is that JS, an interpreted language, is becoming slower to compile than some of the newer compiled language (i.e. golang, which compiles to machine code and therefore avoids all compatibility issues).

Re: Plans for the Next Iteration of Vue.js

#89

Post by barbecue_sauce »

jhoh wrote: post #84
IgorPartola wrote: post #55

Phew. After the Angular 2 disaster, I am traumatized by posts with this title format. It seems like the changes will be simple, useful, and mostly backwards compatible. I look forward to upgrading my current Vue projects to use 3.x. I am especially excited about not having to worry about missed observable mutations with arrays. That was annoying.

How was Angular 2 a disaster? I know it was basically a new Framework but I think they made it very clear and even did a rebranding (AngularJS -> Angular) and AngularJS is still being maintained.

While I agree Angular 2 isn't a disaster, AngularJS -> Angular is probably the laziest and most ambiguous "rebranding" I've ever seen, considering the fact that historically AngularJS was often referred to as Angular. This will be a clunky simile, but it's like if all of a sudden Coca-Cola decided to rebrand Cherry Coke as just Coke and branded regular Coke as CokeNC. (Coke NoCherry).

Re: Plans for the Next Iteration of Vue.js

#90

Post by kangax »

russellbeattie wrote: post #81

I'm really worried about the wholesale move to Typescript in so many projects. To me it's the new coffeescript combined with the verbosity of J2EE. Yes it's corporate sponsored, so hopefully will be maintained indefinitely - but I like JavaScript, and Typescript isn't JS. What's worse is so many developers using their own slightly tweaked versions of JavaScript. I spent a solid day this week trying to get decorators…

I agree that TS increases barrier to entry for contributors. However, it's very different from Coffeescript. It offers better program correctness via types whereas CS was mostly sugar. Libraries that (properly) use Flow/TS are less likely to have bugs and are safer to contribute to (you're less likely to introduce a bug) and that's a good thing.
Post reply on HN