JetBrains Fleet vs. VS Code | Is Fleet VS Code Killer?

JetBrains released their brand new Code Editor (or IDE?) Fleet. I had several hours to use it on my front-end projects. As a junior front-end developer, I am here to share my opinions about the new JetBrains Fleet. Is it really VS Code killer?

Selim Enes
CodeX
3 min readOct 16, 2022

--

JetBrains Fleet original page.

Everyone knows that JetBrains is popular with their IDEs. They have different IDEs for almost every single programming language. Yes, they are earning good money with them. But people have already started to complain about it. If someone works on different projects with different programming languages, it disturbs to change the IDE. Probably JetBrains heard about these complaints either. They just released their “polyglot” code editor. Actually, it is hard to call Fleet a code editor or an IDE. Fleet is something between them.

UI/UX | Fleet vs. VS Code

JetBrains Fleet original page.

I am a person who changes themes in my VS Code, changes desktop background often, and so on… It’s kinda sickness for me. If I got used to seeing the background and I don’t even “see” it, I am going to change it. With these changes, I feel more motivated and fresh. So, I am not the person who can criticize UI/UX between both of them. I can say that I loved Fleet’s themes and UX. It’s really cool, easy to use, and minimalistic. But, it’s not a plus. Because there is already Fleet’s theme in VS Code. I can use it just in a second.

Community and Extension Library

Link to the library

I think it’s not even needed to mention it, but VS Code has a great community. With this power, it has also a great library of extensions. VS Code is just an editor with highly customizable skills. On the other hand, Fleet doesn’t even support extensions currently. So, JetBrains will share their API for extensions first, and we will start waiting for new extensions and more. That means we have at least 2 years to count Fleet as a competitor of VS Code. And 2 years is an optimistic idea.

Speed and Performance

Performance with the same project (Next.js) on both of editors.

As you can see above, I opened the same project for both of the editors. When I open my project on VS Code, I can start editing just after 2–3 seconds. But when I try to open the same project on Fleet, I waited for more than 1:30 minutes to be able to write code with smart mode. The first time I open smart mode, it downloads a few extensions and some things. But even after that, nothing goes better about the performance.

Overall | VS Code vs JetBrains Fleet

I tried to criticize everything I saw about Fleet as a junior front-end developer. I am happy with my cutie VS Code and will not change it. But, JetBrains Fleet has good potential. I believe, after 2–3 years it will be an excellent competitor to VS Code, and it was needed already. If there are any mistakes in what I wrote, please don’t hesitate to write about them in the comments. And share your opinions about the Fleet, please. I will be waiting! Also, if you think the content is useful, you can support me through tips below 😇.

--

--

CodeX
CodeX

Published in CodeX

Everything connected with Tech & Code. Follow to join our 1M+ monthly readers

Selim Enes
Selim Enes

Written by Selim Enes

Sharing my experiences on learning front-end development path and more.