4 ms·
I really think that although this might be a boon to packagers it results in an inferior system wherein people end up with bloated,buggy packages. I don't want
by michaelmrose 11y ago
I really think that although this might be a boon to packagers it results in an inferior system wherein people end up with bloated,buggy packages.
I don't want to deal with 2 different package managers and new users are apt to be confused by the idea that they get packages from 2 different places.
- matzipan 11y agoWell, it's the system that is composed of packages. The app images would be distributed through an app center. Most users wouldn't have to touch the system packages in their daily use case.
- djsumdog 11y agoYea, I agree. I personally think that this is a huge step backwards. Look at Android and MacOS. You have these self contained packaging things that contain all their dependencies. You have the same dependencies in each package. You have a TON of wasted space with packages that have the exact same built-in libraries and jar files. Especially with Android, they could have made a real package dependency system, with slotted installs of all the jar/jar-versions from the official maven repos. When you install and app, it could install all its dependent jars. You'd still be able to do multiple versions of each of those jars, probably easier than it is with standard .so/.dll libraries. Projects like this are a huge step backwards is terms of DRY principals and general package management.
- matzipan 11y agoIs space really an issue in most non-mobile user devices nowadays? Consider the tradeoffs: a bit of space vs. packaging nightmare which results in old, buggy and insecure packages. This was posted a few days back on hn: https://statuscode.ch/2016/02/distribution-packages-considered-insecure/ https://statuscode.ch/2016/02/distribution-packages-consider... I am not sure if the whole jar package dependency management would work under ART.
- veddan 11y agoI wastes memory too, having multiple copies of the same shared libraries loaded.
- marcosdumay 11y agoMemory spend on executables isn't a bottleneck even on mobile. You are getting into embedded territory for this to become an issue.
- michaelmrose 11y agoI really hate that people have this idea. It's why people create apps which consist of a built in web server their own copy of chrome that connects to said server. In the end something that ought to have taken 10mb of space and 20mb of ram requires 100mb of space and half a gig of ram and still manages to be slow on a new system at operations that ought to have been fast on a ten year old machine. Down with the Javascript generation.
- matzipan 11y agoI've been spending a lot of time in the embedded area lately (sub-200Mhz 32k RAM automotive systems, firmware and fpgas) and I agree with you. But there's always tradeoffs. In this case you're trading some memory (which is cheap nowadays) for up-to-date, secure, usable apps, which seems to be a pretty complex thing to do. Nobody solved it so far. The people using node-webkit are offloading the library compatibility issues to the people who built Chromium and are provided with a consistent container to run their application in.
- takluyver 11y agoAndroid and MacOS each have a lot more users than desktop Linux, a lot more applications packaged, and applications get updated in a more timely fashion. Obviously that's not all down to a difference in packaging, but it does seem like the inefficiency of duplicated dependencies isn't all that big a problem. Android also runs on phones that still mostly have less storage and less RAM than our desktops, so you'd expect saving space to be even more important for Android.