|
> User feedback was consistent: If you already work with IntelliJ IDEA, Rider, WebStorm, PyCharm, or any other JetBrains IDE, switching to Fleet required a strong reason – and Fleet did not offer enough value to justify the transition from IDEs you already know and love. My problem was that Fleet just wasn't very good when compared with VSC. For my more serious development I use JetBrains IDEs (one of the few pieces of software that I actually pay for, alongside MobaXTerm and some others) but Fleet didn't neither use that much less resources, nor was that much more responsive, nor was a step above VSC in any way. To be clear, I didn't hate it, it wasn't horrible and with a bit more work could have been quite good... just not convincingly so up until now. If they wanted to throw some more years of engineering at it, maybe, I mean look at what Zed is doing and it seems to be okay, but I don't think it makes that much business sense for them - they already have Junie available in their editors for AI stuff and that other subscription (though I just use Claude Code, Codex, Gemini CLI and sometimes VSC with KiloCode/RooCode/Cline and either those models through the API or Cerebras Code since it works pretty well in there). I just find that most AI solutions out there are also a little bit half-baked, like Gemini CLI fails when I paste multiple lines into it, whereas KiloCode/RooCode/Cline are unable to give a model enough helpful instructions for it to not start looping when it fails applying a complex diff sometimes, and pretty much nothing outside of the regular GitHub Copilot plugins does autocomplete decently (especially if you want a local model with Ollama or something, no good options, Continue.dev is trash). With how prevalent AI is and how useful various linters and build output is, sometimes I wonder whether I need to pay hundreds of euros for the Ultimate package of tools when I don't write/refactor as much code manually and doing what I need inside of VSC also feels more and more sufficient. Maybe a bit except Java codebases, Spring Boot sometimes does weird shit and you're better served by an IDE that's aware of all of the templating, annotations and other stuff. Oh well, despite being RAM hogs, I still enjoy the experience of using JetBrains IDEs and if nothing else will keep them around for that reason for a while. A bit like how I also enjoy a GUI of some sort for Git, like previously I paid for GitKraken but reevaluating my usage found that SourceTree is also decent enough for the price (free vs GitKraken paid version), I can just drop down to the CLI for niche use cases. |