Izzy 
something I think nodejs software developers don't undestand is that using and running node-based software as an admin is miserable; it's basically impossible to package for a distro sanely, the actual software ends up taking up huge amounts of disk space, the dependency kudzu situation makes it really difficult to trust anything...
basically unless it's the only option I will avoid it. at least go software tends to result in easily usable binaries.
Jun 24 at 4:53amWeb
Show threadIzzy Jun 24
"just use docker" you know full well that this is not a solution it's just hiding the problem
Show threadIrisJun 24
@izzy Speaking as a bit of a container fiend, sometimes that's good enough, honestly. Would be nice if it were better, but... sometimes just packaging up all the shit the application devs make and hiding it in a neat little box makes things that much more sane.
Show threadIzzy Jun 24
@iris_meredith oh I'm a big container enjoyer (mostly debian on proxmox LXC) I just don't think packaging your software as 90% of an OS image is a good solution to it being awful to administer
Show threadIrisJun 24
@izzy This is fair, though, if I'm to be honest, I'm a little burnt out on writing applications entirely. We have too many damn apps, and so many of them are not very useful.
Show threadpurple 💜Jun 24
@izzy@social.shadowkat.net docker solves one thing: "it works on my machine".

the problem is, we're supposed to deploy 'your machine' in production,,
Show threadJan AntošJun 24
@purple @izzy well I have seen docker compose build environment that definitively did not worked on my computer, guess what, I am using podman and there was some obscure networking setup. Nope there is zero guarantee that one’s container setup will work on another one’s machine. If it is simple container than yes, but nothing today is that simple. If you want distribute app then we have flatpak or appimage.
Show threadF4GRX SébastienJun 24
@izzy I've seen a linux command line tool that was defined as an alias to run a docker container. This is going too far.
Show threadgürkan �’ :catlong_head_left::catlong_h::catlong_end_right:Jun 24
@izzy sad part is, that is accepted as a solution by the majority, which does not care about sustainability or maintenance at all. so that crap becomes the foundation of the next big thing and so on..
Show threadCall Me MañanaJun 24
@izzy after using it for the few Linux related tasks i have at work i've actually come around on Docker a fair amount
Show thread✨メッツォ✨  Jun 24
@izzy Literally this.
Show threadIzzy Jun 24
@mezzodrinker I feel like it's not talked about in those circles because like, that XKCD comic, "the average person only knows one or two node subcommands" sorta thing
Show thread🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸Jun 24
@izzy this is why I serverless
Show threadarclightJun 24
@izzy Static binaries are underrated. Once something is in production, it needs to not change until I change it. That's basic configuration management.
Show thread41402-nyanJun 25
@izzy I don't get how a bunch of text files can take so much space. Unless there is just so much of them.
Show threadAutumn (Going on a Fopbreak)Jun 25
@izzy as someone who does everything in node/js, highly agreed

i just run my code as a dev server lmao, i have zero idea how you'd package it outside of Docker, which sucks
Show threadIzzy Jun 25
@null I feel like you'd basically need to write a nix ... extension? if you wanted to package it without just slapping it in a container, to auto-generate the nix package definitions of all the dependencies recursively.. because instead you'd be packaging it inside a web of symlinks. :skull:
Show threadirina 🐇🌷Jun 25
@izzy if i ever see the phrase npm install i just bail. i love myself too much