Exactly that, Cloudflare complains about extensions.

What you are describing is not browser incompatibility. It's default fallback page that Cloudflare shows when it fails to run its javascript code.

Site owners such as programming.dev maintainers purposely onboarded Cloudflare to run those scripts, as that's how their anti-abuse system works.

Cloudflare gives its 522 error

This means Cloudflare is forwarding the request but the origin server times out. Meaning, it's the origin server that is unable to handle the IPv6 request.

https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/

No left at the company even knows how to work the erp properly. Because the person who set it up and customized it didn’t document or train anyone and then left…

That's not technical debt. That isn't even the definition of legacy code. That's a mess and a whole set of problems, but technical debt ain't one of it.

Technical debt is very real and can complete fuck companies.

Even though the situation you described is unfortunate, I don't think it has any relationship with the concept of technical debt.

The term "technical debt" conveys the idea that a resource is invested in a way that requires to be repaid later. The whole concept revolves around the idea that taking shortcuts doesn't eliminate the need to actually do the work to make things then right way. Rushing to a deliverable can leave a mess in your wake, but cleaning up that mess is also work that needs to be done and doesn't magically go away.

It’s very hard for “Safe C++” to exist when integer overflow is UB.

You could simply state you did not read the article and decided to comment out of ignorance.

If you spent one minute skimming through the article, you would have stumbled upon the section on undefined behavior. Instead, you opted to post ignorant drivel.

I agree. Those who make bold claims like "AI is making programmers worse" neither has any first-hand experience with AI tools nor has any contact with how programmers are using them in their day-to-day business.

Let's think about this for a second: one feature of GitHub Copilot is the /explain command, which is used to put together a synthetic description of what a codebase does. Please someone tell me how a programmer gets worse at their job by having a tool that helps him understand any codebase anywhere.

I don’t believe you have to specify the condition at compile time. I think that optimization would fall under dead code elimination.

How do you tell if some code behind a conditional is dead if the predicate that drives the condition is evaluated at runtime?

I’m reasonably sure compilers can shift the if out. I believe it’s called “loop invariant code motion”.

That scenario would only apply if the condition was constant and specified at compile time. There's no indication on whether var1 or var2 are compile-time constants or predicates evaluated at runtime.

Also, it’s worth noting that cargo is a fairly good package manager all things considered.

Yes, I'm familiar with Cargo. My point was to point out the absurdity and silliness of OP's remarks on "no bulky management of a virtual environment, no make files, no maven, etc." Once Rust fundamentalista take off their rose-tinted glasses, it's clear that Cargo is just as good (or as bad) as any contemporary integrated build system.

Maybe I’m dumb because I’m a backend dev, but if we can’t offload these tasks to Async tasks and we need to block the main thread, why can’t we just put up a loading screen?

That's not the problem. These tasks can be offloaded to async. The underlying issue, and the reason why I think this is an outstanding article, is that running code on the UI thread straight from handlers is easy and more often than not it goes perfectly unnoticed. Only when the execution time of those handlers grow do these blocking calls become an issue.

There's a gray area between "obviously we need to make these calls async" and "obviously we can run this on the main thread", and here's where the real-time mental model and techniques pay off.

“Don’t turn off the application we are saving” games have been doing this for a decade and you can’t convince me that your enterprise application is heavier than a AAA game.

You're missing the whole point.

The point is that running handlers in the main thread leads to far simpler code and, depending on the usecases, is adopted in scenarios where the approach works well with 99.9% of the conceivable usecases. But then the software starts to be modified and get features added, and some of these code paths start to do more things and take more time to run. When this happens, the 99.9% starts to shrink and some main thread blockages start to become more and more noticeable.

The article does a very good job in underlying the mental model that needs to be in place to avoid this slippery slope to become a problem.

You could just upvote Java 8 and Java 17

A database carry the schema, structure, that allow you to validate that you are still having the structure you want.

So do all file formats.

SQLite is both a file and a database, but what I’m saying is that people shouldn’t mess with the file, but the database interface instead.

The same holds for all file formats: don't go around licking random bits in a file, use a client instead.

I have nothing against third party clients, the important thing is keeping the structure.

That's what file format clients are for, and anyone can even roll out their own if they want it.

The facts a DB use the Filesystem behind the scenes, is an implementation details the user shouldn’t be much concerned about, some DB can do without Filesystems.

That's really besides the point. The point is that it doesn't make sense to frame using databases over files as using a higher level client over persisted data.