Live data from Hacker News

Plans for the Next Iteration of Vue.js

medium.com

31–40 of 152 posts

Re: Plans for the Next Iteration of Vue.js

#31
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.

Nope, and it won't run with ECMAScript-compatible editors, linters, static analyzers, or type checkers (see: Flow).

I can't imagine recommending TypeScript to anyone I like.

Re: Plans for the Next Iteration of Vue.js

#32
post #30

Earlier quoted context omitted.

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.

How are they running TypeScript in the browser without transpiling?

Re: Plans for the Next Iteration of Vue.js

#33

Earlier quoted context omitted.

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.

Nope, and it won't run with ECMAScript-compatible editors, linters, static analyzers, or type checkers (see: Flow). I can't imagine recommending TypeScript to anyone I like.

What are you talking about? Typescript is what the Vue source code will be written in, which is compiled to javascript when distributed and includes Typescript definitions for editors that make use of it.

Your code can continue to be written in regular javascript with whatever toolchain you want.

And Typescript is a fantastic platform for bringing strong typing to Javascript, it's a rather extreme comment to say you don't recommend it to anyone.

Re: Plans for the Next Iteration of Vue.js

#34
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.

Do you mean running Vue by just adding a script tag to the page? That will still work because it's just using a precompiled/transpiled JS file, which will continue to be available as part of the package. FYI, React can also run the same way.

Re: Plans for the Next Iteration of Vue.js

#35
post #3

One thing I was finding weird about all those template compiling frameworks is the use of javascript for parsing the page/template instead of the lightning fast browser's native parser (DOMParser) Can somebody shed some light on that design decision?

Vue 1 used to do that.

It caused issues, specifically, the svg attributes are camelCased and DOMParser would convert them to lowercase when used with v-bindings. So, Vue2 come up with its own parser to mitigate the issue.

Re: Plans for the Next Iteration of Vue.js

#36
post #30

Earlier quoted context omitted.

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

How are they running TypeScript in the browser without transpiling?

You transpile TS at build time, i.e. when the library itself is built, not when your project is built.

Re: Plans for the Next Iteration of Vue.js

#37

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…

>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 what exactly do you mean? you didn't understand the templating language? you didn't understand the data model? you didn't understand webpack? what does "i didn't have the slightest clue what was going on" even mean? do you know what gcc does when it compiles your C code to assembly? is that the resolution at w…

It's hard to explain. I know how the web works. I used to write HTML in Notepad many years ago. With Vue I just didn't know how the stuff I was writing was turning into the stuff that the web browser actually sees. React is just a JS library that you can add on to your HTML and CSS and makes sense in the standard model.

I guess with Vue I just don't feel in control any more, and that's a big no for me.

Re: Plans for the Next Iteration of Vue.js

#38

Earlier quoted context omitted.

>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 what exactly do you mean? you didn't understand the templating language? you didn't understand the data model? you didn't understand webpack? what does "i didn't have the slightest clue what was going on" even mean? do you know what gcc does when it compiles your C code to assembly? is that the resolution at w…

It's hard to explain. I know how the web works. I used to write HTML in Notepad many years ago. With Vue I just didn't know how the stuff I was writing was turning into the stuff that the web browser actually sees. React is just a JS library that you can add on to your HTML and CSS and makes sense in the standard model. I guess with Vue I just don't feel in control any more, and that's a big no for me.

It's usually React that people complain about.

If you like jQuery, you should like vue. Cause, you can use vue just by adding a script tag in your web page.

You don't need command line, web pack or any other tool to use most of vue.

Re: Plans for the Next Iteration of Vue.js

#39

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.

Check the article here [0].

[0]: https://medium.com/@ryanseddon/rendering-to-iframes-in-react...

Re: Plans for the Next Iteration of Vue.js

#40
Seems like they're repeating the mistakes of Angular 2.x+. Breaking backwards compatibility and adding a ton of tool requirements and libraries for basic usage. We're still stuck on Angular 1.x for exactly that reason.

They also seem like they're going to drop IE10/11 support (ES2015 everything) thus either pushing the tool/library requirement even higher or simply not working on older browsers.

Vue.js was attractive because it was the anti-Angular 2.x, it was light weight, simple, and with nearly no requirements (on either browser or developer's machine). Now they'll just be a "me too!" Angular 2.x clone, but with a smaller community.

Post reply on HN