Jump to content

About That Office 365 and JavaScript Thing


steven36

Recommended Posts

By Paul Thurrott

 

https://s7d5.turboimg.net/sp/cb864c6f00cb21241c203d93a76c2320/wrong-again-monkey-boy-1024x576.jpg

 

A Microsoft employee claimed publicly that “all of Office 365” was being “completely rewritten” in JavaScript. And then all hell broke loose.

 

First things first. It’s not true. So if you were freaking out that Microsoft was somehow abandoning C# and C++ for its most mission-critical offerings, freak out no more. It’s not happening.

 

So what is happening?

 

A Microsoft program manager named Sean Larkin perhaps got a little overly-exuberant on Monday, when he tweeted the following. (I’ve edited out some nonsense.)

Quote

All of Office 365 is (almost finished) being completely rewritten in this little scripting language called #JavaScript.

And Skype
And Microsoft Teams
And [Visual Studio] Code
And all of [Microsoft Edge] Debug Protocol (instead of C++)

nbd

 

“nbd,” for you fellow old folks, means “no big deal.” Well, sorry, Sean. This is a big deal. And you got most of that tweet completely and utterly wrong.

 

Without even looking at his follow-ups and clarifications, I can tell you off the top of my head that “all of Office 365” is not being “rewritten” at all, let alone in JavaScript. Most of the new apps that have been added to this service over the past several years are indeed web-based. And most likely use some combination of web technologies, which could include JavaScript. (But also TypeScript, Microsoft’s superior JavaScript-like language.)

 

Skype is not being rewritten in JavaScript.

 

Microsoft Teams is not being rewritten in JavaScript. (It’s already web-based, however, and is being evolved into a Progressive Web App.)

 

Visual Studio Code not being rewritten in JavaScript. It has always been Electron-based.

 

The Edge thing could be correct, who cares. But Edge itself is a native app and is, of course, not being rewritten in JavaScript.

 

Sigh.

 

Anyway, he tried to clarify things in follow-up tweets when his original missive exploded intro controversy. Which shouldn’t have been a surprise. And yet, somehow, it was.

 

“It’s always the tweet’s you’d least expect to blow up,” he noted, obliviously.

 

Anyway, he finally corrected himself on Reddit, blaming Twitter’s character limitations for his many factual errors.

 

“We are not abandoning C++, C#, or any of the other awesome languages, APIs, and toolings that we use across Microsoft,” he clarifies. “Nothing [in Office 365] is converting to ‘all/completely’ JavaScript/TypeScript.”

 

Stupid Twitter and its character limits. Sigh.

 

But seriously, facts matter. And getting something this big this wrong is inexcusable.

Source

 

Link to comment
Share on other sites


  • Replies 4
  • Views 1k
  • Created
  • Last Reply

That clueless bloke must be my avatar's boss, the PHB.:)https://en.wikipedia.org/wiki/Pointy-haired_Boss

 

Everyone else at Microsoft knows it's going to be rewritten in COBOL and FORTRAN. :lol:

Link to comment
Share on other sites


I imagine Windows 10 written in Wolfram Language jajaja ... It would be so fast even in PCs with 512MB RAM and Intel Core2Duo jajaja

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...