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

21–30 of 152 posts

Re: Plans for the Next Iteration of Vue.js

#21

Post by Klathmon »

baybal2 wrote: post #13
Keats wrote: post #8

Written in TypeScript and with TS type support in mind! That was the thing missing for me to look at Vue, looking forward to the release.

I never had a time to take a look at type script. What is the benefit of adding static typing to an inherently dynamically typed language? As I understand, they don't get any performance improvement from that, as the browser still runs it in JS vm?

While there can technically be a perf improvement by making the types of functions less likely to change over time meaning to better jit code, the real reason is for safety (you'll get a warning if you pass an array of elements into a function that expects an array of functions that return elements) and IDE-style tooling assistance (like intellisense).

Re: Plans for the Next Iteration of Vue.js

#22

Post by baybal2 »

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.

But further they went, the more dogmatism showed up, and more it felt that they are effectively trying to invent their own language. Remember the famous "you are not doing it the Angular way!"

A big benefit of Vue is that China and big money are on the Vue train now. In China, companies are reluctant to use React.

Re: Plans for the Next Iteration of Vue.js

#23

Post by prima-facie »

lazarljubenovic wrote: post #14
jwdunne wrote: post #12

Earlier quoted context omitted.

Yeah this is great. Last time I tried, Vue itself wasn't too bad to get going with TS. The real issue for us was Vuex. The official examples and the Typescript examples we found looked completely different. It wasn't easy to get started. We actually moved to React + Redux since it was early enough in the project to make that decision. Typescript support is much better there. If typescript support was better in Vue/Vu…

> Vue itself wasn't too bad to get going with TS Last time I tried, there wasn't any support for type check across component boundaries (props, events). Did something change? A deal-breaker for me. I mostly know types from within the component; if you keep them small enough it's not much of an issue to just look up/down to check for a name, for example. But cross-component communication is where I need TS the most. H…

Props can have a type.

Re: Plans for the Next Iteration of Vue.js

#24

Post by enraged_camel »

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 the exact opposite. I took several React courses and wrote a few apps, but it didn’t click. My mind would bend but fail to fully wrap around, if that makes sense.

In comparison, within 10 minutes of reading Vue “getting started” docs I had it up and running and everything just... made sense. I have been using it for a year and a half and haven’t looked back.

Re: Plans for the Next Iteration of Vue.js

#25

Post by enraged_camel »

jaequery wrote: post #7

All I'd like to see is just better error reporting and debugging

Eh, debugging experience is already great. Vue Dev Tools is just phenomenal.

Is there something specific you are looking for that is not addressed in the article? (e.g. they are adding render tracking)

Re: Plans for the Next Iteration of Vue.js

#26

Post by erikpukinskis »

no1youknowz wrote: post #4

As someone who writes complex applications on the client side, I welcome a lot of the changes coming up for the next release and they are seriously anticipated. Anything that positions JSX for Vue to be similar to that of React would be awesome for me. I have some issues with relativity with deeply nested JSX templates. Unfortunately I wasn't able to get any help from the discord channel as most are opposed to JSX, c…

What does React do with iframes? I don’t understand how you could have a component in an I frame without having two instances of React either.

Re: Plans for the Next Iteration of Vue.js

#27

Post by atentaten »

petepete wrote: post #18

The ability to split Vue components into multiple (html, ts, scss) files in a single directory would be nice. I dislike the single file approach and it makes things like having nice syntax highlighting and completion more complex than it should be.

https://vuejs.org/v2/guide/single-file-components.html#What-...

Re: Plans for the Next Iteration of Vue.js

#28

Post by jwdunne »

lazarljubenovic wrote: post #14
jwdunne wrote: post #12

Earlier quoted context omitted.

Yeah this is great. Last time I tried, Vue itself wasn't too bad to get going with TS. The real issue for us was Vuex. The official examples and the Typescript examples we found looked completely different. It wasn't easy to get started. We actually moved to React + Redux since it was early enough in the project to make that decision. Typescript support is much better there. If typescript support was better in Vue/Vu…

> Vue itself wasn't too bad to get going with TS Last time I tried, there wasn't any support for type check across component boundaries (props, events). Did something change? A deal-breaker for me. I mostly know types from within the component; if you keep them small enough it's not much of an issue to just look up/down to check for a name, for example. But cross-component communication is where I need TS the most. H…

Oh wow. We didn't get far enough to notice that was a problem. We needed Vuex for something and that's where we got stuck and switched.

It's a good job - at that stage in the project, it wouldn't have been a big problem so we didn't notice. If we had continued, I would have a hard time justifying a switch at that stage and could have been in a bit of a corner right now.

Re: Plans for the Next Iteration of Vue.js

#29

Post by Semaphor »

lazarljubenovic wrote: post #9
Keats wrote: post #8

Written in TypeScript and with TS type support in mind! That was the thing missing for me to look at Vue, looking forward to the release.

This was the only thing stopping me from using it in larger projects. Can't wait to see how it plays. Hopefully the class-based interface has no weird object notation (methods, props, computed) and uses decorators like Angular.

With the current TS helpers you have:

    @Prop myProp!: string;
    get myComputedGetter(): string {…
    set myComputedSetter(val: string) {…
    myMethod(in: number): string {…
    @Watch('property') methodToCallOnChange() {…
And a bunch of decorators to connect vuex actions etc.

I assume the Vue3 version will be similar

Re: Plans for the Next Iteration of Vue.js

#30

Post by rk06 »

cimmanom wrote: post #19
Keats wrote: post #8

Written in TypeScript and with TS type support in mind! That was the thing missing for me to look at Vue, looking forward to the release.

Will it still be possible to run in an ES2015-compatible browser without transpiling? That was one of the killer features of Vue for me.

As there is no mention of it, it should be available. After all, as you said, Modern mode is a killer feature.
Post reply on HN