Slashdot Mirror
Google's Angular 2 Being Built With Microsoft's TypeScript
itwbennett writes Big news for fans of static typing! Google and Microsoft have partnered to both enhance TypeScript and rebuild Angular in the TypeScript language. TypeScript, Microsoft's attempt at improving on JavaScript development, has been out there for a while without a notable use case. Likewise, Dart, Google's attempt at a language which accomplishes many of the same goals, hasn't seen a lot of traction outside of Google. With Google creating the next version of its popular framework Angular 2 using TypeScript, some weight is being thrown behind a single effort. Of course, Angular has its fair share of haters, and a complete re-write in version 2 that breaks compatibility with previous versions isn't going to help matters.
Yes @ script is a superset of Typescript and it will be used in Angular 2. Not really a hot news story.
Democracy Now! - your daily, uncensored, corporate-free
Bollocks. TypeScript is open source, just like Angular.
It's good luck to be superstitious
I don't know how to tell whether I should care or not. Is it a language for creating angles? Mathematica can do that.
If they haven't finished it, I don't think would care anyway.
I should use this sig to advertise my book ISBN-13 : 978-1501515132.
Looks like a return to the old "embrace and extend" to me. And we know how that worked out.
=^..^= all your rodent are belong to us
Next step: make Angular maintainable and non-magic for mortal programmers.
Shut up with your facts so I can keep spelling Google as Scroogle and Microsoft with a dollar sign.
So what exactly is angular?
So why should I start using this, when Google has a history of abandoning their projects after a couple of years?
And it too will have its own way of doing things that nothing else does, just like Angular and React are right now. At least jQuery was open from the beginning that devs should know the language that it mostly shielded them from. Now it doesn't seem to matter; job postings are mainly for those who can write , not JavaScript. Don't know the particular framework du jour (or preferably *all* of them)? Tough.
"Wait. Something's happening. It's opening up! My God, it's full of apricots!"
Take 2: "those who can write *insert framework*..."
Use take 2.
"Wait. Something's happening. It's opening up! My God, it's full of apricots!"
Yes let's all just not bother learning anything ever because something new that will replace it is always around the corner.
In a month
Release 0.9.0 of Angular was 52 months ago and the appearance of the next framework that topples it will be the first. As a web developer, if you haven't actually used Angular for at least experimental purposes by now then you're an old fogy that's likely to get canned for someone more current.
Angular 2.0 won't trip up anyone and going with Typescript was a smart and pragmatic decision; the Angular team does not indulge NIH, apparently. That sort of humility and wisdom is both rare and a big part of the reason Angular remains popular. The tools that typical Angular developers use already integrate Typescript declarations for auto-complete, detecting errors, etc., and now that will just get stronger.
Google could have used their momentum and mind share to bull AtScript into yet another Javascript hairball. They could have and they didn't. That deserves acknowledgement.
So Typescript is the way. Microsoft has actually managed to contribute something they can't monetize to the modern web stack. How times have changed.
Maw! Fire up the karma burner!
Every time someone writes "open source language", a pet dies.
Programs can be open source, but languages are not programs. They are specifications of syntax, grammar and semantics. Maybe we have an Open Source compiler for the TypeScript language, but who defines the language itself? Is it a foundation or similarly open group participated by the community and key players of the industry, or is it steered behind closed doors in some meeting room in Redmond, WA? That is what matters.
Compilers... nobody pays for a compiler nowadays, and Microsoft is very aware of that. They are not stupid.
Angular is the shit. My term for web development with JavaScript pre-Angular (and similar tools) was "Web Assembly Language" (WAL). It was so fucking tedious, it took so much work do do simple shit, etc...
Angular isn't for every project, just like sometimes you have to be the poor fucker writing assembly language for some very narrow cases. But for most projects it (and tools like it) are the shit.
Perhaps but I recently got back into Knockout on an engagement, and I'd rather use Angular at the dentist than go back to that du jour again.
I bet you'll soon see job ads like:
"Must have at least 6 years experience on the next-big-thing of next month."
Table-ized A.I.
Apparently no one is allowed to disagree with you.
Otherwise my client isn't interested
http://saveie6.com/
IE invented Ajax and css. My have people forgotten this. Much of IE 6 css had css 3 functionality. Just Web standards moved away from it in 2001
http://saveie6.com/
From the summary (emphasis mine):
Microsoft's attempt at improving on JavaScript development, has been out there for a while without a notable use case.
That is not what 'use case' means (https://en.wikipedia.org/wiki/Use_case). The phrase you're looking for is "without a notable real-world use".
I haven't used Angular for pretty much anything. I've used Ember, though, because someone else on the team liked it. I mostly do server-side development anyway. I mostly just leave the client-side stuff to the colored-pencil jockeys.
I despise Javascript and wish it would die a horrible, ugly death, allowing something not completely made of shit to take its place.
I'm a web developer, and my web services don't trust your shitty client-side code (nor do my data integration components trust your poorly-constructed files), so they'll enforce restrictions that will make you whine and cry and you'll have to just deal with it. Why? Because data integrity and business rules are more important than your precious animations, your stupid by-convention framework's auto-generating code style, or your garbage "architecture". And that's also why I hate Javascript. It's not so much that it isn't useful, but it lets so many incompetent idiots act like they have "mad skillz".
A year ago they were slowing work on AngularJS to put more effort into a complete rewrite with AngularDart.
Dart is a better language than TypeScript and it's a Google creation... I have no idea why they did this.
I don't care about Angular. It's just another tool for the saps in the web page mines (and one that can get you trapped in those mines as well).
TypeScript, OTOH, is the greatest addition to JavaScript I've seen. No more messy .prototype., and much less "can't read property 'x' of undefined". It's not there yet, I must say. I would like it to add some more transformations instead of just type checking, but if you have to write in JavaScript: do yourself a favor, and check it out.
You remember that? lpStr and things? Where you prefixed some cooked up type notation to the variable name? What can possibly go wrong?
(The reason, at that time btw was that their C compiler was too crappy to do type checking itself).
What major Google product uses Angular?
It's not a complete loss. Virtually all of these frameworks are doing the same damned thing and implementing the same damned patterns just with different code. And underneath Angular or WhateverReplacesIt will be the usual heap of JS libs - JQuery, Underscore, Backbone et al. So knowledge is transferable even if AngularJS stops being fashionable.
What does jQuery has to do with this?
Anyone can point the cool things that one have and the other doesn't. Sure static typing is nice and all but I rather dislike static typing for big iterative projects, refactoring static typed code is a pain in the ass. Yet at the same time static typing makes a lot easier for a new dev in a big project to start being productive without breaking the whole thing (although test-driven development in dynamic typing languages help a lot in this regard).
Also how are the tools for typescript? Having static typing but no auto-complete IDE is a major drawback. In my opinion the main advantage of using static typing after compile-time errors are the auto-complete IDEs. What about debugging? Coffeescript can be debug rather easily on browser debugger because all variable names remain the same, Clojurescript has the REPL that I believe can push code into the browser, what about typescript?
Visual Studio 2013.
go away or i will replace you with a very small shell script
In other new, Angular 3 is planned for next year using MVVM pattern and Google's new HTML5+JS generator that was previously used for converting Flash. Same as with Angular 2, it is not backwards compatible and will be maintained for 2 years.
He really does have the knack for programming language design. I didn't get TypeScript at first, but with 1.4, it clicked. The great news about this is that Angular is a highly visible framework, and with this, more people will look at TypeScript and be willing to use it. Thanks to type definition files and definitelytyped.org, you can use a ton of JS libraries right now; hopefully, more people will officially maintain these files.
Also, this makes it easier to recommend it's use in work projects. Being able to say: "It's good enough for Angular, it's good enough for us" helps a ton.
You praise MS for contributing something they aren't monetizing ... but do you choose to work for free?
You praise MS for contributing something they aren't monetizing ... but do you choose to work for free?
Occasionally. Much like many for-profit businesses that use and rely upon open source software, I too contribute to projects that either interest me or are important to my livelihood.
Maw! Fire up the karma burner!
Fair enough! Objection rescinded.