Skip to content
Notifications
Clear all

Is JetBrains Fleet actually stable enough for daily use?

2 Posts
2 Users
0 Reactions
79 Views
(@migrator_maria)
Eminent Member
Joined: 6 months ago
Posts: 23
Topic starter   [#4206]

Hello everyone! 👋 As someone who spends an inordinate amount of time planning and executing migrations—be it data, CRM, or entire ERP systems—I’ve developed a deep appreciation for a stable, performant development environment. It’s the bedrock upon which all those careful rollback plans and user adoption strategies are built! My current IDE of choice has served me well, but the promise of JetBrains Fleet, with its fresh approach and distributed architecture, is incredibly appealing for the kind of large-scale codebase analysis I often do.

However, my migration-brain is always on, and before I even consider a “lift-and-shift” of my daily work, I need to do my due diligence. Stability is my non-negotiable number one requirement. I can handle a missing feature here or there, but crashes, data loss, or plugin conflicts that eat memory and slow startup are an absolute dealbreaker. They sabotage productivity and, in a professional context, can derail project timelines.

So, I’m turning to this wonderful community for some real-world, ground-truth experiences. I’d love to hear from anyone who has taken Fleet from a test drive to their primary driver.

* What has been your experience with plugin compatibility? Have you encountered any conflicts that broke core features like the language server, especially with plugins for database tools, version control, or language-specific extensions?
* How is the memory footprint and overall performance, particularly with larger projects? Does it feel snappy during refactoring or code navigation, or are there noticeable hiccups?
* Have you experienced any data loss or corruption with project settings, run configurations, or local history?
* Most importantly, does it feel *predictable*? As someone who loves a good checklist, I need to know if the environment behaves consistently day-to-day.

I’m especially keen to hear your setup details—your OS, project type, and any critical plugins you’re using—to better understand the context of your stability assessment. My own migration plans can’t proceed without a solid rollback strategy, and that starts with knowing the true state of the new platform.

Thank you in advance for sharing your insights and lessons learned!

migrate with care


migrate with care


   
Quote
 amyt
(@amyt)
Reputable Member
Joined: 4 months ago
Posts: 221
 

That's such a key point about stability being non-negotiable. I've been using Fleet for some lighter data analysis scripts and it feels surprisingly solid for a "preview." But I haven't braved a full migration project on it yet.

For your large-scale codebase analysis, the distributed backend is fantastic and really fast. I've noticed a few hiccups with the Git integration when you have really complex branching, though. Nothing that caused data loss, just occasional weird UI states that required a restart. That might be a red flag for your timeline-sensitive work.

Maybe run it side-by-side for your analysis tasks first? The performance there is a genuine win, but I'd keep my main IDE open for the actual build/deploy steps until the next few updates land.



   
ReplyQuote