21–30 of 332 posts
Earlier quoted context omitted.
Yeah I'm getting strange adobe-like vibes from creative cloud announcements.
Exactly, when you want to download JetBrian fleet, you'll first have to download their "JetBrain Toolbox", which looks and functions VERY similar to the adobe CC menubar app.
Earlier quoted context omitted.
> But what does distributed mean in this context? You run the editor across many machines? What does that mean? Yes: > distributed architecture. For more details check out the Fleet product page [link]. > [Fleet product page:] Distributed for flexibility > Fleet’s architecture is designed to support a range of configurations and workflows. You can simply run Fleet just on your machine, or move some of the processes e…
Ok, so I could kind of understand the use case of running the UI on one machine and the backend for the UI on another machine. Lots of complexity for small amount of gain, but somewhat makes sense. But then they say "distributed" so that would mean many backend machines, not just one. What on earth is the backend doing where one instance is not enough for one client? How could one client UI possibly need more than on…
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.
So those are potential customers that JetBrains was/is losing. My brain is almost 20-years-wired for JetBrains products. I would have been much happier to be able to use a remote JetBrains IDE vs a remote VSCode.
There are also people for whom the existing JetBrains IDEs will always feel big slow and bloated. They have a lot of features packed in and come with a lot of lifestyle assumptions. I can see the value in JetBrains rolling out something that feels lighter-weight.
Given they're presumably spending a lot on this development, it would be useful to give a bit more detail than this. What is different?
I just downloaded the Fleet beta from the App toolbox. First impressions is that it is very clean. This is essentially Vscode but with Jetbrains language and refactoring engine. Quick thoughts: - It needs a bit more autocomplete e.g automatically close tags for React components - GUI run configuration - they have made it so it uses a JSON file like Vscode to configure, GUI is quicker and easier (can still click run o…
And better auto-complete for that. I tried to add my golang project, but had no clue what it wants from me for goExecPath or buildTargets. Why not show the help inside the editor? I had to google and look around (goExecPath is the actual link to the bin, not GOPATH or something) and buildTargets means files (main.go). The naming feels weird.
> 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…
I assume this is their answer to that.
JetBrains trying to fight back Visual Studio Code taking over their market share.
Earlier quoted context omitted.
> But what does distributed mean in this context? You run the editor across many machines? What does that mean? Yes: > distributed architecture. For more details check out the Fleet product page [link]. > [Fleet product page:] Distributed for flexibility > Fleet’s architecture is designed to support a range of configurations and workflows. You can simply run Fleet just on your machine, or move some of the processes e…
Ok, so I could kind of understand the use case of running the UI on one machine and the backend for the UI on another machine. Lots of complexity for small amount of gain, but somewhat makes sense. But then they say "distributed" so that would mean many backend machines, not just one. What on earth is the backend doing where one instance is not enough for one client? How could one client UI possibly need more than on…
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…
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.