[austincheney]

> I have no doubt that Rome will massively increase the producitvity of thousands of companies and developers

I would like to see that measured.

My suspicion is that many developers are already too reliant on tooling and that reliance harms productivity rather than improves it. Bundling those tooling concerns eliminates some operational costs associated with a plurality of tools but increases dependency upon the tool.

This problem is not a technical problem (as in how do I solve a problem), but a cultural problem (as in what is the proper way to solve a problem). It comes down to the difference between a product focus (what do we ship) versus an operational focus (what do we work on).

[Oddskar]

I think you're being very selective with what you call "tooling" here. I understand where it's coming from though, and I agree that in some circumstances people are adhering too much to what might be perceived as "standards" instead of building or using something more fit to the task.

On the contrary I would also say that I see a lot of developers not being reliant enough on tooling. A simple example is getting very acquainted with the debugger in your language of choice. It's very common to sprinkle logs everywhere instead of properly learning how to step through code.

[austincheney]

I mean tooling as generally as possible, everything outside your application's execution runtime and the shell it runs in. Of course developer's will benefit from a code editor and a language compiler (assuming there aren't many), but how much tooling do you really need to deliver a product?