Live data from Hacker News

JetBrains cancels Fleet

blog.jetbrains.com

21–30 of 87 posts

Re: JetBrains cancels Fleet

#21

Fleet started as our attempt to explore a new generation of JetBrains IDEs, developed in parallel with those based on the IntelliJ Platform. Over time, we learned that having two general-purpose IDE families created confusion and diluted our focus. Rebuilding the full capabilities of IntelliJ-based IDEs inside Fleet did not create enough value, and positioning Fleet as yet another editor did not justify maintaining t…

I want to begin by saying I love JetBrains IDEs. I go out of my way to personally pay for PyCharm Professional, DataGrip, Rider, and others, and have done so for years, so I can use it at work where the next best thing provided to us is VS Code, or Visual Studio...

Please, for the love of all things almighty, re-invest in your core IDEs. That's what you're known for, and that's what professional developers want.

I don't want a glorified text editor that does a few cheap tricks, and is 'AI first'. I know I'm going to piss off a few people here rubbishing VS Code, however people are blown away when I show them how much more powerful PyCharm is when debugging complex code.

Its embarrassing that there are many popular, numerously starred, issues across JetBrains' YouTrack that have been open for nearly a decade, that are already well integrated features in other, free, IDEs.

However all is not lost - you have a great suite of products that need much more tender love and care. They'll see you through.

You already have AI in the AI Assistant plugin. Make your core fleet of IDEs worth the investment, for new and existing JetBrains customers alike. AI, agentic or not, will only get programmers so far before it's time to toss the kids toys then break out the real tools that require human intuition, domain knowledge, and reasoning.

To pick up on one of the points in the article:

> Combining them in a single tool results in a disjointed experience, so the Fleet team chose to stop competing with IDEs and code editors and instead build a product focused on agentic workflows. This led to a pivot to a new product: an agentic development environment.

You don't need to develop an entire IDE/environment for this. Develop plugins/enhance the existing AI Assistant plugin for these workflows that integrate with your existing IDEs, 'the real tools' I was talking about above.

I feel like this new "agentic development environment" is making the Fleet mistake all over again, when you could be value-adding to your already great suite of IDEs directly by way of plugins, and also continue to refactor and improve your IDEs along the way.

Re: JetBrains cancels Fleet

#22
It's probably a wise move and not so different to what many other companies have experienced in the past.

Netscape tried to remake Navigator whilst halting development on the old codebase, and it killed them.

Microsoft tried to remake Word, the rewrite failed. Luckily they had continued to develop the old codebase in parallel.

Google tried to remake Gmail multiple times. Every attempt failed.

Apple tried for years to remake MacOS Classic and failed every time. Eventually they had to buy and reskin NeXTStep.

Banks are full of war stories trying to migrate off their old mainframe codebases, and often giving up.

I kinda expected Fleet to die from the day it was first announced. IntelliJ is an extremely mature product that's hard to compete with. They've continually managed big changes to it to keep up with changing fashions and trends in the IDE space, most recently with their new Islands theme that launched yesterday, with integrated coding agents and so on. It's outlasted continuous competition from free IDEs that are always abandoned after enough years pass and whichever executive was championing subsidies moves on or retires (see: NetBeans, Eclipse, VS Express, MonoDevelop...). VS Code isn't so different. Fleet was clearly a reaction to that but the concept was not innovative and focused on reinventing wheels that users wouldn't be able to tell the difference for and which would consume most of their budget, like writing a new UI toolkit, or using a split frontend/backend architecture. Same mistake Mozilla made. Meanwhile IntelliJ was continuously refactored and improved, so Fleet chased a moving target even when they reused a lot of code.

Although people will hate to hear it, the history of the IDE market suggests that eventually MS will get tired of funding VS Code without a big revenue stream to justify its existence. Executives like making new projects and being able to present growth because it represents glittering future potential, but they hate being landed with the maintenance of loss making legacy projects when the originators move on. There's no glory there. For all their problems, JetBrains aren't going to lose interest in their core products due to random executive churn, and that has given their core IDEs a remarkable staying power.

Re: JetBrains cancels Fleet

#23
post #12

Last week i cancelled my Jetbrains sub after a decade of daily driving it. I just cant take the performance issues anymore. Across 5 different machines all kinds of actions would just take ages and it got worse every year. Moving to Apple Silicon made it bearable for a few months but somehow Jetbrains manages to get slow even on a M3 Max with 36GB RAM. Ive been fiddling with configs for years, i tried everything sinc…

[flagged]

I've been using Firefox and Jetbrains for about a decade. Firefox is currently using 0.8% CPU while streaming music in another tab. The only speed difference between it and Chrome is that Chrome will prefetch pages in the background, which appears to make it faster on clicks. However, even were it much slower than Chromium alternatives, I would never give up my fully functioning uBlock Origin.

But anyway, in regards to Jetbrains, its performance certainly seems to be degrading over time. I'll try to explain why I still use it. First of all there is high friction to change IDEs when I have memorized every shortcut and configured every panel to my liking. I have within my IDE the terminal, the DB viewer and query executor, the debugger, the profiler, HTTP client, LLM chat, etc. Configuring all of this elsewhere would be a large pain in the ass, especially when switching computers/jobs.

More sticky still is the functionality. I've unfortunately become reliant upon, or perhaps fortunately been able to learn, the advanced features of the thing. Advanced refactoring tools that I trust to work without review, because they do. Quick shortcuts to insert large chunks of custom boilerplate. Perfect inference of method definitions/sources (try this in a Rails codebase in VSCode; it doesn't work). Other such things that I take for granted but that probably aren't in the competitors.

It might be possible to replicate this functionality with about thirty plugins from random authors in vim/VSC, but I'd rather just pay my yearly license fee and get good working software. Yes, it takes a couple of seconds to do certain things, but it saves me a lot more time than that.

Re: JetBrains cancels Fleet

#24
post #10

Earlier quoted context omitted.

Dropping Fleet is a good move. Just please for the love of God focus on your IDEs. Stop getting distracted with AI slop.

>Stop getting distracted with AI slop In the business cycle this is particularly risky. You'll have a smaller base of users that don't want AI slop, but will keep using your AI anyway even if it's there. But what you lose is the large paying corporate customers that demand 'soup de jour' that end up going to VScode or whatever, and you may never get them back. Building software is hard, being profitable at it is even…

If JetBrains want's to provide a simple plugin for Copilot or Anthropic to keep the vibe coders happy, I'm not going to complain about the feature. It just seems for the past couple years they have been primarily distracted with AI: AI Assistant, Junie, and now agentics.

Re: JetBrains cancels Fleet

#25
post #22

It's probably a wise move and not so different to what many other companies have experienced in the past. Netscape tried to remake Navigator whilst halting development on the old codebase, and it killed them. Microsoft tried to remake Word, the rewrite failed. Luckily they had continued to develop the old codebase in parallel. Google tried to remake Gmail multiple times. Every attempt failed. Apple tried for years to…

"Banks are full of war stories trying to migrate off their old mainframe codebases, and often giving up."

Most of the time it's a question of trying to apply "death by a thousand cuts" to their codebase, which works well enough as long as you're in the periphery, but eventually they start moving into "core business", you know that entangled mess that has 60 years old code that still runs today, and they realize they need to rewrite all of it, which will take a long time, and cost a lot of money, and they forget about it again for a few years.

It's the same problem everywhere with large and old codebases. You can easily amputate a tentacle here and there, but as soon as you get to the core of it, it is basically one giant monolith, and with age there has been added loads of "integrations" or "shortcuts" between various subsystems, and nobody in the company today has any idea why it is like it is, it just is and it works.

A bank I used to work for had somewhere around 50000 batch programs running nightly. Some were the same program running multiple times, but at least 20000 were "unique" programs. All of those programs had to fit like pearls on a string, each working off of the output of the previous program in the chain.

Untangling that mess is like peeling an onion one layer at a time, with the added bonus that the output of one program might be the final result for some report, and at the same time the input for some other program that needs to do something else.

Add to that, that there's no inherent problem with the mainframe or COBOL. They both work, and reliably as well. Both can push some serious IO through the system, loads that many x86/x64 builds would struggle with.

The conventional answer to IO problems is eventual consistency, which doesn't really work well with finance, at least not if applied broadly. You can get some of the way with slicing / partitioning, but you will still have to deal with a lot of traffic between partitions.

Re: JetBrains cancels Fleet

#26
post #12

Last week i cancelled my Jetbrains sub after a decade of daily driving it. I just cant take the performance issues anymore. Across 5 different machines all kinds of actions would just take ages and it got worse every year. Moving to Apple Silicon made it bearable for a few months but somehow Jetbrains manages to get slow even on a M3 Max with 36GB RAM. Ive been fiddling with configs for years, i tried everything sinc…

[flagged]

Everyone who promotes a product they use every day doesn't have to be a paid shill. I like PyCharm, DataGrip, and IntelliJ because they generally work very well for me at my day job and open source side projects.

Firefox is an odd case because I've personally never experienced stability issues with it on Ubuntu. The only problem I've had in the past is some Google products are noticeably slower than on Chromium. Colleagues of mine have had stability issues on Windows though.

Re: JetBrains cancels Fleet

#27

Fleet started as our attempt to explore a new generation of JetBrains IDEs, developed in parallel with those based on the IntelliJ Platform. Over time, we learned that having two general-purpose IDE families created confusion and diluted our focus. Rebuilding the full capabilities of IntelliJ-based IDEs inside Fleet did not create enough value, and positioning Fleet as yet another editor did not justify maintaining t…

Open source it & let community take over?

Re: JetBrains cancels Fleet

#28
I left JetBrains in January after a very long time; with the new UI, there was realistically not a lot separating it from VSCode, and it was clear where all the fun was.

I didn’t really want to switch to VSC but the extensions made it easy to find things that you just couldn’t do in IntelliJ, and… I haven’t looked back. Haven’t really missed the suite at all.

Re: JetBrains cancels Fleet

#29
post #12

Last week i cancelled my Jetbrains sub after a decade of daily driving it. I just cant take the performance issues anymore. Across 5 different machines all kinds of actions would just take ages and it got worse every year. Moving to Apple Silicon made it bearable for a few months but somehow Jetbrains manages to get slow even on a M3 Max with 36GB RAM. Ive been fiddling with configs for years, i tried everything sinc…

> Last week i cancelled my Jetbrains sub after a decade of daily driving it.

I’ve been paying for a personal license for about 20 years and I’ve been thinking of dropping it. I don’t use it much, but I wanted access to something that I could use offline. I’m not sure that’s possible at this point, so the main appeal is kind of gone for me.

I frequently choose “lesser” tools if it means I’m guaranteed they’ll run offline. I’ve always wanted to have a dev container with all the tools needed to develop 100% offline if needed. Licensing makes that almost impossible and Jetbrains doesn’t look like they have any solutions that work great for 100% offline development anymore.

I might check out Zed this week. I’ve never heard of it. If anyone has some great resources for 100% offline development, I’d love to see them. My subscriptions are getting out of hand and this may be the year for me to trim the fat.

Re: JetBrains cancels Fleet

#30

Earlier quoted context omitted.

[flagged]

Everyone who promotes a product they use every day doesn't have to be a paid shill. I like PyCharm, DataGrip, and IntelliJ because they generally work very well for me at my day job and open source side projects. Firefox is an odd case because I've personally never experienced stability issues with it on Ubuntu. The only problem I've had in the past is some Google products are noticeably slower than on Chromium. Coll…

Yeah, I'm not a paid shill. I have been using IntelliJ since version 2 way back in 2003(?). Yes, it's had its performance issues, but people tend to forget the feature set they brought to market, and have continued to do so. But, my career is dead now, as I am an unemployed loser. So, 2026 will probably be the first year that I no longer have an updated IntelliJ.
Post reply on HN