4 ms·
> If the application can control the whole stack, then the application author can fix it. You are right, but the other point is that it becomes the application
by jrochkind1 13y ago
> If the application can control the whole stack, then the application author can fix it.
You are right, but the other point is that it becomes the application authors responsibility to fix it.
If you're bundling apache httpd with your app, and there's a security flaw and a new version released, it becomes your responsibility to release a new version of your app with the new version of httpd.
If there are 1000 apps doing this, that's 1000 apps that need to release a new version. Instead of the current common situtation, where you just count on the OS-specific package manager to release a new version.
Dozens of copies of httpd floating around packaged in application-delivered VMs is dozens of different upgrades the owner needs to make, after dozens of different app authors provide new versions. (And what if one app author doesn't? Because they are slow or too busy or no longer around? And how does the owner keep track of which of these app-delivered VM's even needs an upgrade?)
- jacques_chester 13y agoYou're describing what you see as the advantages of the shared hosting scenario and in the blog post I linked, I explain why I think that business will be progressively squeezed out by VPSes and SaaS. In any case, there's no difference in kind between relying on an upstream app developer and an upstream distribution. You still need to trigger the updates. And you might have noticed that stuff is left alone to bitrot anyhow.