Gumby

Ow my neck

Joke’s on them, I don’t want any of the smart features

I see the Login with SSO option all over the place. Of course, that assumes the users actually understand what that means, and they know whether or not they need to click it.

I’ve definitely run into that. Even more frustrating is when there was one particular site that forced me to actually delete the last character of my password and then retype it. Just focusing in the field wasn’t enough, I had to actually send it a keystroke. And Ctrl-V to paste the password in manually didn’t count. I suppose typing a random character at the end and then deleting it would have worked too.

There’s been a ton of back and forth finger pointing but the more I hear about it (and other news about Krafton), the more my gut tells me that Krafton are the bad guys.

It does if you eat enough of it

I prefer the extended versions every time, but there are a few scenes here & there that do slow down the pacing a bit. However, the “Concerning Hobbits” intro to hobbits and The Shire at the beginning of Fellowship should have absolutely been included in the theatrical version. It sets the stage so much better and really drives home just how much of an idyllic life the hobbits are forced to leave behind.

Well shit, I’ve never seen AoC before - I’m not usually very interested in programming just for fun, but I might give that a try!

And yet here we all are, reading your comment. Maybe the algorithms on some platforms are that aggressive, but certainly not here.

I agree with your main point, although I think your example of COBOL being used to this day in financial institutions is actually the opposite problem. The guys that originally developed that shit were damn good programmers, but they were severely constrained by the available hardware, limitations of the language, etc. So they had to get really clever in order to make these massive, complicated systems work. In my experience, those really old legacy systems tend to be rock solid with near 100% uptime and almost no errors. They’ve never been rewritten because doing so would be a multi-year effort costing millions of dollars, and the end result would be a system that is most likely slower, buggier, and has less functionality.

TLDR: The old COBOL systems are unmaintainable messes not because of incompetent developers, but because the limitations of the available technology when they were originally developed forced a bunch of really good devs to have to get extremely creative and hacky with their solutions.