3 ms·
The problem with this premise is that by raising the bar for any IDE that wants to support that language, you risk the creation of an IDE monoculture.
by robonerd 4y ago
The problem with this premise is that by raising the bar for any IDE that wants to support that language, you risk the creation of an IDE monoculture.
- pjmlp 4y agoJetBrains is doing quite well with InteliJ monoculture.
- xxpor 4y agoIs that as true any more with the language server model? I'm not familiar enough with it to know how much is truely in the protocol vs what the editor still has to do themselves.
- robonerd 4y agoLSPs are great, I think they've proven fairly easy to integrate into many text editors. But consider something like the Scratch programming language. How many editors support Scratch? Once you stray from code-as-text, adding support to old editors often becomes infeasible and the effort needed to create new editors is a significant barrier to entry.