Is javascript really so bad?
Edit: Why did this question get down voted? It was an honest question...
Angular 2: Built on TypeScript
21–30 of 235 posts
Re: Angular 2: Built on TypeScript
#22So Angular has gone from being written in plain JS, to Dart, to Atscript, and now Typescript? Why so much jumping around? Isn't that creating a lot of technical debt issues?
Constantly trying out the "new hotness" seems to be the norm in front end dev.
Re: Angular 2: Built on TypeScript
#23Embrace, extend, extinguish.
If you're talking about TypeScript, I don't believe that mantra is applicable when the extensions are open source, liberally licensed (Apache License), cross-browser, and developed in the open. There's nothing proprietary or exclusive about it.
Re: Angular 2: Built on TypeScript
#24Is javascript really so bad? Edit: Why did this question get down voted? It was an honest question...
It probably is if you have to deal with > 25k LOC code base like what Angular has.
Re: Angular 2: Built on TypeScript
#25So Angular has gone from being written in plain JS, to Dart, to Atscript, and now Typescript? Why so much jumping around? Isn't that creating a lot of technical debt issues?
Constantly trying out the "new hotness" seems to be the norm in front end dev.
Ditching angular has been the new hotness for a while.
Re: Angular 2: Built on TypeScript
#26Is javascript really so bad? Edit: Why did this question get down voted? It was an honest question...
It probably is if you have to deal with > 25k LOC code base like what Angular has.
Well, there's their problem...
Edit:
Ok, for the down voters. Angular is HUGE. And all that code has to get shoved onto the client side when someone visits a page. And that's JUST for the framework. We aren't even talking about the application code yet. More and more clients are mobile. Nobody sees a problem here? You're using more (precious) data, it's slower to load and slower to run. It's just a nasty little trend going on.
NOW LET'S SEE SOME FREAKING DOWN VOTING!!!
Re: Angular 2: Built on TypeScript
#27So Angular has gone from being written in plain JS, to Dart, to Atscript, and now Typescript? Why so much jumping around? Isn't that creating a lot of technical debt issues?
It's a bit confusing, but basically right now there are two Angular products: AngularJS 1.x and AngularDart. These two efforts are supported by completely separate teams. Now the JS and Dart teams are merging and the new Angular 2.0 will be written in TypeScript and transcompiled down to ES6, ES5, and Dart. So while it may look like jumping around, the message seems to be consolidation.
Re: Angular 2: Built on TypeScript
#28Why not Dart?
Why Dart?
Re: Angular 2: Built on TypeScript
#29As if we didn't have enough reason to move on from Angular. Now you need to learn Typescript to contribute or grok the source files?
I am pretty sure that TypeScript just adds type safety and is optional. I don't see this as a huge negative and I actually see this as a positive. Just curious, what and why are all your reasons to move away from Angular?
[deleted]
Re: Angular 2: Built on TypeScript
#30As if we didn't have enough reason to move on from Angular. Now you need to learn Typescript to contribute or grok the source files?
I am pretty sure that TypeScript just adds type safety and is optional. I don't see this as a huge negative and I actually see this as a positive. Just curious, what and why are all your reasons to move away from Angular?
- Breaking changes
- Obtuse, verbose, non-performant code
- Did I mention breaking changes?