With the recent announcement on KMP tooling im cur...
# fleet
m
With the recent announcement on KMP tooling im curious where fleet will be positioned in the product stack moving forward? Ive been trying it out on occasion and i found the big design refresh over the standard jetbrains IDE to be pretty pleasant so i wouldnt want to see it fizzle out. My initial understanding of the goals of fleet was that it was meant to be a polyglot ide with a focus on KMP development with the latter being the killer feature. Without the KMP focus is it moreso meant to be a bridge between "text editor with code highlighting" (in lightweight mode) and full featured IDE in one software?
p
Hi, Michael! I’m a PM working on the Fleet team. From the very start we envisioned Fleet as a versatile lightweight code editor capable of working in remote environments. That positioning hasn’t changed.
m
I see so it was the lightweight aspect of it that was more the initial goal of fleet and the KMP support was more of a tack on feature. That makes sense to me thank you for clarifying and great work on fleet so far!
🙏 1
s
plus one about the pleasant Fleet design! I would like to see that design in other JB IDEs
🙏 1
d
I think it was a good call from Jetbrain to focus on Idea regarding KMP. Fleet has a lot of potential but in my opinion isn’t ready yet, and pushing a new tech on an IDE that isn’t ready would have been a failure
👍 4
💯 3
c
I would like to see that design in other JB IDEs
I think the New UI in IJ was an effort to modernize the UI, which Fleet shares some elements, though not without a lot of change aversion from IJ users. Not to mention the tech stacks are very different (IJ is Swing and 20+ codebase, Fleet is in-house reactive UI fx and much newer code base). But perhaps with current investments of using Compose Desktop to develop IJ, we will see future UI enhancements faster in the future.