[kibwen]

> Outside of Slack

Slack has a standalone app? I've only ever used the web version. What more does it do?

> Discord

Likewise, I never even realized Discord had a non-browser implementation.

> WhatsApp

I never even realized that WhatsApp had a non-mobile implementation.

> they definitely need native access to local APIs

Which ones?

> And now they are arguably failing to push it to themselves

Er, the whole point of Mozilla is to champion standards-based web tech. They're rewriting their UI using CSS/HTML/JS because this is feasible today, whereas it wasn't in 2005. So I ask again, why would Mozilla want to retain XUL instead of making web technologies more powerful?

[toyg]

> Slack has a standalone app? [...] I never even realized Discord [...] I never even realized that WhatsApp [...]

But that's exactly how Electron and friends got popular: they allow for web-first development. Desktop support is a bonus for people who need it.

When Mozilla started working on XUL, the future of the web looked a lot like XML and fat clients. Applications would be built by desktop developers targeting the desktop in a way that would allow for the web to integrate in the background. They wanted to bring the web to the desktop, woo-hoo!

As it turns out, the opposite workflow won: applications are now built by web developers targeting the web, in a way that allows for desktops to come onboard where required. In this scenario, XUL is just too complicated for people who simply need "a web view with a couple of extra APIs". This is still "bringing the web to the desktop", the fundamental role of the runtime is exactly the same; but the paradigm is opposite to what Mozilla had envisioned.

> They're rewriting their UI using CSS/HTML/JS because this is feasible today

XULRunner/Gecko was already built on CSS and JS, but it lived in a desktop paradigm of pseudo-native widgets - because HTML interfaces were terrible back then. It wasn't even a performance issue, but rather that everything was a page refresh because nobody knew any better. AJAX had not been formalized, and XMLHttpRequest was used (guess what) to pull actual XML. HTML4 was considered a hack that was supposed to eventually go away. It wasn't a "this is not possible today" problem, but rather "why would anyone want that?". Already there were lots of arguments on whether JS was "good enough" for desktop development, whether CSS was too verbose, and so on...

> why would Mozilla want to retain XUL

XUL is battle-tested to a different level, having survived almost 20 years, and it's a better option for pure-desktop development than web views. If Mozilla had paid more attention to its evolution, rather than going on quixotic adventures like FFOS, maybe they could have competed with Electron-style apps. Alas, now it's probably too late.

[kibwen]

> Electron and friends got popular

Maybe I'm just an old fuddy-duddy (I'm in my 20s, jfc), but I don't see how Electron's popularity is considered a given. I know plenty of people who use the given services, but none who use the desktop interfaces. VS Code is the only Electron app that I've ever seen used in the wild. Am I just hanging in the wrong crowds? Which ones should I be looking at, if so?

> It wasn't a "this is not possible today" problem

Hence "feasible" rather than "possible". :P (And conspicuously not "easy" rather than "feasible", either...)

> maybe they could have competed with Electron-style apps

I sound like a broken record by now, but I still don't see what people think Mozilla has to gain by offering a native GUI framework that people have already proven they don't want. And frankly, I think FirefoxOS, while ill-fated, was at least audacious. :P

[__derek__]

> VS Code is the only Electron app that I've ever seen used in the wild. Am I just hanging in the wrong crowds?

Just to note: Atom is the original Electron app. I assume you've seen more people use that than Code.

[flukus]

> As it turns out, the opposite workflow won

Maybe for you, definitely not for me. Most of the applications I use daily are desktop ones and I'll refuse to install an electron one unless I have to.

[wott]

His point was about the fad amongst developers (well, "developers"...), not users.

[coredog64]

> Slack has a standalone app? I've only ever used the web version. What more does it do?

Chew up a bunch of RAM and glitch display compositing if my experience is typical.

[hvidgaard]

My slack has been running for days now, and it's humming along at 50mb.

[duncanawoods]

Electron is multi-process. If looking in Windows task manager, there will be the initial process at 50 Mb and then e.g. 7 more background processes.

[hvidgaard]

That puts it at 250mb. That is quite a lot for a chat app.

[M_-]

> Likewise, I never even realized Discord had a non-browser implementation.

Can't give an answer on slack, as it's not something I use (and I wouldn't use any of the three services if I had a choice, but you don't get to make choices for entire communities as an individual and chat apps are about communities..), but I can say something about discord.

Custom keybindings, ability to do things like push to talk while you're in game, general integration with your OS desktop features (systemtray, native OS notifications), GUI that can overlay over your full-screen window ( like this: https://youtu.be/aVQyk_GX7aE?t=98 ) and probably other features I haven't paid attention to.

> I never even realized that WhatsApp had a non-mobile implementation.

http://www.theverge.com/2016/5/10/11653606/whatsapp-mac-wind...

Released in May, 2016.. and the webapp launched in 2015.

> Which ones?

Are you seriously asking that of terminal emulators that are supposed to be drop-in replacement for iTerm or Gnome Terminal and whatever else? how do you think your bash scripts can operate without breaking on your local data in a webapp without added native calls? I feel like I'm getting trolled here.

> Er, the whole point of Mozilla is to champion standards-based web tech. They're rewriting their UI using CSS/HTML/JS because this is feasible today, whereas it wasn't in 2005. So I ask again, why would Mozilla want to retain XUL instead of making web technologies more powerful?

So a great deal of selective quoting up till here while acting sassy and not paying attention to what was quoted to support the point yet still asking the question?

Why would they retain a competitive edge when other platforms like electron are attracting all the developers to enhance their application with native access goodness, why indeed.

I'll quote it again.

> Whether you need to migrate an existing web application to the desktop [...] or want to integrate your own cool features into the browser, XUL warrants serious consideration.

Is what Electron and Chrome actually do for people now, successfully, in droves and was an aspiration they had before. As for what is feasible now that wasn't before.. electron is not going away any time soon and webapps haven't replaced native. Even more so on mobile platforms, as 90% websites are begging you to install the app with full screen popups.

[kibwen]

> still asking the question?

Yes, because the question isn't "how is this useful", it's "how is it in Mozilla's best interest to invest in this?" Mozilla came up with XUL because they wanted a cross-platform way to develop a large graphical application, and given that they're an open source organization they figured they might as well try to popularize the framework to hopefully get some volunteer contributions to the codebase. But XUL was never an end, only a means to an end, and the technology itself no longer has any strategic advantage.

As for "failing to execute" on taking over the world of desktop apps with XUL, I don't think Mozilla will lose any sleep over it. The secret sauce to Electron isn't Chromium, it's Node.js. We can say that Mozilla failed to execute the opportunity to popularize server-side Javascript first... but that's Rhino was for, and really, nobody in 2005 would have foreseen that developers would eventually want to write their backends in Javascript. :P

[pjmlp]

> Why would they retain a competitive edge when other platforms like electron are attracting all the developers to enhance their application with native access goodness, why indeed.

Be careful with generalizations, I am surely not part of that list and know quite a few others that want their computers Electron-free.