News for hackers. Stuff that matters.

A comment on Migrating Slack's Desktop App to BrowserView. Parent comment

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".

[ Parent | on HN ]
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.
[ Parent | on HN ]
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.
[ Parent | on HN ]
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.
[ Parent | on HN ]