The point is that having near or below 0 rates has been a terrible policy for almost everyone, just as increasing them in response to inflation is going to hit most people hard now.
A problem has been kicked down the road for years, it was always going to blow up in our faces.
I think you might be missing parent comment's point. The way I read it they aren't saying that old code is better, just that you used built everything up from scratch generally (or to a much greater extent than nowadays) instead of using whatever framework is in fashion this week
>Your manager should of deflected this sort of stuff
Also keep in mind that there is a good chance the manager might have had OPs back in all this, maybe it's just the managers boss who has unreasonable expectations (maybe due to poor communication from the manager about changing requirements etc).
> Let's take take a look, using the disastrously bad unix libc timezone tools
Are there any more examples of them causing issues to warrant being called "disastrously bad"? This post just seems to have one example of bad error handling when they the TZ env var is set incorrectly.
I'm genuinely interested if they actually are bad since they are used a lot.
It seems to be everywhere (even on the top rated comment here). Biden himself is dismissed as being not left enough by a lot the online population from what I can see.
Because he wasn't the the fashionable choice for Democratic nomination (Sanders) he's reduced to being just an old guy who isn't Trump but is in the right party without anyone even bothering to even read his Wikipedia page or look up some of his speeches on youtube.
He's a passionate politician and an empathic speaker who has the experience to be a realist and appeal to republican voters too. He's exactly what is needed right now.
Sanders wouldn't have had a chance to get in, but even if he did he would just polarise things even further.
A problem has been kicked down the road for years, it was always going to blow up in our faces.