Re:Vue.js: the good, the meh, and the ugly
by Ronsenshi on Friday July 06, 2018 @01:50AM
(#17469198)
He's possibly meaning that if you completely rewrite framework it would lead to something like what happened to Angular when it was rewritten and promptly lost huge number of followers/users?
[ Parent
| on HN ]
Angular didn't lose mindshare because of TypeScript, it lost mindshare because they completely changed the API of Angular, meaning a bunch of companies had to do expensive ports/complete rewrites/switch to new tech. A lot of companies are still stuck on Angular 1 for this reason.
Most Angular devs I know are happy to use TypeScript. (In fact going out on a limb, most JS devs I know).
Re:Vue.js: the good, the meh, and the ugly
by darkerside on Friday July 06, 2018 @07:53AM
(#17470638)
In this particular case, with a BDFL in Evan, there's probably a much higher chance of maintaining sanity between major releases. People were worried about the change to Vue 2.0, but it mostly sunsetted features that complicated the framework and doubled down on an elegant component system. Seems obvious to say, but frameworks probably get fractured in geometric proportion to the number of powerful authors working on them.
That is amusing because Vue was already rewritten for V2 when they introduced the shadow Dom.
Typescript is very similar to plain JS. The type annotation is purely optional. I really bought into the optional type annotation pattern when I learned and used Julia for a project. Typescript is also like that. It's extremely unintrusive to use and I'm quite sure such a huge shift as the one that happened in Angular won't happen.