3 ms·

I really don't see the problem with either of those. I spend 8+ hours a day in VSCode and it works flawlessly. I just spent more than three hours with a friend

by fbnlsr 9y ago

I really don't see the problem with either of those. I spend 8+ hours a day in VSCode and it works flawlessly. I just spent more than three hours with a friend on Discord playing The Division and it was smooth as it can be. It's kind of become the norm to hate on Electron apps, but to be fair, I don't see the point.

mdip 9y ago
While the bloat of having to basically install a full version of Chrome just to get a UI makes a little part of me die inside, I'll second the 8+ hours a day in VSCode. I'm working on a python project right now and enjoying PyCharm quite a bit, but in a window right next to me is VS Code with my running log. I'm using it at home with a plug-in to write code in CUDA and C++, I use it at work for TypeScript and dotnet core C#, editing configuration files. Heck, on one of my Windows boxes, I have a PowerShell command "Edit-File" that opens up the target in VS Code, is set to the default commit comment editor for Git and aliases "nvim" because I can't get NeoVim to work on that box to save my life. Sure, it doesn't launch anywhere near as quickly as vi/vim/nvim, but since I live out of the thing, it's always already pulled up and the time it takes to open a file when the editor is already up is plenty fast. As far as being resource heavy -- I like to work on the couch at work and it's nowhere near a plug. I started doing light editing of C# and .NET apps in VS Code to avoid having Visual Studio halve my battery life. I get a solid 4 hours of editing/testing which isn't all that much less than I get just leaving Windows running with nothing open. It wasn't always like that, sure -- I recall either Atom or VS Code having a bug where the cursor blinking caused the CPU to stay steady at 15% (though, ConEmu -- a must-have console app for Windows[0] hangs at around 5-10% CPU with nothing executing, too), but I haven't had any battery/memory/CPU issues running Code for the last year or so. [0] If you use cmder, that's Conemu

by fbnlsr 9y ago

mdip 9y ago

While the bloat of having to basically install a full version of Chrome just to get a UI makes a little part of me die inside, I'll second the 8+ hours a day in VSCode. I'm working on a python project right now and enjoying PyCharm quite a bit, but in a window right next to me is VS Code with my running log. I'm using it at home with a plug-in to write code in CUDA and C++, I use it at work for TypeScript and dotnet core C#, editing configuration files. Heck, on one of my Windows boxes, I have a PowerShell command "Edit-File" that opens up the target in VS Code, is set to the default commit comment editor for Git and aliases "nvim" because I can't get NeoVim to work on that box to save my life. Sure, it doesn't launch anywhere near as quickly as vi/vim/nvim, but since I live out of the thing, it's always already pulled up and the time it takes to open a file when the editor is already up is plenty fast. As far as being resource heavy -- I like to work on the couch at work and it's nowhere near a plug. I started doing light editing of C# and .NET apps in VS Code to avoid having Visual Studio halve my battery life. I get a solid 4 hours of editing/testing which isn't all that much less than I get just leaving Windows running with nothing open. It wasn't always like that, sure -- I recall either Atom or VS Code having a bug where the cursor blinking caused the CPU to stay steady at 15% (though, ConEmu -- a must-have console app for Windows[0] hangs at around 5-10% CPU with nothing executing, too), but I haven't had any battery/memory/CPU issues running Code for the last year or so. [0] If you use cmder, that's Conemu