31–40 of 332 posts
What kept me using their main products instead of fleet was the plugins that are available, that makes working just more enjoyable.
I'm sure this is great for enterprises but for me, a single developer on a local machine, what benefits does Fleet bring?
I've been browsing their site for a few minutes now and I'm still lost on what Fleet actually is. It says it's a new IDE, built from scratch, sure, but isn't IntelliJ already the gold standard for many languages? What problems does creating an entirely new IDE solve?
I think they’re trying to move to a browser / cloud model, presumably so that they can charge more for less.
I've been browsing their site for a few minutes now and I'm still lost on what Fleet actually is. It says it's a new IDE, built from scratch, sure, but isn't IntelliJ already the gold standard for many languages? What problems does creating an entirely new IDE solve?
>We built Fleet to be a fast and lightweight text editor for when you need to quickly browse and edit your code. It starts up in an instant so you can begin working immediately, and it can easily transform into an IDE, with the IntelliJ code-processing engine running separately from the editor itself.
It's splitting the difference between text editor and IDE. It's their answer to people complaining "IntelliJ takes too long to start up" while keeping the IDE features that you lose just using a text editor.
JetBrains trying to fight back Visual Studio Code taking over their market share.
The main difference between VS Code and the various JetBrains IDEs is that for VS Code, you have to find and install the relevant plugins for your use case yourself, whereas the various JetBrains IDEs tend to work out of the box (while still supporting plugins). That's usually the difference between most free/open source solutions and commercial software: you can do mostly the same with the open source alternative, y…
Earlier quoted context omitted.
The main difference between VS Code and the various JetBrains IDEs is that for VS Code, you have to find and install the relevant plugins for your use case yourself, whereas the various JetBrains IDEs tend to work out of the box (while still supporting plugins). That's usually the difference between most free/open source solutions and commercial software: you can do mostly the same with the open source alternative, y…
That is why one has the IT department configuring development images. I remeber there was a blog post from JetBrains where they complain about VSCode taking over InteliJ market, by indirectly asserting they don't understand why VSCode adoption was rising. Surprise surprise, a couple of months later Fleet was announced.
Earlier quoted context omitted.
The main difference between VS Code and the various JetBrains IDEs is that for VS Code, you have to find and install the relevant plugins for your use case yourself, whereas the various JetBrains IDEs tend to work out of the box (while still supporting plugins). That's usually the difference between most free/open source solutions and commercial software: you can do mostly the same with the open source alternative, y…
That is why one has the IT department configuring development images. I remeber there was a blog post from JetBrains where they complain about VSCode taking over InteliJ market, by indirectly asserting they don't understand why VSCode adoption was rising. Surprise surprise, a couple of months later Fleet was announced.
There are two reasons:
- People don't know better (yes, they really don't)
- Language server allowed languages with abysmal tools to finally have some semblance of an IDE
None of us know the future, but in my opinion Fleet is a mistake:
- It tries to fight VSCode at VSCode's turf (an editor with primitive IDE functionality)
- while trying to be a testbed for new UI for JetBrains IDEs
- while trying to both serve the Language Server crowd and keep JetBrain's vastly superior language tools
- while diluting JetBrains' offer of development tools
> Fleet is our new distributed polyglot editor and IDE. Ok, polygot makes sense, it supports more than just one language. But what does distributed mean in this context? You run the editor across many machines? What does that mean? Coming from a backend perspective, it quite doesn't make much sense. Thinking about it from a client-side perspective, I'm guessing they mean the architecture is decoupled, meaning basical…
Distributed means you can run the editor UI and the actual backend on separate machines. One long-term goal of such deployments is developers just having a thin chromebook with the UI and the actual code being on a corporate server, like terminals and mainframes in ye olde days. I believe this is a reaction to VS Code, which has supported this functionality for a while already.
Earlier quoted context omitted.
The main difference between VS Code and the various JetBrains IDEs is that for VS Code, you have to find and install the relevant plugins for your use case yourself, whereas the various JetBrains IDEs tend to work out of the box (while still supporting plugins). That's usually the difference between most free/open source solutions and commercial software: you can do mostly the same with the open source alternative, y…
Because you do it only once and can use it in any other company you work. It's a highly portable tool for free. What are the chances that your next employer will pay for a JB license?