Hacker News Reader

Comment by revelation | Hacker News Reader

Embrace: https://nodejstools.codeplex.com/ http://azure.microsoft.com/en-us/develop/nodejs/

Extend: https://github.com/Microsoft/node

Extinguish: ?

Ugh. You realize there are like 3 people who are still working there who were around when this was really a thing? Yes, Satya was hired in 1992, but he didn't grow up in that culture nor did any of the other current leadership. Most people working there now were in grade school when that was actually a strategy.

Given all that Microsoft has been doing lately I'd really be surprised if this is all an elaborate ruse to squash node. Having been around when the actual "embrace, extend, extinguish" was running at full throttle, though, I can tell you what it does looks like:

"Full access to UWP APIs from Node.js applications"

When you use platform-exclusive features then you not only lose a major strength of node, but you put the owner of that platform in a position to start pushing developers around.

It's a choice for the developers. They can use Node standalone or inside a Universal Windows application with access to the underlying platform using JavaScript.

That did wonders for Java.

When was the last time they went all the way?

Read for yourself: http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish and http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt

Looks like it's been close to a decade. The CEO responsible for that whole ordeal is gone. When do people decide Microsoft has behaved long enough to be given a second chance?

I think it's pretty clear that this would take long time. Reputation it's not something company can get just by changing CEO or releasing few things as open source.

After all they still continue their aggressive patents usage and there is still uncertainness around audio/video codecs for web standards mainly because of Microsoft. Pretty sure others may remember some areas where their politics didn't changed for a bit.

> The CEO responsible for that whole ordeal is gone. When do people decide Microsoft has behaved long enough to be given a second chance?

If the company clearly changes it's course, right? Though it doesn't seem to be the case, despite two CEO changes since Bill Gates. Recent news show more or less what they are still up-to.

Yesterdays plans to stop producing Windows and "Win10 as a service": https://news.ycombinator.com/item?id=9521151

TypeScript influences the ES6/JavascriptNext feature & syntax development - lead by Mr. Hejlsberg (TurboPascal) who was responsible for J++, Windows Foundation Classes and C#. In 2012 Hejlsberg announced his new project TypeScript — a superset of JavaScript. (https://en.wikipedia.org/wiki/Anders_Hejlsberg )

Read Bill Gates (former internal) 1994 memo: "Windows: The Next Killer Application on the Internet": http://www.microsoft.com/about/companyinformation/timeline/t...

"The memo starts with a background on the Internet in general, and then proposes a strategy on how to turn Windows into the next "killer app" for the Internet."

The Internet plan "Microsoft Network": https://youtu.be/kGYcNcFhctc?t=17m16s

And the Office format thing in 2007, the Silverlight thing, the XBoxOne launch thing. It was just not as public, as they were not that successful.

All you did is make a list. Can you expand this into something coherent?

Office uses a documented XML format now, Silverlight is dead, and I don't see how Xbox One is in any way relevant.

Not sure how making Windows free is "embrace, extend, extinguish." Most operating systems are free.

People make new languages based on old ones all the time, so you're going to have to expand on the problem with TypeScript.

I could go on, but I'm not a teacher running through an essay with a red pen. You won't convince anyone with a comment-free list of events.

> Office uses a documented XML format now

It's still formats that can't be fully implemented without breaking compatibility with MS products.

PS: Personally I like what MS doing now and I accept that this can be serious change, but that would be dumb to trust them until like 3-5 years pass at least.

I will comment that, had you actually posted a link to the HN comment thread on your TS influencing ES6 development, you'd have noticed there are several comments as to how, no, they are not. In fact, they've diverged quite a bit from ES6, and now have work to realign TS with ES6's newer drafts.

I also really don't understand how a 1994 memo or the Microsoft Network plan are relevant. Those are both pre-lawsuit, how are they relevant today?

Might as well post some Friends quotes and some Pearl Jam videos.

I mean, as long as we are discussing 90s stuff.

Reply on news.ycombinator.com