@laurel @p

> I don't think nginx is a typical micro service. It has a shitload of features, a ton of plugins and can be stretched to support a multitude of use cases. It even comes with a scripting language

yeah i wouldn't consider it a microservice, it could be by size of binary/container deployment, but that's a measurement in density not in functionality.

> I get that. The the problem is that the web is not an OS and there is a difference between an online service and a utility application. I also get that the plan is to make it turn it into WebOS that has g*ogle at the center with OSS programmers being abstracted away along with the hardware.

materially little difference if we're speaking tcp/udp/etc but i get what you're saying. a utility application i guess could be considered a microservice if it's serving i/o or sockets of some sort 🧐

> My problem with these is the same problem I have with gentoo, and I'm gonna paraphrase @p here,

i've known p a long time, i've likely heard this before. but let's find out.

> when you learn gentoo, nix, Talos you don't learn unix, building programs or running in Ram, you learn gentoo, nix,

i was right. and i agree.

> Talos. Whereas with CRUX and Slack you do learn unix. And if you need to, you can minimize disk writes without having to go through next-best-thing and all the baggage it carries with it.

i started with unix in the late 80s/early 90s, moved to bsd, then linux, etc. i'm a bit past the learning linux/unix pattern and more about tooling that makes my life simpler. crux is okay, i just chose to build my own. slackware is fine, but it's just not a very interesting system to me.

most would be surprised to know that my systems are boostrapped and maintained with a single script/service called servo. it builds out a complete stripped down linux distribution and keeps me in a simple space.

all the baggage is stuff i typically get paid for fucking with. although it makes me stressed out, i have to eat.