Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities [email protected]
Why is this necessary? I thought we've moved past language-specific IDEs.
We have? JetBrains never has stopped offering them.
Who wouldn't want an experience tailored to their main language? I certainly favor PyCharm over Ultimate
JetBrains is not representative of every editor / dev. Language servers mean I can use Emacs / Vim / VSCode / whatever else I want and have IDE features for whatever language I want.
Just as JetBrains is not representative of every dev, neither are LSPs. Some developers want a specialized IDE for their language(s), some want a highly customized editor with their language servers. As long as you efficiently produce code that works, who cares what other people use?
You can do that if you want to :
Like many of our IDEs, the functionality of RustRover can be installed as a plugin in IntelliJ IDEA Ultimate.
But if you only care about a particular language/stack you can use the dedicated IDE, it's cheaper and the UX is optimized for your use case.
That's a JetBrains plugin. It is just for JetBrains applications, and it closed source, right? Language servers are basically the metric system of IDEs. I can go from Emacs to Vim to VSCode and just use rust-analyzer for my IDE backend.
I don't understand the benefit of using JetBrains specific plugins that only work with JetBrains.
Because I (and many others) find their products to be far superior to the competition.
This. I'm using PyCharm with the new UI, and watching my colleagues struggle with VSCode is a bit painful to see. Not saying you can't be productive with it, but why make your life harder than it needs to be?
Same here but with WebStorm.
JetBrains users kind of live in their own weird bubble. Of the ones I've worked with, a decent number didn't even know how to use git, they just relied on the built in vcs tools
And? Do you get high off of the smeeeelll of your own farts, sir madam?
I think there's something for everyone. Some people want one editor for everything, some want one tailored to their language needs
This is the right answer, and I wish more people would grasp that.
Tech has an abundance of people who really need to be right in an argument. I've had this same argument with a developer at a client company of mine. Just couldn't let it go when I said I was comfortable with the Jetbrains suite and used their language specific tooling instead of VSCode.
Yea, I was thinking the same. I have the JetBrains toolbox, and already have these installed:
I don't really get why they need to make 10 different IDEs for every language, instead of just consolidating everything into a single UI/IDE.
For pricing it doesn't make that much sense, anyone that wants more than 2 JetBrains products is better off buying the entire toolbox.
I'm still waiting for Cobolilissimo and Fortransformer...
You know that you can use IntelliJ Idea Ultimate to get all of these in one package?
How does that work?
All of the languages from their other IDEs are available as plugins: https://www.jetbrains.com/products/compare/?product=idea&product=idea-ce
And there is already the Language Server Protocol, which basically everyone else uses.
The Jetbrains IDEs go further than many language servers do.
This is likely just rebranded intellij with some rust specific plugins and some UI adjustments like pycharm, goland, etc.
All the JetBrains IDEs feel like basically the same platform with different plugins and tweaks.
They wanted to showcase again that if you contribute to an open source project under a CLA, ie. the previous Rust plugin for Intellij, they will take your contributions, make them close source and sell them back to you.
They don't require CLA, since it's MIT license. So what they showcase is the benefit of copyleft.
Is this IDE going to make it impossible to install the Rust plugin in their other IDEs? Like is there anything preventing a user from continuing to use the Rust plugin and CLion after this has been released?
No. The plugin will continue to work, but JB will no longer release new features and bug fixes for it.
They can come in handy, for some people. I am certainly happy with VSCode
VSCode isn't language specific, is it? Why would they come in handy?
Almost all of these IDEs have language-specific features in them. PyCharm has Scientific tools (like SciView) for generating graphs using code and data. Rider features a pretty nice Windows Form builder for generating and creating GUIs for applications. Etc.
I can't imagine it being very useful or practical to unload all these language-specific plugins each time you open the program to write in a language that can't utilize those features.
You build workspaces with vscode but the real magic is you never have to switch to visual studio or spend time configuring plugins for a new workspace each time you start a new project
Because sometimes you have an irrepressible need to spend cash on an IDE?
What I am saying is that I don't need an IDE to program stuff. I am fine with VSCode with extensions. With extensions, VSCode can be a multi(programming)language IDE. I don't see the need to have different IDEs for different programming languages. They do have their benefits.
Marketing
I would've liked it more if they didn't deprecated IntelliJ Rust in favor of RustRover, I liked being able to write Rust in any JetBrains IDE if I needed it, now I'm stuck with an old, unsupported version of the plugin.
Well, you can still have the up-to-date plugin, you just have to pay for it now.
funny
agreed
Your username gave me anxiety.
u and me both
I liked using CLion for both Rust and C++, now I see they outright deprecated the Rust plugin
It would be nice if it would work better
As in... ?
Last time I used it it couldn't even show errors in code that couldn't compile without using clippy all the time, which is suboptimal
It is slated to be release in mid 2024, so if you reported the bug, it should probably be fixed by then.
Hopefully
