“npm install our project dependencies. Download this 5GB file onto your five year-old laptop. Install docker. Build and start the containe—”
You bolt awake in the mountains of Carthage. You are not online. It is 217 BC. You are the general Hannibal, and you have changed your mind. The future cannot come to pass. Rome must burn.
@beep every new tech comes along, "it's now so easy build a basic website! Just use these arcane proprietary commands, and make sure your project is dependent on something you can't access"
Meanwhile html, css and JS huddle in the corner
@ronanmcd @beep
I like docker/containers.
Sometimes I need to make web applications serving research models.
Such models are written by researchers, and rely on that specific version of R and libraries that has been deprecated 10 years ago, as well as some python library that is not published anymore and some glue to make it work with some Fortran library that needs some very specific hooks to work. Of course you can not change anything, because it has to be the same model to make results reproducible.
Then it has to be installed by someone else on a server I have no access to. Go explain to them how to install that kind of stuff into their system, while most of the people doing this are also researchers trying to figure out what Apache is...
With the container I can just tell them, look run this command and then have a reverse proxy pointing at the selected port.
Most of them don't even bother with the reverse proxy and just serve the docker on port 80 and that's it, fuck SSL too complicated.
