3 ms·

I think I 100% agree with this. There have been threads here about burnout and disillusionment, and I think it kind of feeds into this. There's so much churn an

I think I 100% agree with this. There have been threads here about burnout and disillusionment, and I think it kind of feeds into this. There's so much churn and confusion about what is the best way to do things, and there's no real guiding force - everything is still so young. For me personally, it's frustrating how so many new ideas are really solutions to problems tech itself has caused. I like to say that Docker is great, but really it shouldn't need to exist - packaging complexity is self-inflicted and a sign of an immature discipline. Also, what other discipline can spend millions of dollars, and 10s of thousands to millions of man hours building a package/framework/language/ecosystem, then decide a few years later that "meh, seems dated", and "look, this new stuff is so refreshing!". Again, the inability to focus is a kind of immaturity.

linuxdude314 4y ago
We are there though. Currently there is no need to use docker to run containers natively in many OS. Systemd nspawn, rocket, cri-o accomplish the same workflows with tight OS integration. We don’t hear about them that much, but almost anyone using k8s is not using docker at this point.
- orev 4y ago
  You’ve completely missed the point. By “docker” they mean the concept of containers, which is only needed because developers are so absolutely awful at keeping track of what libraries they’re using, and completely opposed to using OS packages like rpm/deb, that someone (Docker) finally had to say “screw it, we’re just going to lump everything into this binary blob that includes a whole set of OS libraries because we just give up even trying to get them the play nice with the rest of the IT ecosystem”.
- rileyphone 4y ago
  Still the same problem, which is that the OS introduces a bunch of baggage that requires an additional layer of virtualization. To quote Dan Ingalls: > An operating system is a collection of things that don’t fit into a language. There shouldn’t be one.
spacemadness 4y ago
Lots of confusion and yet a sense there is a lack of compassion for not knowing optimal solutions in the same wild west environment. Enter imposter syndrome. Enter disillusionment.

linuxdude314 4y ago

We are there though. Currently there is no need to use docker to run containers natively in many OS. Systemd nspawn, rocket, cri-o accomplish the same workflows with tight OS integration. We don’t hear about them that much, but almost anyone using k8s is not using docker at this point.

orev 4y ago
You’ve completely missed the point. By “docker” they mean the concept of containers, which is only needed because developers are so absolutely awful at keeping track of what libraries they’re using, and completely opposed to using OS packages like rpm/deb, that someone (Docker) finally had to say “screw it, we’re just going to lump everything into this binary blob that includes a whole set of OS libraries because we just give up even trying to get them the play nice with the rest of the IT ecosystem”.
rileyphone 4y ago
Still the same problem, which is that the OS introduces a bunch of baggage that requires an additional layer of virtualization. To quote Dan Ingalls: > An operating system is a collection of things that don’t fit into a language. There shouldn’t be one.

spacemadness 4y ago

Lots of confusion and yet a sense there is a lack of compassion for not knowing optimal solutions in the same wild west environment. Enter imposter syndrome. Enter disillusionment.