[cmgriffing]

I think it's an interesting idea, but I feel like creating a whole new language has too much overhead for adoption. You would need to create a language server and extensions for every editor you want to support.

A language-specific DSL (Pulumi, CDK, etc) just works in any editor that already supports your language.

This is a similar reason to why I dislike most docblock-based infra tools as well. If wing is confident in their ability to maintain editor tooling, more power to them, but it isn't maintenance I would want to manage.

[shaiber]

[I'm on the Wing team] I get what you mean about adoption and maintenance overheads.

On the adoption front, we are aware it takes time for languages to get adopted. We also plan to release the Wing SDK to other languages soon, but the best DX is still provided by using Winglang itself simply because we are not constrained by what other languages support.

The language server is actually the same one for different editors, but we do need to create and maintain different editor extensions. The best supported one at the moment is VSC.

[cmgriffing]

> We also plan to release the Wing SDK to other languages soon

Awesome! I agree that your intended experience is likely to be more curated, but supporting other languages might really help. This is really cool to hear.

Also, I realize I might have phrased it poorly, but I meant exactly that about the language server. Language server once, but each editor needs its own extension. Even the extension wrappers around the language server could quickly eat up a lot of maintenance time because there is no true standard. Open VSX is pretty nice for cross editor extensions, but not too many editors use it, yet.

[shaiber]

Yea, no good way around IDE extensions. Hopefully if Wing gets popular enough the community will create extensions where there is demand for them.

Also, thanks for taking the time to give us feedback