Most of their products are like that. There are a lot of specific language support features in each one that may become available as plugins later on but not at the same pace or “fullness” as the specific product itself.

For example, PHPStorm has good JavaScript support but if you want really good Typescript support you should probably go with Webstorm.

Alternatively, I can totally write Rust code in Webstorm through the Rust plugin but I’m better off using CLion that has better support (or now RustRover which will be where all the latest Rust support features are added, although it’s still a preview product afaik).

Also worth noting though that there are indeed some “tiers”. Like Webstorm won’t support PHP but PHPStorm will support JavaScript/Typescript (again, not fully but enough to maintain a front end operating off your PHP backend)

[–] aksdb@feddit.de 7 points 1 year ago (1 children)

clion is also strictly separated.

[–] ursakhiin@beehaw.org 1 points 1 year ago (1 children)

As it should be. The needs of a systems language are very different than the needs of a virtualized or interpreted one. I honestly don't see how people use a single IDE for every language but I respect their choice to do it.

[–] aksdb@feddit.de 1 points 1 year ago (1 children)

I have a few projects where parts are Java, parts are Go and parts are C. Having that in a single workspace can be convenient.

[–] ursakhiin@beehaw.org 1 points 1 year ago

Even those I tend to open up in their specific IDEs when the time comes. It helps me separate the language but also the workflow.