3 ms·
There is a certain practicality in running the same thing on the server as on your developers' laptops. Ubuntu and Debian are pretty similar, and using Debian
by michaelt 3y ago
There is a certain practicality in running the same thing on the server as on your developers' laptops.
Ubuntu and Debian are pretty similar, and using Debian gets rid of things like snap, which I'm glad to be rid of - but it adds an extra level of "well it works on my machine" which I'm not glad for.
If it's going to be hard to get that special different version of Java to work on the server, it should be hard to get it to work on the desktop too :)
Of course the rise of containers has made a lot of this stuff less relevant.
- dylan604 3y agoIf the headless server has a UI process running that is absolutely wasted resources. Having the same environment for the dev's laptop and the server seems like such a waste of resources. The two things are not the same, so don't try to fit the square peg in the round hole. Whatever these differences are, they should be able to be determined and accounted for in the deployment. To me, we've gotten a bit lazy and a bit too focused on the wrong things. I feel like this happened when we started running javascript on the server. That was such a shock to the system and all sorts of things had to be done since it just was not the normal way of doing things. Someone decided it'd just be easier to clone the dev's system and deploy that as a server. Like what the actual... I also totally feel the same way about running a Windows Server. Like why on gawds good earth would you ever think that was a good idea?
- chromakode 3y agoUbuntu has a bunch of non-GUI server flavors. It's a common base image for cloud VMs, similar to Debian. https://ubuntu.com/download/server https://ubuntu.com/download/server