9 Jul 2013 7:55 AM #151
Ext JS already has a reputation of a product that is time-consuming to learn. It certainly has a learning curve.
9 Jul 2013 8:24 AM #152
I posted the link just to provide a nice overview for folks who haven't looked into TS yet. In my opinion, it's going to become (and is already becoming) a big deal in the web development world.
9 Jul 2013 1:47 PM #153
Lets hope SenchaCon makes some announcement about TS.
Also apparently they're making Ext more touch friendly, good news for people writing universal desktop/tablet apps
10 Jul 2013 12:45 AM #154
> they're making Ext more touch friendly
Ext more touch friendly - great news.
10 Jul 2013 5:53 AM #155
The only really interesting one is TypeScript. GWT has been around for a long time and is already practically dead (what a shock: no one wants to use Swing-like syntax to build JS apps). I've never heard of GorillaScript but the GitHub repo only has 190 stars.
I use CoffeeScript already for everything I do. I love it, and it helps a lot, but IDEs and tools still can't really help you in CS any more than they can in JS, because the tools have no idea what the types are. All it can do is guess and/or throw huge lists of possible matches at you.
Then there's Dart. Might have been interesting, except that it's a totally different language (not ECMAScript 4, 5, or 6). And since Google's goal is to get browsers to run Dart directly, it's a non-starter. There's no way Apple, Firefox, or Microsoft would incorporate a Dart interpreter and hand Google that kind of victory.
10 Jul 2013 5:58 AM #156
Please learn your facts before stating stuff you have no idea about.
10 Jul 2013 6:25 AM #157
GorrilaScript is brand new. Give it time.
10 Jul 2013 6:31 AM #158
Settle down, sparky. I know exactly how GWT works; I've used it. The syntax is horrible. Go find an example GWT app (if you can) and then laugh at the ridiculous amount of Java code it requires.
GWT code and Swing code are very similar. They're both verbose, over-engineered monsters, and there are far more concise and elegant ways to accomplish what they do. The only redeeming quality of GWT was that it was Java, and thus offered better type checking, tooling, and build integration (e.g. Maven). But that isn't enough to outweigh the sheer bulk of the code that building a GWT app requires.
Google themselves isn't even building anything with GWT. Everything they build is Closure or Dart-based. They've disassociated themselves with the project and handed it over to an open source steering committee. Why? Because even Google doesn't use it any more. Those are the facts. So sorry to upset you (not really), but yes, GWT is dead (or at least dying quickly).
10 Jul 2013 6:41 AM #159
Moving GWT to an industry driven forum isn't exactly "disassociation" on google's part. Google still have developers working on GWT. There were still GWT presentations at their last IO conference. And they have internal projects implemented using GWT. This discussion comes up frequently on the Dart forums. It's not "abandoned". At the same time, we're told, many of the GWT developers have moved to the Dart development. They are moving forward, as they should.
We could debated the merits of whether javascipt is, or should be, on its own tedious trajectory of abandonment in this industry. People are finding paths around it.
10 Jul 2013 6:42 AM #160
I do hope Sencha comes back with a full rewrite in Ext JS 5 / Touch 3, because a lot of this is carrying over from the 1.x days and it's really starting to drag the whole API down. But I digress...