Anyone successfully using typescript with react/flux?
I found it a bit cumbersome to use with most of the flux implementations
Angular 2: Built on TypeScript
161–170 of 235 posts
Re: Angular 2: Built on TypeScript
#162Looking at the example source code & having experience of AngularJs & TS, I would say this is a huge development in term of enterprise adoption. Statically typed, annotations, built-in dependency injection, comprehensive test support (easy to write testable code), declarative UIs, 100s of already available libraries & above all support from Google and Microsoft. I can say this with confidence that even with a complet…
Yea, I'm super excited that the Angular team has given us ES6!
Re: Angular 2: Built on TypeScript
#163Earlier quoted context omitted.
> 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?
coldtea, you just got served.
How does this compare with "Did you win the Putnam?"
Re: Angular 2: Built on TypeScript
#164Earlier quoted context omitted.
To be fair, JavaScript started out as a language that looks like Java. "JavaScript was designed with Java's syntax and standard library in mind. In particular, all Java keywords were reserved in original JavaScript, JavaScript's standard library follows Java's naming conventions, and JavaScript's Math and Date objects are based on classes from Java 1.0" -- http://en.wikipedia.org/wiki/JavaScript#JavaScript_and_Java
That cherry picking you just made just completely reversed what was actually said in that article: "A common misconception is that JavaScript is similar or closely related to Java. It is true that both have a C-like syntax (the C language being their most immediate common ancestor language). They also are both typically sandboxed (when used inside a browser), and JavaScript was designed with Java's syntax and standar…
Aye, I did cherry pick a bit, sorry about that. But still, if you go to Brendan Eich's wiki page [0], it says that he wanted to put Scheme in the browser, but was commissioned to create a language that resembled Java instead. I guess he ended up doing a little bit of both :)
[0] http://en.wikipedia.org/wiki/Brendan_Eich#Netscape_and_JavaS...
Re: Angular 2: Built on TypeScript
#165Angular 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…
About breaking backward compatibility - they mentioned at ng-conf an interesting thing today: you'll be able to partially migrate from Angular 1.x to Angular 2 in both ways - having either Angular 1.x app with some Angular 2 components, or Angular 2 app with some Angular 1.x components.
https://www.youtube.com/watch?list=PLOETEcp3DkCoNnlhE-7fovYv...
Re: Angular 2: Built on TypeScript
#166Remember Angular Dart?
It's still there and still will be in Angular 2.
Re: Angular 2: Built on TypeScript
#167Remember Angular Dart?
Angular 2 is heavily inspired by AngularDart. Angular 2 has a single codebase for JS and Dart.
Re: Angular 2: Built on TypeScript
#168Angular 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 main mistake, in my opinion, that Angular 2.0 is making is removing two-way data binding. The whole cornerstone of my love for Angular was the idea that wherever data was updated (view, model, server, another user's browser, etc.) it was trivial to make that update appear everywhere else. This is even more powerful when you add in a technology like WebRTC data channels or websockets.
I could just bind the data to the view, and if the user changed it, I could react accordingly. Data changing became an actual event that I could subscribe to. It abstracted away the onkeydown, onkeyup, onclick, etc. so that it just became ng-change. So much less mental noise when I'm developing when all I have to do is react to data having changed.
I hope this gets picked up. ES6 and TypeScript have so much to offer, but without a data-centric paradigm, I find I'm just not interested anymore.
Re: Angular 2: Built on TypeScript
#169Earlier quoted context omitted.
Nope, AtScript was doing runtime type checking (AtScript is basically traceur with some experimental features) while Typescript DOESNT. To be fair , I don't care, but that's an important precision. It means that the Angular team is giving up on traceur or maybe traceur and typescript will merge somehow in the future.
I don't see why anyone would want runtime type checking the way AtScript does it. With static typing, the compiler can catch type errors early, at the cost of rejecting some otherwise valid programs. With dynamic typing, that type checking is delayed until execution time. More programs are valid, but type errors are caught late. With AtScript-style late type checking, they took the dynamic type system and introduced…
You would almost never use the runtime checking in production. This is an optional feature that you would only use in development.
Re: Angular 2: Built on TypeScript
#170Earlier quoted context omitted.
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."
Wrong, JavaScript is valid Typescript, so you don't have to rewrite anything.