What's the end goal?

Hi,

first of all, huge fan of JB products!

I just wonder what crowd is the target audience for Fleet? 

I am mostly using Rider, a bit of PyCharm, love both. I really enjoy that those can become my “whatever I do, I use the same tool”. Database support is awesome, Rider works great for web-dev also.

Recently I played around with Rust during Advent of Code, my first though was hey, let's fire up Rust Rover! Unfortunately, it was so slow to open a directory with a separate project for each day. Gigabytes of ram just to watch some spinners.

In the end I fired up Neovim and that was a blast - I really enjoyed keyboard only nature of it, the abillity to use vim motions in the terminal for navigation and selection. It was fast, snappy, I could start a watcher to rerun tests on save, debug (that part sucks :)) - it was pretty cool. However, configuration is a pain.

I fired up Fleet and immediately it felt more like Neovim than Rider - generic editor, with custom sources for stuff. It also auto-installed everything I neede - whether it's dotnet backend, TypeScript plugins etc - really cool.

I am fully aware that it's still in progress, so I don't judge things like RAM usage or scroll smoothnes (both aren't that great now on Windows). 

I am also aware that Rider and InteliJ in general have quite a lot of legacy code in them, so some things just are not possbile (like proper Neovim-like consistent keyboard only navigation). 


Is Fleet planned to be more like Neovim (editor + LSP/Smart Mode per language), or is it an attempt to rewrite the Idea Platform from scratch, to eliminate specialized IDEs and have a single product that does it all?

Unless Fleet becomes “the one thing to rule them all”, so that I don't have to switch between Rider and PyCharm cosntantly, and it will get full keyboard only setup, I don't see anybody choosing it over a specialized IDE.

So, what's the end goal? I saw you closed the position for fleet developer, so I guess it will continue to get better


 

1
1 comment

Hi, thanks for sharing your feedback and thoughts! The short answer is that we see Fleet as a modern coding tool. That means a bunch of things, including minimalistic UI, support for a bunch of languages, and remote development. The use cases can vary – for some it can be a companion tool like neovim is for you, for others it can become a primary tool. With the AI very quickly shifting how we develop code, we are trying to keep Fleet as versatile as possible.

0

Please sign in to leave a comment.