I remeber there was a blog post from JetBrains where they complain about VSCode taking over InteliJ market, by indirectly asserting they don't understand why VSCode adoption was rising.
Surprise surprise, a couple of months later Fleet was announced.
There are two reasons:
- People don't know better (yes, they really don't)
- Language server allowed languages with abysmal tools to finally have some semblance of an IDE
None of us know the future, but in my opinion Fleet is a mistake:
- It tries to fight VSCode at VSCode's turf (an editor with primitive IDE functionality)
- while trying to be a testbed for new UI for JetBrains IDEs
- while trying to both serve the Language Server crowd and keep JetBrain's vastly superior language tools
- while diluting JetBrains' offer of development tools
Or maybe VS Code is just really good? I was skeptical for a long time as well. I am a longtime Emacs and JetBrains IDE user (starting with IntelliJ in 2013). A while back I gave VS Code a try again. I primarily used CLion for Rust and PyCharm. And I found that the Rust/Python is at least as good as in CLion/PyCharm (with the exception of Cython). And thanks to VS Code's rich plugin ecosystem, I have a Magit implementation that is almost as good as Emacs Magit, the same with VSpaceCode to get Spacemacs/Doom-like spacebar-driven workflows.
My JetBrains All Products Pack is up for renewal later this month, but I am seriously considering to let it lapse...
I think Rust support is comparable (probably because they both use rust-analyzer). I've found the opposite for Python. PyCharm is WAY smarter than VS Code.
Edit: more info:
https://plugins.jetbrains.com/plugin/8182-rust/docs/rust-faq...
That said there is one part where I still have to turn to VSCode and that's when I want live breakpoints inside of a Tilt powered Kubernetes pod. I like the way that those settings are persisted so that other dev's can also use the debug functionality with literally one click. If pycharm just made remote debugging easy I'd never have to open VSCode for python development (but I'd probably still open it for something else like a quick editor of a file -- it's like my new vim). VSCode shines for supporting odd-ball languages and libraries sooner than JetBrains - and opens relatively quickly, sublime is much faster and I still use it for large files -- I just wish it was a little less involved to extend like VSCode.
It's okay. And its ecosystem is also anywhere from okay to abysmal.
For languages (like Rust) that never really had any tools to begin with it seems like an amazing IDE/editor. In comparison to what IDEA offers for more established languages (anything from language support to framework support) it's ... just okay :)
Oh yeah, this is absolutely true. If VS Code is the de facto standard for your language, it's probably a decent experience. I use it for 6502 assembly.
But I see people talking up VS Code over Visual Studio for C++ or C#, which I find completely baffling.
This is from my experience: Just listen to most junior developers. They regurgitate and repeat marketing fluff spoken to them by twitter evangelists or twitch developer streams. I just spent the afternoon listening to it and it was sickening. You can't reason or get through to them. Compromise and nuance just feeds their pompous attitude.
/rant
Sounds like a nightmare! What do IT know about development to be picking tools?
Anything beyond the standard development image requires opening a request to IT and procurement, with the respective OK from management.
Developers require low-wage workers to prevent developers from doing the wrong thing. It's stupid.
I'm ok with you revoking Bob's admin privileges if Bob keeps installing malware, but don't revoke my ability to install Python because of it.
Every developer has their own way of being productive which involves different tools & software. Forcing everyone to use one standardized environment sounds horrible.
"We need to switch to tool Y".
There's usually a host of reasons I may not want to move to tool Y, but in most cases, it's because I don't want to have to learn yet another tool just to do what I was doing. Why? Cognitive overload... but also for some period of time I'm going to be much less productive. I don't want to be judged on that. you are saying I have to use Y... I'm going to be slower. Every estimate will be 20% more than what it was for the next Z months. I've got 10 years of muscle memory to undo. Is it worth it?
In most cases, really not. BUT... if someone mandated that, AND also acknowledged up front that the delivery expectations will be reduced for some longer period of time... perhaps it's OK.
On the JB topic, IntelliJ was one 'heavy' tool I resisted for a long time. "I'm faster in these other tools - notepad++, vim, netbeans, whatever". I was faster, for many tasks. Adopting something new was slow. I'm generally glad I did it, but I did it mostly on my own projects, and freelancing. Had I been under pressure to deliver at a high pace while having to undo years of habits/tools/processes that got me where I was at that time, it would have been far more difficult to deal with.
If you like to work in extremely low trust companies, you do you. If somebody trusts me to write production code but not to pick text editors, they are morons with red tape wrapped around their eyes.
Reduced pricing in year 2 and 3, but up front it's $600/year.
And... while someone's base pay may be a lot, these sorts of 'extras' might come from a different budget. And when there are a dozen services you're paying $20-$50/month/seat for, I know some managers start to scrutinize things a bit more. "Can't you just use the free version like other people do?"
I really like the licensing model they employ.
Also I think that it's more like $600/yr for companies.
Not really though. Extensions are frequently deprecated or outdated, need to switch to new alternative, don't play nice together, etc.
Anyway, there's no need to advocate for vscode, it's not an underdog. I imagine everyone here has already formed their opinion and tried JB IDEs, vscode, and other tools, and probably make use of all of them somewhere in their workflow.
Unfortunately my experience differs from yours in this area. It all of course depends on the languages you use, what you do, on which side of adoption curve you are, etc.
I work with .Net plus a plenty of web stuff, I'm rather conservative about plugins. And for me everything is quite stable in my area so that the plugins configured 5 years ago still work. Adoption of language server protocol in different languages and frameworks, adoption of .editorconfig helped a lot to stabilize everything.
VSCode Web as modern version of X Windows based IDEs is great, as yet another Electron app not really.