💾 Archived View for bbs.geminispace.org › s › discuss › 146 captured on 2023-11-14 at 08:39:29. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-11-04)

➡️ Next capture (2023-12-28)

🚧 View Differences

-=-=-=-=-=-=-

CircaDian: The Trouble With IDEs

CircaDian: The Trouble With IDEs

Reply to various replies, also CircaDian

Reply from winter

Reply from JeanG3nie

This whole discussion kicked off with me advocating for coding in a proportional font; then one of the various replies mentioned the trouble with IDEs, and it's a great topic so I posted about that.

Then there were some more replies and I thought we were done, but a few more drifted in; linked above.

The latecomers appear to share my appreciation for what VSCode and LSP (Language Server Protocol) have achieved; thanks for chiming in! It great to hear from people who disagree with me, but I'm happy to also hear some agreement.

One aspect I didn't touch on at all is what this whole thing looks like from the point of view of teams maintaining a new or less-popular language. LSP means you can provide an "analyzer binary", implemented in the language of your choice, rather than having to choose a set of tools to support and provide whatever each one needs. This creates a level playing field across languages that makes it much easier to create viable new languages.

Of course, there are still huge barriers to success for new languages, but at least this mosty takes care of one of them.

Posted in: s/discuss

☕️ Morgan

May 15 · 6 months ago · 👍 moonsheep

1 Comment

🦀 jeang3nie · 2023-05-15 at 15:22:

That's a great point. I think if you combine the effects of lsp with how llvm has jump started compiler development it explains how new languages have been flourishing a lot more in the past decade than the ones before.