News for hackers. Stuff that matters.
Re:Qt for WebAssembly by toyg on Tuesday June 19, 2018 @04:50PM (#17350203)
> I hope this "screw the OS, I'm rendering everything myself" strategy doesn't take off on account of that.

Dude, that battle was lost when Electron gained traction. I hate it with all my heart, but it's a sad reality.

Re:Qt for WebAssembly by OskarS on Tuesday June 19, 2018 @05:49PM (#17350544)
Electron uses platform-native font rendering. It's just Chromium, and Chromium uses Uniscribe on Windows and CoreText on Mac. Compare Chrome on Windows and Mac, you'll see the difference in text rendering.
Re:Qt for WebAssembly by toyg on Wednesday June 20, 2018 @09:22AM (#17355077)
Nobody cares. Developers use Electron because it gives consistent results across platforms, not because it looks native. If Chromium were to switch to a custom font renderer that looks exactly the same on all platforms, no developer using Electron would care - in fact, they would probably like it even more.
Re:Qt for WebAssembly by OskarS on Wednesday June 20, 2018 @03:09PM (#17358670)
I care! I care a lot!

Good font rendering makes SO much difference in how stuff looks. No joke: font rendering is the number one reason I prefer the look of macOS over Windows (especially now since WSL exists). I realize I'm a weirdo font nerd and probably alone in that stance, but working with computers mean staring at text on a screen for hours and hours every day. It fucking better be rendered right.

Re:Qt for WebAssembly by badsectoracula on Tuesday June 19, 2018 @10:52PM (#17352191)
Don't worry, people will simply start using Qt for WebAssembly with Electron to fix that issue.
Re:Qt for WebAssembly by jcelerier on Wednesday June 20, 2018 @06:01AM (#17353908)
uh... what ? the text on all electron apps looks like a blurred shit on my machine, and does not look at all like the text settings I apply.
Re:Qt for WebAssembly by wlesieutre on Tuesday June 19, 2018 @06:57PM (#17350953)
Yes and no. My biggest gripe with Electron is that it tends to murder battery life. It still gives you native text rendering, and it gives you native menubars which have some options if not always as many as I'd like. At least there's not a fake menubar at the top of the window.

There are other issues like contextual menus, in VS Code they're handled well and give you all the actions you'd expect. But in Slack it gives you the bare minimum OS included items and has their own "..." button on each message for things that ought to be in the contextual menu.

It can also do multiple windows (again, see VS Code which is a good example), but Slack stuffs everything into one window (preferences overlay is a good example of what should be separate) because it's a much simpler wrapping of a webpage instead of being designed as a native app would be.