News for hackers. Stuff that matters.
Re:From Markdown to remote code execution in Atom by scrollaway on Thursday November 23, 2017 @10:40AM (#15765665)
Look, I love Qt; I worked with it a ton, I contributed back to it, I even still work on LXQt sometimes.

But the rise of web apps, and Electron along with it, have turned the Linux desktop from a "you need to dual boot or use wine" machine into one where all my tools and apps are Linux compatible and have feature parity with Windows and macOS.

I also wish Qt would see more use, I also wish more people would write desktop apps using desktop frameworks when it's meant to be a desktop app, and I really wish people would start writing tiny CLI apps in nodejs and include 70 dependencies. But truth be told, I'm happy to live in a world where I can do 100% of what I do on Linux without feeling like a second class citizen.

I think the "Web on desktop" paradigm is the future, even if it's currently a bleak one. Ten years ago, it was becoming pretty clear that Javascript would be the future, and at the time that was a bleak prospect -- but tooling improved and today, things like Typescript, React, the plethora of incredible development tooling and excellent cross-platform compatibility have turned what used to be bleak into an excellent environment.

There's a lot of improvements that can happen with Electron, if rather than fight it we actually embrace it. Running 10 different web browser engines for 10 different apps may be silly, but what if Electron was global to the desktop instead of included in every fat app?

You'll note that Google has been dipping their toe in that water for years with ChromeOS; Mozilla also tried their version of it with FirefoxOS, which failed for a plethora of reasons that don't undermine the concept at its core.

Basically, JS on the desktop is in the same uncanny valley as it was on the web a decade ago. It's ugly, slow, overwhelming and changing too fast. But there's an end goal there, which doesn't have to suck.

Re:From Markdown to remote code execution in Atom by pjmlp on Thursday November 23, 2017 @11:52AM (#15766250)
The thing is, with the desktop Web in the end what we get is ChromeOS, a browser window manager that makes the actual kernel completely irrelevant.

The adoration of Electron apps among Linux users will be the final nail on the year of desktop Linux.

Re:From Markdown to remote code execution in Atom by chrisweekly on Thursday November 23, 2017 @01:42PM (#15767025)
> “really wish people would start writing tiny CLI apps in nodejs and include 70 dependencies”

did you mean /s/start/stop/ above?

Re:From Markdown to remote code execution in Atom by scrollaway on Thursday November 23, 2017 @02:07PM (#15767155)
Uh, yeah. People have definitely started.
Re:From Markdown to remote code execution in Atom by aussie1233 on Thursday November 23, 2017 @01:54PM (#15767092)
"Web on desktop" Reminds me of Win98 and how Microsoft tried to push that back then. It's just a bad security model. Technologies were different, but the security implications that lead to exploits stayed the same.
Re:From Markdown to remote code execution in Atom by z3t4 on Thursday November 23, 2017 @05:30PM (#15768242)
theres very litle reason today to make an electron app instead of a web app. especially if its just a client.