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

121–130 of 235 posts

Re: Angular 2: Built on TypeScript

#121

Post by hokkos »

spion wrote: post #94
BinaryIdiot wrote: post #73

Earlier quoted context omitted.

> Transpiling may actually be the safest way to use JavaScript, especially given its rate of change. [..] A transpiler allows you to use these features now without any worry. I disagree and my original statement applies as much to TypeScript as it does to an ECMAScript 6 transpiler. If you want to use the new features and you're transpiling now you need to have a good understanding of the differences between ECMAScri…

I feel more comfortable writing TypeScript rather than using an ES6 transpiler, really. The compiler is built really well - you can observe the team's development process on github and I have to say the level is quite impressive (extensive code reviews and great discussions on the issue tracker).

The same can be said for Babel, and it is actually very simple to predict or retro-engineer the transpilation from ES6 to 5.

Re: Angular 2: Built on TypeScript

#122

Post by vonklaus »

AlwaysBCoding wrote: post #104
Firegarden wrote: post #84

Earlier quoted context omitted.

I have specifically avoided angular because I feel like it's a monster in that you are so tied to learning and understanding it's proprietary system. I too have moved directly to react. Can anyone comment on how the skills learned by learning Angular can be applied any where else?

You're 100% right. Once you're in Angular-land you are completely tied to the framework. You don't think about "how can I make X in my domain happen?" you think about "how do I make X in Angular happen". This coupled with the horrific Angular docs make it really tough to justify using from a productivity standpoint. I've moved to React as well and feel it's a 10x boost in productivity because I'm constantly thinking…

I am a newer developer, and this is how I feel. I didn't think it was normal. I always had problems grokking the docs as they are obtuse and thin. Also, things I find straight forward to implement in JS seem laborious in NG.

I am going to start learning react as well, and if you have any suggestions on how to get started, I would be appreciative of a few resources.

Re: Angular 2: Built on TypeScript

#123

Post by bdcravens »

discreteevent wrote: post #110
bdcravens wrote: post #97

Earlier quoted context omitted.

Your response seems defensive. I'm not speaking to Microsoft's motives, but to the psychology of developers who have been exposed to "embrace, extend, extinguish" for many years. They don't deserve trust just because "we're nice now, we promise". The same way that Google's shuttering of services over and over earns them a bit of discomfort amongst their users.

"deserve's got nothing to do with it". The source is open and licenced. If you make technical decisions based on this kind of emotion you will waste a lot of time going round in circles. Because once you start looking for the spooks they're everywhere. Technical forums ain't what they used to be. The problem for me is that this kind of Tarot card thinking is also now to be found in your local workplace. But there rea…

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 issue as "Tarot card thinking".

Re: Angular 2: Built on TypeScript

#124

Post by wycats »

coldtea wrote: post #119
skeeterbug wrote: post #93

"Special shout out to Yehuda Katz, who helped us design the annotation+decorator proposal which helped make this work possible." How in the world does this man keep up with all these projects? He needs to write a book on motivation.

> How in the world does this man keep up with all these projects? He needs to write a book on motivation. By dumping them mid-way and getting to the next shiny one? Anybody knows how this RoR kickstarter project finally went?

Yep. I shipped Tokaido and people use it. It was mentioned on Ruby Weekly last week.

You can get releases at https://github.com/tokaido/tokaidoapp/releases. Andres (who now maintains the project) released Tokaido for Ruby 2.1 (with support for Mavericks) recently and we're working on Ruby 2.2 support as we speak.

The org is here: https://github.com/tokaido/ and there are a number of auxiliary projects (muxr and tokaido-dns are the big ones) that I developed separately along the way.

Re: Angular 2: Built on TypeScript

#126

Post by solomone »

AlwaysBCoding wrote: post #104
Firegarden wrote: post #84

Earlier quoted context omitted.

I have specifically avoided angular because I feel like it's a monster in that you are so tied to learning and understanding it's proprietary system. I too have moved directly to react. Can anyone comment on how the skills learned by learning Angular can be applied any where else?

You're 100% right. Once you're in Angular-land you are completely tied to the framework. You don't think about "how can I make X in my domain happen?" you think about "how do I make X in Angular happen". This coupled with the horrific Angular docs make it really tough to justify using from a productivity standpoint. I've moved to React as well and feel it's a 10x boost in productivity because I'm constantly thinking…

It's not like anything you build in React is going to transfer over to another framework either. In fact, I've been to a lot of React talks and people mostly ask "how do I do X" in react. The last talk I went to they spent 10 mins talking about how you might make a spinner when data is loading.

I think that's the nature of any framework.

Re: Angular 2: Built on TypeScript

#127

Post by smacktoward »

BinaryIdiot wrote: post #66
usingpond wrote: post #6

As 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?

This is the main reason why I don't like using languages that transpile into JavaScript. I don't mind the languages themselves but transpiling into JavaScript now means you have to be effective in both languages instead of one to properly debug and you're also subjected to bugs that may or may not be known in the transpile itself. Everyone seems to hate on JavaScript but it's really not that bad to use.

"You have a problem with JavaScript. You rewrite your entire code base in TypeScript. Now you have two problems."

Re: Angular 2: Built on TypeScript

#128

Post by ianbicking »

JustSomeNobody wrote: post #21

Is javascript really so bad? Edit: Why did this question get down voted? It was an honest question...

I don't personally find TypeScript a rejection of JavaScript in the way that some other transpiled languages are. It feels to me like optional typing plus a bunch of features JavaScript will get in ES6 or beyond.

Re: Angular 2: Built on TypeScript

#130

Post by fryguy »

RussianCow wrote: post #98
fryguy wrote: post #95

Earlier quoted context omitted.

Would you complain if a c++ project started using c++/14 features, because "now you need to learn c++/14 to contribute or grok the source files?" Typescript is really just Javascript with type checking, and what would be used in browsers if they didn't have to deal with backwards compatibility.

I don't think that analogy is valid. It's more like if a C++ project started using a bunch of proprietary third-party language extensions, in which case, yes, I would complain because I have to learn some non-standard C++ derivative in order to be able to read the source code.

I disagree. Typescript is just ECMAScript 6, with type annotations. Most of the differences come from the language changes (ES5 -> ES6), than the superset that Typescript explicitly adds.
Post reply on HN