Well, they got the "Embrase Extend" part

Story: Microsoft releases JavaScript alternativeTotal Replies: 14
Author Content
Bob_Robertson

Oct 02, 2012
4:45 PM EDT
So any bets on when "Extinguish" will be tried?
tracyanne

Oct 02, 2012
7:37 PM EDT
It's no different from any of the other Javascript programming environments, it compiles the code down to standard Javascript.
flufferbeer

Oct 02, 2012
10:15 PM EDT
@tracyanne, I slightly beg to differ in that M$'s js alternative is CURRENTLY similar to "any of the other Javascript programming environmnts". I forget who said this, but someone famousonce said that Those Who Forget the Past are Doomed to Repeat it! You've much too conveniently FORGOTTEN about that whole craziness where the big M$ hitter$ effectively steamrolled the OOXML standard right over we innocent users. No question that the same thing will happen again with M$-js!

(start rant) What'll eventually happen, of course (as it always has!), is that the evil Macro$uck$ will "leverage" the mindshare of its new M$-JS recruits to create an entirely new, proprietary, and eventually INCOMPATIBLEe standard that breaks use of current standards for JS. That shall be the Extinguish which Bob_Robertson writes about. When this extinguish happens is WHEN some M$ Bad Cop higher-up manager starts throwing re$ources into all sorts of code "improvements' to Good Cop Hjellsberg's M$-JS, or else some M$ legal counsel higher-up somehow manages to get the Redmond empire's infamous restrictive EULA thrown into these "improvements" right just before the fork for M$-J$ comes out ---- (*ahem* Silverlight / Moonlight *ahem* *ahem*) (rant finish)

My 2 big c's.
tracyanne

Oct 02, 2012
10:56 PM EDT
In addition to compiling down to standard javascript it's open source under a permissive license.

Microsolf, in spite of getting ooxml published as a standard didn't use ooxml in their office products, and originally had no intention of ever using ooxml. It was a cynical attempt to appear open, when they weren't. The fact of the matter is with respect to ooxml Microsoft has been hoist on their own petard

In this case the code compiles down to industry standard javascript . In fact even Silverlight used industry standard javascript behind the Silverlight canvass, not some proprietary script like Adobe did with action script behind their flash canvas.

Silverlight is now a moribund product, and very few people are developing anything in Silverlight, Microsoft no longer supports it... one of the dangers of basing an infrastructure around a proprietary product.

So i call bullshit on your paranoia.
flufferbeer

Oct 02, 2012
11:55 PM EDT
@ta,

> In addition to compiling down to standard javascript it's open source under a permissive license.....

Nope. I stand by my snarky comments that the pre-fork M$-JS is CURRENTLY fully oss under its own license variant. They say (someone? who?) that a zebra never changes its stripes, so I maintain that in its always-present desire to get back mindshare, marketshare, and downright money(!), M$ WILL find some way to capitalize on M$-J$ --- you can downright BET on it.

> So i call bullshit on your paranoia.

Without violatin' the TOS here, right back atchya with mine well-founded paranoia :-o. You just refuse to see what WILL happen!

2more c's and now some zzzzzz's
Prisqua

Oct 03, 2012
12:36 AM EDT
I have Dell Studio model and am not able to install Linux. Can anybody help me please?

Visit my blog here
vainrveenr

Oct 03, 2012
12:44 AM EDT
Quoting:It's no different from any of the other Javascript programming environments, it compiles the code down to standard Javascript.
Indeed, GNOME and Mono's de Icaza brings out this and other positive aspects of TypeScript in TypeScript: First Impressions :
Quoting:The Pros

* Superset of Javascript allows easy transition from Javascript to typed versions of the code.

* Open source from the start, using the Apache License.

* Strong types assist developers catch errors before the deploy the code, this is a very welcome addition to the developer toolchest. Script#, Google GWT and C# on the web all try to solve the same problem in different ways.

* Extensive type inference, so you get to keep a lot of the dynamism of Javascript, while benefiting from type checking.

* Classes, interfaces, visibility are first class citizens. It formalizes them for those of us that like this model instead of the roll-your-own prototype system.

* Nice syntactic sugar reduces boilerplate code to explicit constructs (class definitions for example).

* TypeScript is distributed as a Node.JS package, and it can be trivially installed on Linux and MacOS.

* The adoption can be done entirely server-side, or at compile time, and requires no changes to existing browsers or runtimes to run the resulting code


OTOH, TypeScript is not completely without its negatives:
Quoting:The Bad

The majority of the Web is powered by Unix.

Developers use MacOS and Linux workstations to write the bulk of the code, and deploy to Linux servers.

But TypeScript only delivers half of the value in using a strongly typed language to Unix developers: strong typing. Intellisense, code completion and refactoring are tools that are only available to Visual Studio Professional users on Windows.

There is no Eclipse, MonoDevelop or Emacs support for any of the language features.

So Microsoft will need to convince Unix developers to use this language merely based on the benefits of strong typing, a much harder task than luring them with both language features and tooling.

There is some basic support for editing TypeScript from Emacs, which is useful to try the language, but without Intellisense, it is obnoxious to use




Quoting:They say (someone? who?) that a zebra never changes its stripes,
A remarkably similar quote comes from one of the common translations of the Old Testament's Jeremiah 13:23
Quoting:Can the Ethiopian change his skin, or the leopard his spots? then may ye also do good, that are accustomed to do evil.
(source: JEREMIAH 13:23 Can the Ethiopian change his skin, or the leopard his spots?...)

This reduces to the quintessential question "Can the leopard ever change his spots?"; a decidedly rhetorical statement, at that.



HoTMetaL

Oct 03, 2012
2:17 AM EDT
Fluffer and vainrveenr's paranoia may have some vailidity, but it's kinda hard to take either seriously when one refers to Microsoft as "Macro$uck$" and the other references biblical quotes. But as someone who suffers with Javascript's suckiness every day, I'll never be convinced that anything Microsoft can vomit up - and anything only usable in Windows no less - will be something I'd develop with.
r_a_trip

Oct 03, 2012
4:19 AM EDT
It's crazy, but I'm not afraid that MS will try to abuse TypeScript to create lock in. They have behaved remarkably well regarding C# and the CLR and they've never sued over the non-ECMA bits. I have no reason to believe that TypeScipt is a Trojan Horse. (Yeah, I think I need to check my stripes.)

The thing that bothers me, is that every Dick, Tom and Harry is trying to come up with a better JavaScript on their own. Worse than that, the resulting new languages are just putting a nice layer of icing on top of JavaScript and the resulting code of these tools is just the same old JavaScript.

Why don't all these parties come together in an Industry Consortium and tackle the problem where it's really at? Seems to me that JavaScript is deficient and that it needs a major overhaul. Why not adress JavaScript and the interpreter itself? Now the world will end up with twenty new ways of writing the same garbage code "better". While it would be painful, why not give all future browsers a better scripting engine?
Bob_Robertson

Oct 03, 2012
10:00 AM EDT
@TA,

As it is right now, it's not bad. But this is just the same pattern Microsoft has used in the past. They've embraced it, they've extended it.

I won't even try to say that the extensions aren't good ones. I'm not a programmer.

What I am is a Linux user, and Microsoft, as a publicly traded company, has only one overriding priority: Maximize shareholder value.

They do that by getting people to pay for their products. Lock-in is THE primary way they do that, since they can't depend upon making a better product.

Which means getting people to stop using Linux and F/OSS. To do that, they extinguish.
flufferbeer

Oct 03, 2012
11:50 AM EDT
@vainveinr,

Not a big programmer either, but good to know about Miguelo el MonoManiac's technical impressions. I wrote before

"WHEN some M$ Bad Cop higher-up manager starts throwing re$ources into all sorts of code "improvements' to Good Cop Hjellsberg's M$-JS, or else some M$ legal counsel higher-up somehow manages to get the Redmond empire's infamous restrictive EULA thrown into these "improvements" right just before the fork for M$-J$ comes out "

I don't know WHO the extinguishing Bad Cop(s) will eventually be (and I doubt that Hjellsberg's team, Tracyannie, or many others know either), but in my well-founded "paranoia", I'm going to keen insisting that despite all those CURRENT postives of HypeScript, there is still some unknown M$ Wolf lurking around in JSheep's Clothing! And V V, I happen to know that AESOP is the one spread around this fable of the wolf in sheep's clothing, so there ;o!

++ Bob Robertson

fb
tracyanne

Oct 03, 2012
4:45 PM EDT
Does anyone here use Visual Studio?
CFWhitman

Oct 03, 2012
4:54 PM EDT
Well, I've used Visual Studio 6 in the past. I may end up doing some AutoCAD programming in a newer Visual Studio in the future (all the AutoCAD programming I've done previously was in AutoLisp or VBA, but VBA support has now been dropped in favor of .NET support).
tracyanne

Oct 03, 2012
5:57 PM EDT
Are you locked in to Microsoft?

I would suggest that people who use Windows and Microsoft tools will use this tool, which is, after all merely Microsoft's version of CoffeeScript, and all the other JavaScript entenders, and those that don't use Microsoft tools won't.
caitlyn

Oct 08, 2012
4:04 PM EDT
@flufferbeer: The quote you were looking for is: "Those who cannot remember the past are condemned to repeat it." -George Santayana, from "The Life of Reason" (1906)

The book is still well worth reading over a century later.

Posting in this forum is limited to members of the group: [ForumMods, SITEADMINS, MEMBERS.]

Becoming a member of LXer is easy and free. Join Us!