patchguard

There are conventions, but like anything that isn't explicitly enforced, developers will do whatever they can/wish.

> Performance can be bought with better hardware.

I hate this argument. If current hardware promises you a theoretical throughput of 100 MB/s for an operation, someone will try to hit that limit. Your program that has no hard to understand code but gives me 5 MB/s will loose in the face of a faster one, even if that means writing harder to understand code.

Not so hard to believe tho. I work on a product that has parametrized feature flags. This means that, from a web interface, someone can say things like "activate feature X, on machines running operating system Y, at version Z, and are running product version W with license type Q". This is not a hard thing to build, and once you have it you can mix and match filters without being a software engineer or knowing how it works behind the scenes.

> copilot skirted that need by just analyzing the AST of code they host and using the nearby comments to identify what a section of code is meant to do.

I'm curious what it spills out for things like "Todo", or "this is probably broken", etc.

What HVMI is and how you can use it to monitor and/or protect your VMs.

Since when is Office a developer tool that runs only on dev machines?

Assembly also lacks features.

A mature framework should not have this kind of problems https://github.com/nodejs/node/issues/12115