Thread · HN Continuity

The problem all these products have is these blog posts that describe in enough detail what the patterns are, out of necessity, also provide the information for the product to be cloned into a form that is then more dynamic and malleable for use by other developers.

It's clearly existential for JetBrains, and it's revealing that the opening goes for the fear with "but it hasn’t changed what it costs to be wrong" while ignoring that this hasn't exactly been a major concern for most software people for a scarily long time, including JetBrains themselves.