Re:Thoughts on Rust bloat
by nickpsecurity on Thursday August 22, 2019 @01:41PM
(#20770571)
You might find this article interesting:
http://blog.johnnovak.net/2016/05/29/cross-platform-gui-trai...
well, I still think that Qt is the better solution, and so by an order of magnitude :-) it allowed me to write the software, which is being used in production in mac / linux / windows, while doing a ph.d. at the same time ; not sure I could have done the same with any of the other options in there (an older version was using JUCE but it was full of problems ; in particular JUCE's software renderer is much less efficient than QPainter).
And for all of REAPER's goodness, it took decades before getting a linux version.
Re:Thoughts on Rust bloat
by nickpsecurity on Friday August 23, 2019 @09:36AM
(#20777422)
Oh yeah, I agree. It's a good one. Several folks in the comments called out the author for not bringing it up. Personally, I think the author had a bias where any solution had to be close to the size of the native, standalone app.
One thing I wondered about Qt is if there's a way to trim out anything an app doesn't use. Have you seen anything like that?
There's https://qtlite.com
Along with the following shell command :
grep --only-matching --no-filename -R 'include <Q.*>' | cut -f2 -d' ' | sort | uniq
I disagree. I develop an audio workstation - https://ossia.io ; the total size is between 50 and 100 megabytes depending on the platforms. It uses Qt and LLVM and is itself around 500kloc so I'm already around the lower limits of what I can do.
My users, & much people on the internet keep comparing it in size to Reaper, another DAW where the binary is around 10 megabytes (https://www.reaper.fm/download.php) - but they wrote their own gui toolkit and language interpreter.