Re:JetBrains Fleet: The Next-Generation IDE by JetBrains
by johannes1234321 on Monday November 29, 2021 @09:46AM
(#29380438)
Just to add reasons:
Especially in corporate context this will be the future for compliance reasons. No more developers who accidentally have code on their machine and lose it. Less access tokens on the client machines etc.
Will be an interesting trend of going back to the mainframe ... and will be interesting to see how that will collide with developers who want to have control and chose their tools and setup.
Re:JetBrains Fleet: The Next-Generation IDE by JetBrains
by closeparen on Monday November 29, 2021 @10:01AM
(#29380611)
The very first step of our engineering onboarding process is to turn on FileVault...
Re:JetBrains Fleet: The Next-Generation IDE by JetBrains
by sirsinsalot on Monday November 29, 2021 @12:00PM
(#29382142)
As another data point, I buy a license to all Jetbrains IDEs as a private individual. The non-remoteness and the fact my license is for a perpetual installed version matters to my livelihood. It's also a known cost where many things get more PAYG
The only thing slowing it down was developer rejection of the austerity of vim and emacs. That’s changing now with VSCode’s in-browser and SSH Remote support. That’s the golden path now at my work. Although we still pay for JetBrains licenses, the JetBrains workflow is quietly and unofficially deprecated.
They have to do this to stay relevant. And I’m glad they’re doing it, because I want my JetBrains-level capabilities back. VSCode doesn’t come particularly close.