![]() Although, you can achieve the same in VSCode with the power of extensions. It also has a nice history tab where you can review all your branches, past commits, and so on. You can review and commit your changed files in the Git tab as you’d expect. I very much liked the Git integration Fleet comes with by default. Okay, finally something genuinely nice to say. Fleet even put Google Chrome to shame with its memory usage! Git Integration This just did not seem right, and I hope it is optimized in the future. With the same project and file open, Fleet was proud enough to take up more than 3 times the memory than VSCode. I honestly do not know what to say about this one. ![]() I do realize it is a preview version, but it has a long way to go before it is usable. I tried opening a Svelte project and it was all plain white. Also, it is just not there with language and tools support. VSCode barely takes a minute before the IntelliSense and all the nice code completions are ready to use. First of all, my medium-sized React project took a few minutes to get indexed by Smart Mode before I could use its features. But I think it still has a long way to go in terms of support. I really wanted to like the Smart Mode, I do like the idea of being able to turn IntelliSense on and off. Although I think having a good UI is a no-brainer for JetBrains, they have been making IDEs for decades. I also really liked the file explorer window, and I think I prefer how it looks and feels over VSCode. It is clean with the ability to dock any window you’d like in its left, right, or bottom panel. I really enjoyed how snappy the editor felt, big points for that. ![]() I tried to open a decently sized React project and opened up almost instantly. Thankfully, that was not the case with Fleet. I love the sheer amount of features and tooling they provide but their IDEs always feel very heavy and slow at first. I’ve had mixed experiences with JetBrains IDEs. This seems to be a growing trend from a lot of big companies to get people into their ecosystem (I’m looking at you, Adobe). If you don’t use other JetBrains IDEs then there is no point in having a manager for all your JetBrains tools. If you want to download Fleet you need to first download their Toolbox App and download Fleet from there. Okay, I had to mention this because I know it is a huge turn-off for a lot of people. These are not separated by the pros and cons but rather are my thoughts about different parts of the editor. Here I’ll be listing down a few of the important pointers that caught my eye while I was using Fleet. When working with your code, Fleet allows you to connect to a remote machine and use a Fleet instance already there. Fleet is also trying to go in that direction with its remote development features. In VSCode, remote development has also received a lot of support. Fleet can also transform into an IDE with the help of its “IntelliJ code-processing engine” and provide context-aware code completion, quick fixes, etc. According to its website, Fleet claims to be “a fast and lightweight text editor for when you need to quickly browse and edit your code” which seems to be the same user base VSCode is targeting. The popular VSCode text editor appears to have set off a new trend, which led to the development of this new IDE. So how does it fair against VSCode? In this article, I’ll walk you through my experience with using Fleet for the past few days, and a few things you should know if you’re interested in trying it out. Since then there has been a lot of noise around Fleet within the developer community, and it also has been questioned about being the VSCode killer. JetBrains, the company behind well-known IDEs like IntelliJ Idea and WebStorm, recently declared that Fleet was now ready for public preview.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |