Live data from Hacker News

JetBrains invites developers to join the Fleet Public Preview Program

blog.jetbrains.com

141–150 of 332 posts

Re: JetBrains invites developers to join the Fleet Public Preview Program

#141

Earlier quoted context omitted.

JetBrains employee here, and I can clarify the point about “Requires login and periodic connection to JetBrains servers to verify the project”. If you are using Fleet in a Free (hobby) mode, we are verifying that the project comply with one of three criteria: 1. your project is local (no Git or Git Remote). 2. your project is public on GitHub. 3. your project is private but has less than 3 committers. In this case, w…

> your project is public on GitHub. What about Gitlab, or some other repo such as gitlab.gnome.org? This seems like it's ripe for edge cases.

Yeah, right, I was not specific enough on this one. It'll definitely go beyond GitHub, extending to some other git solutions, but we don't have a decision whether it's "any" public repo or public repo hosted on the service from some list (like, GitHub, GitLab, Gitee, etc.) We'll look into it later on.

gitlab.gnome.org - I'd expect it to be all open source, right? Open source program should cover such cases.

Re: JetBrains invites developers to join the Fleet Public Preview Program

#142
post #49

> 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…

>But what does distributed mean in this context? The older Jetbrains IDEA IDE is a monolithic local application. E.g. it does both UI navigation _and_ batch processing work like source code indexing . Fleet is re-architected to be "distributed" aka "client/server" style into a "lightweight" frontend + "heavyweight" backend. E.g., the frontend does UI navigation and basic syntax parsing but the backend (which can be o…

so, modular? :)

crud app with frontend + backend is not distributed, but it definitely is client/server architecture

but that's just nitpick, iirc "distributed" means something different in their context

Re: JetBrains invites developers to join the Fleet Public Preview Program

#143
So I tried it out. I own a CLion license and have been using Jetbrains products since IntelliJ 3.0. It seems ok, but very very VSCode-ish.

I tried it with our Rust codebase and it seemed to be fairly competitive with CLion in terms of analysis. I didn't try any refactorings but I did notice that it doesn't have many of them. It was fairly snappy, felt more responsive than CLion. I was disappointed that even after I switched it to "IntelliJ" keybindings many keybindings still were more like VSCode than IntelliJ. I.e. Ctrl-N was still "open new tab" and not "jump to symbol" (have to do ctrl-shift-alt-N for that.)

Overall, I guess I'm curious where they go with it. I won't be trading in my CLion license, though. I am probably not the target audience; I suspect they're looking to capture customers who work in large corporations where VSCode is getting penetration as a hosted/fleet solution. With the default keybindings I suspect those coming from VSCode will find Fleet very comfortable.

For myself, I continue to give Jetbrains money for their IDEs, because as a company they do great work and give good value. I'm happy to modestly help pay the salaries of their employees. I wish them luck.

Re: JetBrains invites developers to join the Fleet Public Preview Program

#144

Earlier quoted context omitted.

JetBrains employee here, and I can clarify the point about “Requires login and periodic connection to JetBrains servers to verify the project”. If you are using Fleet in a Free (hobby) mode, we are verifying that the project comply with one of three criteria: 1. your project is local (no Git or Git Remote). 2. your project is public on GitHub. 3. your project is private but has less than 3 committers. In this case, w…

Will the pricing be same for all users or do users with existing licences (e.g. Ultimate) get a discount on Fleet licence?

We are not ready to share more details on pricing yet, but we are working on it. Will share as soon as we have it!

Re: JetBrains invites developers to join the Fleet Public Preview Program

#145

To use Fleet you have to download the JetBrains Toolbox. Really? Look, I'm a JB subscriber and have the toolbox, but Fleet should not require another app to launch or update itself.

[JetBrains employee] In the future Fleet will be able to update itself. Right now, we use Toolbox App as it can do Fleet updates easier.

Re: JetBrains invites developers to join the Fleet Public Preview Program

#147
post #28
post #26

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 also find JetBrains completions to be smarter than VS Code's plugins (especially for python).

Re: JetBrains invites developers to join the Fleet Public Preview Program

#148

Earlier quoted context omitted.

Because if your tooling is closed source (and if it's paid it almost certainly is) then your ability to maintain a project is dependent on some corporation's willingness to continue to support the tooling etc.

If the possibility of your tooling being discontinued is a real concern for you, paying for a Jetbrains license is your best bet. Their entire business is developer tooling: IntelliJ isn't going away until Jetbrains goes under, and they're not going under until people stop paying them. Microsoft, on the other hand, could decide to drop VSCode at any point as soon as the bean counters start questioning how it's benefi…

It's worth noting that JetBrains has a long history of successfully competing against free IDEs, which were normally always more popular than IntelliJ. First there was NetBeans (bought and open sourced by Sun very early), then there was Eclipse (developed and open sourced by IBM), now there is VSCode. Heck there are probably others I don't know about. So, this is nothing new for them.

Usually what happens is that after enough years have passed, the company funding the free IDE starts to wonder why exactly they're spending so much money to give away the results. The original passion-project founders have moved on, leaving behind maintenance devs who aren't motivated to defend it. Eventually it gets stripped to a handful of devs and donated to Apache. In the meantime IntelliJ continues to develop new features.

The question VSCode users might wonder about is what's Microsoft's strategy here? They have plenty of money, but then again so did Sun/Oracle and IBM. Is there a long term commercial plan to let the VSCode team justify themselves.

Re: JetBrains invites developers to join the Fleet Public Preview Program

#149

Earlier quoted context omitted.

I'd say they still don't understand why VSCode adoption is rising. 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 test…

People don't know better (yes, they really don't) Or maybe VS Code is just really good? I was skeptical for a long time as well. I am a longtime Emacs and JetBrains IDE user (starting with IntelliJ in 2013). A while back I gave VS Code a try again. I primarily used CLion for Rust and PyCharm. And I found that the Rust/Python is at least as good as in CLion/PyCharm (with the exception of Cython). And thanks to VS Code…

> And I found that the Rust/Python is at least as good as in CLion/PyCharm

I think Rust support is comparable (probably because they both use rust-analyzer). I've found the opposite for Python. PyCharm is WAY smarter than VS Code.

Re: JetBrains invites developers to join the Fleet Public Preview Program

#150

I installed this 30 min ago. 1. My M1 temp went from 28c to 60c 2. CPU utilization to 103%? 3. It's using 3.29Gb of RAM And it hasn't changed. With a single python project with 3k lines of code. VSCode sits at 280Mb and CPU temp around 28c. Edit: Vim + SpaceVim sitting at 17Mb :)

While annoying, all intellij EAPs (early access previews) are very cpu intensive, as they run in debug mode by default to create diagnostics and crash reports. Kinda similar like if you would keep the debugger open in your browser. Not sure if you can disable it, but thats the main reason why I stopped using EAPs for work.

But the ram is typical intellij, they take what they can get from the OS :)

Post reply on HN