Yeah but the Salesforce-ification was a long, slow process. We had our own independent offices and executives for several years. Then the gradual slow drain of the old guard...
I'm not surprised. A few months ago I was reverse engineering their login flow (I was writing a driver for Elixir & Rust), and was getting MANY stack traces and weird bugs happening with their authentication flow, especially around OAuth.
I also love places that are named after someone and it's slightly amusing/horrifying.
Harold Holt was the Australian Prime Minister in the 1960's, and went for a swim and went missing (yes, there are many, MANY local conspiracies this :)). So what did we do? Named a swimming pool[0] after him (construction actually started before his death, I believe).
It is generally agreed that Holt's disappearance was a simple case of an accidental drowning, but a number of conspiracy theories surfaced, most famously the suggestion that he was a spy from the People's Republic of China and had been collected by a Chinese submarine.
I don't care about memory usage for editors as much I care about input latency and responsiveness.
Jetbrains (IDEA IntelliJ, Pycharm, etcetc) put a lot of effort into making their IDE low latency as it was getting to a point of being almost ridiculous. Their editor is built in Java, and they run on their own runtime as they have so many hacks and tweaks to make it work as a desktop app as well (font rendering, etc).
Also handy (regardless of framework, language, etc) is if you use feature flags, if you're using actual valid credentials against a service or a local testing service (eg S3 vs minio, etc).
Enabling this for non-technical users really helped also report any issues they would see, it was great for testing environments.
Plus you would probably end up needing all this information anyway if you do any error tracking, so it probably exists somewhere already :-).