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

111–120 of 152 posts

Re: Plans for the Next Iteration of Vue.js

#111

Post by marcus_holmes »

linkmotif wrote: post #107
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…

> To me it's the new coffeescript combined with the verbosity of J2EE How is this the top voted comment on here? How does one go from Coffeescript/J2EE to TS? Coffeescript was... well... Coffeescript, a JS variant with better ergonomics. J2EE was a Java framework that also has no resemblance or connection to TS. What a bizarre comment but truly disturbing to see masses voting this up.

No, I get it.

As a JS dev, Cofeescript appeared to be nothing more than an attempt to make JS more like Ruby.

From this perspective, TS appears to be nothing more than an attempt to make JS more like C#.

Either way, both appear to be attempts to use JS's massive flexibility to make the language work more like another language, because people are more familiar with that other language. And in both cases, there's a familiar response of "please don't do that. Please stop complaining about JS because it's not like your favourite language. Please learn to use it properly instead".

I played very briefly with CS to see what the excitement was about, and haven't touched TS at all, because I enjoy JS. But with Vue moving there, I think I'm going to have to bite the bullet and take a look.

Re: Plans for the Next Iteration of Vue.js

#112

Post by peterkelly »

marcus_holmes wrote: post #111
linkmotif wrote: post #107

Earlier quoted context omitted.

> To me it's the new coffeescript combined with the verbosity of J2EE How is this the top voted comment on here? How does one go from Coffeescript/J2EE to TS? Coffeescript was... well... Coffeescript, a JS variant with better ergonomics. J2EE was a Java framework that also has no resemblance or connection to TS. What a bizarre comment but truly disturbing to see masses voting this up.

No, I get it. As a JS dev, Cofeescript appeared to be nothing more than an attempt to make JS more like Ruby. From this perspective, TS appears to be nothing more than an attempt to make JS more like C#. Either way, both appear to be attempts to use JS's massive flexibility to make the language work more like another language, because people are more familiar with that other language. And in both cases, there's a fam…

I suggest you give TypeScript a try. You might like it, you might not, but at least then you'll know. It uses gradual typing - you can use static types as little or as much as you like. It's not C#.

Re: Plans for the Next Iteration of Vue.js

#113

Post by reaperducer »

another-cuppa wrote: post #37
mlevental wrote: post #17

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.

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

I understand your feeling, even though I don’t work in React.

I worked for a company that brought in a new guy who was all hung-ho on Vue as the new hotness. He managed to convince the project manager that we had to convert the entire site to Vue.

I was never able to wrap my brain around the fact that so much of it was opaque. You just had to trust that A would lead to B would lead to C. And when it didn’t, even the Vue evangelist couldn’t untangle it.

As I’ve explored more and more languages and frameworks over the years, some I immediately grok, and others just never make sense. I think some programmers, brains are just wired differently than others. It’s too bad that there’s this undercurrent of tribalism and brand loyalty in the industry.

Re: Plans for the Next Iteration of Vue.js

#114

Post by guessmyname »

klodolph wrote: post #97
mo1ok wrote: post #88

Earlier quoted context omitted.

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).

Golang doesn't avoid all the compatibility issues. On the contrary, there's a ton of Golang that won't run on anything but Linux.

> […] there's a ton of Golang that won't run on anything but Linux.

Please give examples so I can fix them.

Go code is highly portable to the supported platforms. In all my 5+ years developing code on Mac and cross-compiling for Linux servers, I can count with one hand the number of broken packages due to compatibility issues with the target operating system.

With my experience I am sure that I can fix the cross-compatibility issues in the code that you have had problems with, but I need names and/or links, please point me to them.

Re: Plans for the Next Iteration of Vue.js

#115

Post by lazarljubenovic »

bradstewart wrote: post #105
basil-rash wrote: post #65

Earlier quoted context omitted.

The type is verified at runtime though

It can also be verified at compile time when using vue-class-component.

If it's a primitive type, yes. Throw in a union, a generic, or a conditional and everything blows up.

Re: Plans for the Next Iteration of Vue.js

#116

Post by reaperducer »

Roritharr wrote: post #82
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.

I’ve got almost 25% IE11 and XP to support. I feel your pain.

Re: Plans for the Next Iteration of Vue.js

#117

Post by russellbeattie »

CharlesW wrote: post #101
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 like JavaScript, and Typescript isn't JS. Considering that you don't need to use it unless you plan on contributing to Vue.js itself, my (sincere) question is: Why does it matter to you?

One always ends up going through a library or framework's source code at one point or another while trying to track down bugs. Using Typescript makes this a lot harder.

For example, I was going to contribute to the Visual Studio Code project with a simple tweak: A setting that would make global find key-command happen without have to click the search icon after. After asking online and then wading through the TS source code trying to get something to work, I finally just gave up. Typescript isn't JavaScript.

Re: Plans for the Next Iteration of Vue.js

#118

Post by jakear »

russellbeattie wrote: post #117
CharlesW wrote: post #101

Earlier quoted context omitted.

> …I like JavaScript, and Typescript isn't JS. Considering that you don't need to use it unless you plan on contributing to Vue.js itself, my (sincere) question is: Why does it matter to you?

One always ends up going through a library or framework's source code at one point or another while trying to track down bugs. Using Typescript makes this a lot harder. For example, I was going to contribute to the Visual Studio Code project with a simple tweak: A setting that would make global find key-command happen without have to click the search icon after. After asking online and then wading through the TS sour…

Did you try running the build script and working directly in “out/“? I doubt it would have been easier. Big projects simply take time to learn and contribute to, TypeScript or not.

Actually, I’d say VS Code would be much harder to contribute to without TS. You mentioned adding a setting. This requires touching several different methods (parsing, cleansing, etc.). With TypeScript, the compiler instantly tells you when you have forgotten to implement a part of the setting pipeline. With JS, the runtime gives you some “undefined is not a blah” error to track down.

Re: Plans for the Next Iteration of Vue.js

#119

Post by realusername »

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…

Unlike CoffeeScript, you can't have any technical debt with TypeScript, if one day TypeScript disapears, you just remove the types and you have a perfectly working JS file.

Re: Plans for the Next Iteration of Vue.js

#120

Post by mrath »

tinyvm wrote: post #74

Wow , reading comments was quite interesting. I didn't thought so much people got "exhausted" by Angular. I personally tried it ( v2 , v4 , v5 , v6) and i really fell in love with it. I use mostly Vue and Angular they complete each others very well , i prefer NGRX over Vuex and Angular native support for Typescript. Typescript with Vue is a bit of hassle to set up and maintain, but with this new update this a bit of…

I share your view. I am generally a backend developer, I spent a lot of time with Angular(2+), recently started a project with react and also looked at Vue. so my time spent on Angular > React > Vue. If I have to choose a framework for a new project I would definitely choose between Angular and Vue, I won't write react unless I am paid. It is just verbose and ugly, no magic.
Post reply on HN