3 ms·
> Also, qbrt doesn’t yet support runtime version management (i.e. being able to specify which version of Gecko to use, and to switch between them). At the time
by carussell 9y ago
> Also, qbrt doesn’t yet support runtime version management (i.e. being able to specify which version of Gecko to use, and to switch between them). At the time you install it, it downloads the latest nightly build of Firefox.
This doesn't sound so good, and is the opposite of what I think people have come to expect. It's seems like the most straightforward solution is to hardcode a specific version of the runtime into the package, so that installing qbrt XX.0.0 gets you the runtime that corresponds to Firefox version XX.
- roryisok 9y agoIt has an upside though. If all apps share a runtime they're tiny in size. Every electron app installs its own version of chromium
- nevir 9y agoHow important is binary size for desktop apps, though?
- roryisok 9y agoIt's not that big a deal, but it all adds up eventually. I wouldn't want every .net or java app to install their own versions of .net and java. Sure, my laptop hd probably has enough space for that, but its unnecessary
- carussell 9y agoAnd every qbrt app is the same way. If there are two apps 'one' and 'two' written as node modules, and both have qbrt x.x.x in their dependencies, then installing both will leave you with two identical but independent runtimes. There's no sharing going on. A runtime that can't run the app it's supposed to (because of breaking changes across runtime versions) is also not a very useful runtime, shared or not.