Why?

This is excellent advice and makes me feel less crazy…

AWS is expensive and confusingly structured, but I’ve been impressed with the ECS stuff. The UI for all of it is also way overcomplicated and stupid, but once you have it working it works.

Off the top of my head we use AWS ECS which provides a rolling upgrade method. Push up the new container into ECR (from github actions after they pass tests) run the upgrade command, and new containers will start booting. Once they pass their health checks the load balancer starts serving traffic to them. Once they’re live, the old containers are removed.

We also use a blue/green deployment method so we don’t have to worry about breaking the production database with database changes.

We were talking about software development and deployment in this thread, not necessarily how easy your desktop GUI is to use.

I mean… all those buttons are essentially just calling a command line in the end. And coding that button takes more work so command line is always going to be more likely to be your only option. If you find commands arcane then that’s probably an argument that the help docs should be clearer or the commands themselves should be clearer.

Well, there’s the actual engineer response I was looking for

I am not a full network engineer so take my opinion with a grain of salt. From what I understand, NAT with IPv4 works really really well to mitigate IPv4 address exhaustion. Then there’s an issue with the amount of extra processing switches and routers need to do IPv6, we’re going from 32 bits to 128 bits which is a huge increase and for switches and routers that are handling packets as fast as technically possible with a low amount of resources typically, that’s a not insignificant hurdle.

It’s just easier to do IPv4 in every way, plus that’s what the world’s been using and is used to.

The language this guy is wielding is cringe as hell, has LinkedIn energy all over it.

lmao, how dare you be inquisitive

Yeah that’s probably how your phone gets everywhere, since mobile networks are usually IPv6

I’ve talked to several network engineers over the years about IPv6, engineers that work as hands on with actual production infrastructure as you can get. And they all said that IPv6 would likely never be fully adopted.

That single tool is still propped up by that collective decade of knowledge. ChatGPT would be nothing without sites like stackoverflow

You were able to post on there at all? Don’t they have extremely high barriers to entry for even question comments?

Appreciate the in-depth response! I’ve always been interested in Nix but I’m scared of change lol. And I’m a single systems administrator on a team of mostly non-technicals so large changes like that are … less necessary. Plus you know, mostly dealing with enterprise software on windows unfortunately. One of these days.

Right? If it’s about ease of insight into containers for debugging and troubleshooting, I can kinda see that. Although I’m so used to working with containers it isn’t a barrier really to me anymore.

I wish he had written why he’s so anti-container/docker. That’s a pretty unusual stance I haven’t been exposed to yet.

Where does this guy expect people to find his website? Because there’s only going to be a small amount of nerds who still use RSS feeds. Does he recommend a different search engine?

Eh I called them out on it, but I’d rather they be used to continue developing the code base, which can be forked if necessary. People should be smart enough to evaluate their beliefs, and if not well… something would have gotten them eventually.

I’d suggest making one on programming.dev and advertising it there on the more popular communities