111–120 of 332 posts
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 :)
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 :)
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 :)
This looks really promising. But by far the biggest moat that Jetbrains is going to have to cross to get into VSCode territory is the plugin ecosystem. Personally I work on React projects so my first thought was: "is there a Prettier[1] plugin?". Looking through the landing page it looks like Plugins are in the works but until that is implemented, it's going to be hard adopting it. ALSO I just noticed this but can so…
I have read all the comments on this thread. I'm fascinated by people's thoughts of VSC Vs JetBrains. It seems the consensus is that JB is better, except for web platform? Maybe this is because TypeScript is an excellent language server
This looks really promising. But by far the biggest moat that Jetbrains is going to have to cross to get into VSCode territory is the plugin ecosystem. Personally I work on React projects so my first thought was: "is there a Prettier[1] plugin?". Looking through the landing page it looks like Plugins are in the works but until that is implemented, it's going to be hard adopting it. ALSO I just noticed this but can so…
If you have Fleet license (paid, for example) there are no criteria checks at all, just the license verification with your JetBrains Account. And we plan to support offline usage similar to how it’s done for IntelliJ IDEA-based IDEs now (offline license keys, floating license server.)
Right now Fleet is in the EAP, and there are no licensing checks at all, they are not yet implemented, and we are not yet done with the verification workflow design.
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 :)
Earlier quoted context omitted.
A lot, in many Fortune 500 where software isn't the main product, you get a machine (VM based or real one) customized for your workflows, with the set of software that is white listed for software development in the company. Anything beyond the standard development image requires opening a request to IT and procurement, with the respective OK from management.
And when your company starts doing that to developers it is time to dust off your resume and start looking for something better. I get it that these companies have real issues and their managers are multiple times smarter than me but I refuse to be put into a position where I cannot use the tools that I need to be productive.
"We need to switch to tool Y".
There's usually a host of reasons I may not want to move to tool Y, but in most cases, it's because I don't want to have to learn yet another tool just to do what I was doing. Why? Cognitive overload... but also for some period of time I'm going to be much less productive. I don't want to be judged on that. you are saying I have to use Y... I'm going to be slower. Every estimate will be 20% more than what it was for the next Z months. I've got 10 years of muscle memory to undo. Is it worth it?
In most cases, really not. BUT... if someone mandated that, AND also acknowledged up front that the delivery expectations will be reduced for some longer period of time... perhaps it's OK.
On the JB topic, IntelliJ was one 'heavy' tool I resisted for a long time. "I'm faster in these other tools - notepad++, vim, netbeans, whatever". I was faster, for many tasks. Adopting something new was slow. I'm generally glad I did it, but I did it mostly on my own projects, and freelancing. Had I been under pressure to deliver at a high pace while having to undo years of habits/tools/processes that got me where I was at that time, it would have been far more difficult to deal with.
This looks really promising. But by far the biggest moat that Jetbrains is going to have to cross to get into VSCode territory is the plugin ecosystem. Personally I work on React projects so my first thought was: "is there a Prettier[1] plugin?". Looking through the landing page it looks like Plugins are in the works but until that is implemented, it's going to be hard adopting it. ALSO I just noticed this but can so…
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…