Re:Migrating Slack's Desktop App to BrowserView
by peoplewindow on Monday October 30, 2017 @03:11PM
(#15587973)
Why? Electron apps still have to be packaged for Linux. And cross platform apps can be written in Qt or Java too. Doesn't seem like Electron is the thing making the difference here.
[ Parent
| on HN ]
Re:Migrating Slack's Desktop App to BrowserView
by SomeCollegeBro on Monday October 30, 2017 @03:33PM
(#15588155)
Have you actually written a large scale cross platform app for Linux and Windows? Sure, Qt components will show up on both platforms. But to get them to show up the same tends to be an incredible headache, especially if custom styling is applied.
Re:Migrating Slack's Desktop App to BrowserView
by peoplewindow on Monday October 30, 2017 @04:36PM
(#15588649)
Yes, I have. Well, I guess it depends what you mean by large scale. But I wrote and shipped a Windows/Mac/Linux cross platform app using JavaFX with native packaging for each platform. I didn't try and match native widgets. I styled it to look like a desktop app.
It was quite productive and straightforward. That said, Java likes to use as much RAM as it can get even if it could release a lot back to the OS. It looks at it, sees it's free and thinks "I might as well take that".
Re:Migrating Slack's Desktop App to BrowserView
by chrisco255 on Monday October 30, 2017 @06:48PM
(#15589679)
We're talking about Slack, for context. Non-trivial QA effort to build cross platform apps, even with Qt.
Re:Migrating Slack's Desktop App to BrowserView
by t1o5 on Monday October 30, 2017 @05:24PM
(#15589027)
Cant you put java apps on the leash with Xmax and Xmin memory ? I might be wrong, but I thought that was the case.
Re:Migrating Slack's Desktop App to BrowserView
by sgift on Monday October 30, 2017 @05:51PM
(#15589246)
Yes, but within that leashes it will prefer not releasing back what it has. E.g. if you say minimum 256, maximum 1G, if you used 1G for a short time it tends to hold onto it. This is a performance optimization iirc - it is far cheaper to wait a bit if you need that memory again than releasing it to the OS and then requesting it back again.
Re:Migrating Slack's Desktop App to BrowserView
by yellowapple on Monday October 30, 2017 @06:31PM
(#15589565)
"But to get them to show up the same"
That shouldn't be the goal. Linux and Windows have different norms when it comes to UI design, and (usually) have completely different widget appearances. You can save yourself a lot of headaches by just specifying the bare minimum (i.e. the widgets themselves) and letting the user/system remain in control of exactly how they appear.
In other words, if you're treating desktop GUI design as equivalent to web GUI design and expecting your app to look the same across all platforms, you're going to have a bad time.
Re:Migrating Slack's Desktop App to BrowserView
by sidlls on Monday October 30, 2017 @04:29PM
(#15588598)
Why would you want them to be the same? What percentage of people who use slack on both platforms and who care whether the appearance is the same on both?
Re:Migrating Slack's Desktop App to BrowserView
by manigandham on Monday October 30, 2017 @05:56PM
(#15589281)
Many people expect similar UIs for better branding and easier workflow.
Re:Migrating Slack's Desktop App to BrowserView
by yellowapple on Monday October 30, 2017 @06:34PM
(#15589582)
I'd sooner guess that most reasonable people would prefer the UI be consistent within their chosen platform. Yeah, Slack's UI is pretty, but it sticks out like a sore thumb on pretty much every platform because it looks nothing like any of the other applications running on one's machine.