2,137 karma · joined September 11, 2016
> I mean, for a web application most state should be in a database, but this takes some discipline.
This state could also reside in an image and Smalltalk has solutions like GemStone and Magma (OODBMS) solutions.
> And importing updated code to a live system sounds like a black magic.
Yeah, I don't think for most use cases this would be done. A new image would be built and deployed with the relevant code changes applied.
Start with a base image, import code pulled from the VCS repo, start the image, run some test verifications and copy the image to its designated virtual insurance host.
"deploy war" was pretty damn easy.
I would push back on this quite a bit. Many of the posts and discussions on HN are political masquerading as science.
However, right about the same time web apps were taking over the world there were thick client apps that were solving the problems of installation and and updates. Two of the prominent thick client applications doing this were iTunes and the browsers themselves.
Now fast forward a decade to the early teens and the ubiquitous use of smart phones. What is the single largest determining factor of platform success? Is it the ability for web apps to render on your platform's web browser or is it the breadth and depth of your platform's app store?
My rant is over, I wish web apps would die. I've wished that for most of the 21st century.