Office for Windows (WIN32) will be an Electron app? I have no words. edit, since there seems to be some confusion: I am explicitly talking about the WIN32 variant, which he confirmed to be based on Electron.
Office 365 is being completely rewritten in JavaScript
361–370 of 459 posts
Re: Office 365 is being completely rewritten in JavaScript
#362As a side note, Microsoft login echo system sucks big time in the context of office. You have no idea which URL to use to login to office 365. Between login/logout/timeout/other office apps/personal accounts/business accounts/forgot password workflows browser redirects to various URLs at least a dozen times. And you keep seeing new URLs I am wondering how less tech savvy people are coping with their authentication wo…
Re: Office 365 is being completely rewritten in JavaScript
#363Hi there, original tweeter here. Just to clarify: no one said when this work would land, simply that we are working on it! Sorry to disappoint XD, but I guess blame the OP.
when you say rewritten in JavaScript, you mean acutally rewritten or just cross compiled to Javascript ? Or a bit of both ?
Re: Office 365 is being completely rewritten in JavaScript
#364Earlier quoted context omitted.
comment seems to be saying -- in modern windows (UWP) it'll be using native code, but microsoft is taking the easy path on win32. i guess some people are surprised that despite years of telling people that win32 is going away microsoft is finally making good. but I am not, I'm more excited than anything at another good sign that Microsoft is finally done with legacy windows.
> Microsoft is finally done with legacy windows. It's kind of sad; all the good stuff I use is basically legacy Windows. None of what Microsoft has done since Windows 7 has appealed to me.
Re: Office 365 is being completely rewritten in JavaScript
#365I wonder how often NoScript maintainers just feel like throwing in the towel.
I often wish we could just fork off the modern web and redo things the right way.
Re: Office 365 is being completely rewritten in JavaScript
#366Oh, just what Office needed: a rewrite that will almost certainly not even approach feature parity
Re: Office 365 is being completely rewritten in JavaScript
#367Earlier quoted context omitted.
Office client never used .net or C# to begin with
Actually at one point they went very close to replace VBA with .net. It was called VSTA and meant to be a mini visual studio in office apps. I believe one of the office apps shipped with it in Office 2007, then they killed it.
Re: Office 365 is being completely rewritten in JavaScript
#368Earlier quoted context omitted.
Why at all? I would expect, long term, the ideal solution for a “run in browser” solution would be WebAssembly, possibly with JavaScript glue to the DOM. If so, they probably can keep large paths of their existing code base. Also, I expect the existing code base isn’t small, so a rewrite won’t be ready soon. That makes cross-compiling from whatever they have now to WebAssembly or JavaScript seem even better options.
Well TFA is about a big-time rewrite of Office into JavaScript, so at least MS doesn't appear to see any perspective in WASM. Considering they are uniquely positioned to make it happen given their C# buy-in and probably more than just a bit of existing software to leverage, I'd say this is as strong a signal of non-endorsement as it gets.
Re: Office 365 is being completely rewritten in JavaScript
#369Office for Windows (WIN32) will be an Electron app? I have no words. edit, since there seems to be some confusion: I am explicitly talking about the WIN32 variant, which he confirmed to be based on Electron.
I’m an engineer in Office. This is not the case. The desktop app’s are fully native, and will remain so. They utilize React Native for a few components, but otherwise are written in C & C++.
So, what the hell was this guy tweeting about?
Re: Office 365 is being completely rewritten in JavaScript
#370Earlier quoted context omitted.
It's just a tiny example of how silly this whole thing is. What's the point of having a committee to draft and design an language that can't even be bothered to have a working Set implementation? It simply doesn't make sense.
It's a pointless example that's trivial to fix. There are actual problems with Javascript. The examples you and many other detractors mention expose the actual problem: You have no idea how to use the language because you don't use it. Instead you whine about some trivial things (At a method to the Set type... it would take minutes), or things you don't understand (prototypal inheritance).
> You have no idea how to use the language because you don't use it.
I do use it daily for more than 15 years.