Speak for yourself. I've been paying for my own developer tooling for 25+ years.
- The JetBrains suite of tools (Rider, CLion, DataGrip, Webstorm)
- Sublime Text
- Prior to offering Visual Studio Community Edition, I used to pay for MSDN if my employer didn’t supply it.
- Beyond Compare
- Recently paid for Tabnine Pro, the jury is still out if this is worth it.
IDEs should be replaced with libraries that allow one to operate over the code (or make IDEs allow you to script their AST manipulators)
Writing tests is not connected to the two above.
I need to know how the program ended up in that state. I can't reproduce this from a core dump or via a debugger.
Because you don’t know how to debug. Time travel debugging does exactly this.
I think the main promise of an IDE is being integrated. But maybe it could just be done with libraries.
Yeah, but the core dump doesn't give you an answer on how the program ended up in failure state, does it?
Interesting...
But monetization might not be the root of this since we have very sophisticated tools delivered as open source. The question then would be why the "dev comunity" is not interested in building tools like those mentioned in the article?
My guess is that tools like Reflexion Models doesn't ring any bells for junior/mid-level developers. They don't know exactly what to optimize when it comes to long-term maintenance. That's why we have so many parsers, linters, etc. and now typed languages (again!) and not Reflexion Models.
The other day I was looking for something similar to Reflexion Models: a tool that I could describe high level modules and its files (like a package), describe the dependency hierarchy between then and check if there is any calls between modules that break the hierarchy. For instance: getting a alert if there is a call to a repository from the a controller (DDD). It's a common problem for big teams with junior developers that could be solved by automation.