Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 2: Built on TypeScript

blogs.msdn.com

Post reply on HN
Print view View original

191–200 of 235 posts

Re: Angular 2: Built on TypeScript

#191

Post by zghst »

peferron wrote: post #185
BinaryIdiot wrote: post #155

Earlier quoted context omitted.

I'm sure the compiler is well built but stability is my main concern. JavaScript, even with its many flaws, is used by millions of people every day and is one of the most used programming languages in existence. That's a ton of testing through real world use. Since transpilers just compile to JavaScript, they can take advantage of some of the same stability of JavaScript for its output but the act of transpiling is o…

You have a very valid point regarding bugs. Transpiler bugs definitely happen. When I first tried using Babel - still named 6to5 then - instead of Traceur, it immediately broke my code because of an incorrect TCO implementation in Babel. Babel's maintainer (sebmck) is insanely responsive and the bug was fixed almost immediately, but still. If I used Babel or any other transpiler for critical production code, I would…

Babel is a completely different transpirer than all the others. It's goal is readable, understandable transpiled code and Sebastian (sebmck) is a genius robot wunderkind. I check the repo everyday and see new updates, bug fixes, etc. It is heartening to see someone give a project so much dedication.

I have an affinity for Babel unlike any other JS project (except React). They team works really hard to keep it interesting.

Re: Angular 2: Built on TypeScript

#192

Post by zghst »

ahoge wrote: post #99
shubhamjain wrote: post #31

Earlier quoted context omitted.

If type safety was the issue, couldn't they have tried Facebook's Flow[1] which believe would have reduced the technical overhead by large? [1]: http://flowtype.org/

Flow doesn't work on Windows yet. Atom seems to be the only editor which supports it. That plugin had its 2nd release just 3 days ago.

If I can get Flow to work in vim, I am sure it works in more than just Atom

Re: Angular 2: Built on TypeScript

#193

Post by mikerichards »

davexunit wrote: post #112
smrtinsert wrote: post #80

Earlier quoted context omitted.

Any dynamically typed language is absolutely horrible once you break a certain line count.

Citation needed. Static typing isn't a panacea.

The parent's post doesn't mean anything, but the please don't do a "citation needed". Even if he had a citation it wouldn't mean much.

That said, static typing does help with intellisense/code completion, on-the-fly error checking, refactoring, etc...

Re: Angular 2: Built on TypeScript

#194

Post by Alex3917 »

pfooti wrote: post #156
WhitneyLand wrote: post #82

Angular 2 is having a lot of pushback and challenges, but this may be a positive. First, there have been hard feelings over breaking backward compatibility. To rub salt in the wound the new syntax doesn't seem to buy you much for many basic scenarios. If you are going to push big breaking changes you need to show big benefits that are easy to understand at a glance. Secondly, the Ember community started small but has…

The typescript move is more along the lines of "we had these extensions to typescript we were calling AtScript, but now they're included in the forthcoming release of TypeScript, so we'll just call it Typescript". It doesn't seem to actually change any on-the-ground syntax, just what you call the language. another, more important piece (IMO) of response to the pushback they've been getting came during the new router…

> just what you call the language.

Being part of an existing project that's backed by both MS and Google is a significant value proposition though. I wouldn't have learned AtScript, although I'll probably end up learning Typescript now even though they're the exact same thing.

Re: Angular 2: Built on TypeScript

#195

Post by ahoge »

zghst wrote: post #192
ahoge wrote: post #99

Earlier quoted context omitted.

Flow doesn't work on Windows yet. Atom seems to be the only editor which supports it. That plugin had its 2nd release just 3 days ago.

If I can get Flow to work in vim, I am sure it works in more than just Atom

Define "get to work".

I mean something like this: https://atom.io/packages/ide-flow

Tool-tips, call-tips, auto-complete, type checking, and so forth. The kind of stuff you get with TypeScript or Dart.

Re: Angular 2: Built on TypeScript

#196

Post by ohsnap »

aikah wrote: post #46

I don't care what people say Angular totally suffers from the second system effect. http://en.wikipedia.org/wiki/Second-system_effect

I am holding out hope that this isn't the case because Angular is/was really brillant. But yes, it looks like version 2 got out of control.

Re: Angular 2: Built on TypeScript

#197

Post by bdcravens »

mikerichards wrote: post #188
bdcravens wrote: post #123

Earlier quoted context omitted.

Look at the list of contributors to the project (both in terms of numbers of committers and commits). Overwhelmingly Microsoft employees. Until it gains some serious momentum where it could successfully be forked and seriously maintained by the open source community at large, at this point it's a Microsoft product, and you have no choice but to trust their support and openness, so you can't hand wave away the trust i…

Uhhh...lots of Microsoft employees working on Typescript is a good thing. Pulling the old, "We're happy to leave this in "the community's" hands would be a bad thing for obvious reasons. Seriously, stop the FUD

You're right, no open source projects that weren't developed in the majority by a single large corporate benefactor have ever succeeded. We can trust those corporations: they have our best interests at heart. Now if you'll excuse me, I need to get back to my successful career building applications for the Google Glass.

Re: Angular 2: Built on TypeScript

#200

Post by peferron »

zghst wrote: post #191
peferron wrote: post #185

Earlier quoted context omitted.

You have a very valid point regarding bugs. Transpiler bugs definitely happen. When I first tried using Babel - still named 6to5 then - instead of Traceur, it immediately broke my code because of an incorrect TCO implementation in Babel. Babel's maintainer (sebmck) is insanely responsive and the bug was fixed almost immediately, but still. If I used Babel or any other transpiler for critical production code, I would…

Babel is a completely different transpirer than all the others. It's goal is readable, understandable transpiled code and Sebastian (sebmck) is a genius robot wunderkind. I check the repo everyday and see new updates, bug fixes, etc. It is heartening to see someone give a project so much dedication. I have an affinity for Babel unlike any other JS project (except React). They team works really hard to keep it interes…

Yeah, Babel and the Babel team is great. I got very suspicious of the project after my first experience with it broke perfectly valid code, but after reporting the issue and then another and having them fix it almost immediately they won my confidence back. :)

For production code I'd still stick to a whitelist of features that have been released for at least a month though. Babel is aggressively pursuing ES6 coverage and new features might not have all edge cases covered when they're released. Give them one month though and with their responsiveness it's 90% likely it's going to be fixed.

Post reply on HN