Live data from Hacker News

Fleet, a Lightweight IDE from JetBrains

blog.jetbrains.com

141–150 of 427 posts

Re: Fleet, a Lightweight IDE from JetBrains

#141

Earlier quoted context omitted.

IDE language isn't tied to the language used in your codebase

Parent has a point, there are so many things that don't even make sense in other languages, for example in my native language we don't have a word that corresponds to "Refactor", any possible translation would be weird and hard to understand, that's why I've never used an IDE in a language other than English. It's got nothing to do with "the language used in your codebase", whatever you mean by that (programming lang…

I'm sure the Academie Français has made up an authorized word like rererefateurellement.

Re: Fleet, a Lightweight IDE from JetBrains

#144

Earlier quoted context omitted.

VSCode has debugging built in and can connect to various runtimes. Not that I ever use that - I prefer sticking with the language native tools, and I rarely require anything beyond inspecting runtime values and simple benchmarking. Maybe this comes from the perspective of Java, where you need an IDE to do proper debugging, building/starting an application requires a gazillion command line arguments, and you have laye…

Refactoring, "show me where this class, function, variable is used", "show me a class hierarchy", "analyze my code and tell me where I'm not using best practices and suggest the best fixes and apply my selected one", are places where a full-fledged IDE shines. An editor won't do those, or most of those. A 15-minute task turns into a 20-second blip.

VSCode does all of the former, at least for the two main languages I work with, TypeScript and Go. Prettier, ESLint and golangci-lint handle the style checks.

JetBrains says the problem is “users are unaware of what an IDE can do” but maybe it is the other way around?

Re: Fleet, a Lightweight IDE from JetBrains

#145
I just hope the remote development features will actually work adequately in this.

They tried to get that stuff working with existing IDEs multiple times [0][1][2][3], but they are all broken in their unique ways.

Whenever I see them announce something new in the remote development space I always jump in right away and try it out, discover it is broken too, and then go back to using VS Code remote dev features.

For local dev I still use JB stuff, but it is simply too broken and awkward for remote.

[0] https://www.jetbrains.com/help/pycharm/configuring-remote-in...

[1] https://lp.jetbrains.com/projector/

[2] https://blog.jetbrains.com/blog/2021/11/29/introducing-remot...

[3] https://www.jetbrains.com/code-with-me/

Re: Fleet, a Lightweight IDE from JetBrains

#146
post #76
post #52

Earlier quoted context omitted.

Google translate from a dev vacancy: You will be surprised, but we decided to create a new IDE from scratch and put together a bold team with a proven success track in creating tools inside JB. And right now we have a prototype and a bunch of bicycles. Our program consists of several parts that communicate with each other over the network. The first part is an editor that is written in a new cross-platform UI framewo…

Now that's interesting, let's hope it's not immediate mode based and is closer to SolidJS (without Virtual DOM) than modern React, which clearly has no long-term future.

they didn’t say it’s a JS framework though

Re: Fleet, a Lightweight IDE from JetBrains

#147
post #11

Earlier quoted context omitted.

Same. > For years folks have been asking us, “JetBrains, when will you create a lightweight editor?” I sure never did. If anything, I want their IDEs to be more involved and sophisticated. Otherwise I'm likely going to cancel our company subscriptions next year, VSCode is starting to overtake e.g. PyCharm in terms of developer comfort. So I really hope this is just a tech demonstrator to renew the architecture of the…

I've worked in 4 different software shops over the last 15 years. My general observation is the developers who rely on heavily automated/magic tooling are significantly outclassed by those who use the terminal + a basic text editor. Terminal + Vim or Emacs/VSCode (depending on configuration) is not only all you need, it also produces developers who understand the systems they work with. I know a lot of people will di…

Jetbrains IDEs will step into framework/library code/stack-frames/variables that you didn't write yourself and let you trace the full context of your code ... that's insight and knowledge no straight-editor will give you.

Re: Fleet, a Lightweight IDE from JetBrains

#148
post #11

Earlier quoted context omitted.

Same. > For years folks have been asking us, “JetBrains, when will you create a lightweight editor?” I sure never did. If anything, I want their IDEs to be more involved and sophisticated. Otherwise I'm likely going to cancel our company subscriptions next year, VSCode is starting to overtake e.g. PyCharm in terms of developer comfort. So I really hope this is just a tech demonstrator to renew the architecture of the…

I've worked in 4 different software shops over the last 15 years. My general observation is the developers who rely on heavily automated/magic tooling are significantly outclassed by those who use the terminal + a basic text editor. Terminal + Vim or Emacs/VSCode (depending on configuration) is not only all you need, it also produces developers who understand the systems they work with. I know a lot of people will di…

Bit of a sweeping, overgeneralisation don't you think? Don't see how the quality of the developer correlates to their choice of environment.

Re: Fleet, a Lightweight IDE from JetBrains

#150
post #145

I just hope the remote development features will actually work adequately in this. They tried to get that stuff working with existing IDEs multiple times [0][1][2][3], but they are all broken in their unique ways. Whenever I see them announce something new in the remote development space I always jump in right away and try it out, discover it is broken too, and then go back to using VS Code remote dev features. For l…

This is also the main reason I switched from PyCharm to VS Code at the start of the pandemic, which I think was really a really fortunate circumstance for the latter IDE. Even though PyCharm is a superior IDE, its remote development features were really broken, while VS Code nailed it.
Post reply on HN