4 ms·

Just personally, I use several of those "clunky" apps daily and they're more seamless than native counterparts. Particularly VS Code. Its biggest struggle is in

by duped 5y ago

Just personally, I use several of those "clunky" apps daily and they're more seamless than native counterparts. Particularly VS Code. Its biggest struggle is input latency, but if I really cared about that I wouldn't have left editing in the terminal.

clumsysmurf 5y ago
I agree, some of the "clunk" apps feel real nice. Problem is, when you have 4 electron apps running, and your system starts grinding.
datavirtue 5y ago
Yeah, I use VS Code as my terminal now. I love having the directory tree visible if I need or want to single click a file and play with it instantly with zero overhead. I use thunder client now instead of that dreadful postman obomination after learning about it here last week. VS Code is becoming my general purpose environment. I was working in PowerShell ISE today and was thinking "this has to go" the whole time. So if I have any PowerShell work in the future I'm going to try the VS Code tooling for that. I knew at least one person at Capital One who was using it for their Spring Boot project instead of Intellij.
- bdcravens 5y ago
  I have dedicated tools for most tasks like the terminal, git client, REST client, etc, but most of the time I use VS Code (built-ins or extensions); even when I'm making compromises, I prefer the workflow of staying on one screen.
Semaphor 5y ago
While I rarely use it, VS Code is great. But MS Teams? I feel as if I’m on a mobile device that’s running out of memory when I’m using it. (Windows PC)
- lostlogin 5y ago
  It’s actually disgusting, and probably broken in several regards. Why is functionally so different between the native app, web and teams. How is this an industry standard? I edited a table, moved a picture and changed a footer. How can that be complex?
  - aidos 5y ago
    We had to use Teams for the kids school over lockdown. What a dumpster fire. On a daily basis you could never tell which method of extracting a document would or wouldn’t work. Sometimes they wouldn’t open at all. Or would only open on web, but not desktop (or the other way around).
unfocussed_mike 5y ago
I really have trouble with the idea that VS Code is "clunky". Not least because one of the apps I used to use -- Panic's Coda -- had really severe keyboard lag issues in some situations, on hardware that should have been fine with it. In my experience VS Code is plenty quick enough, not least when I am editing something inside a VM or on a remote server using the Remote SSH mode. It might show a bit of keyboard latency but the Remote SSH mode more than makes up for this, for me; the sheer flexibility it offers me as a developer means I am going to ignore a bit of general latency. And we've put up with worse in IDEs and programmers' editors, for sure. One thing I would observe about speed complaints in VS Code is that they come from people who navigate through text mostly through keys; people with a vi or emacs back-story. There is no doubt at all that it repaints more slowly than some editors when scrolling down through code line-by-line or page-by-page with the arrow keys etc., because of all the code actions that fire off when the cursor moves. But it is not noticeably laggy when scrolling with a trackpad, because the cursor does not move. This difference probably explains people's very polarised and simultaneously valid responses to VS Code.

by duped 5y ago

clumsysmurf 5y ago

I agree, some of the "clunk" apps feel real nice. Problem is, when you have 4 electron apps running, and your system starts grinding.

datavirtue 5y ago

Yeah, I use VS Code as my terminal now. I love having the directory tree visible if I need or want to single click a file and play with it instantly with zero overhead. I use thunder client now instead of that dreadful postman obomination after learning about it here last week. VS Code is becoming my general purpose environment. I was working in PowerShell ISE today and was thinking "this has to go" the whole time. So if I have any PowerShell work in the future I'm going to try the VS Code tooling for that. I knew at least one person at Capital One who was using it for their Spring Boot project instead of Intellij.

bdcravens 5y ago
I have dedicated tools for most tasks like the terminal, git client, REST client, etc, but most of the time I use VS Code (built-ins or extensions); even when I'm making compromises, I prefer the workflow of staying on one screen.

Semaphor 5y ago

While I rarely use it, VS Code is great. But MS Teams? I feel as if I’m on a mobile device that’s running out of memory when I’m using it. (Windows PC)

lostlogin 5y ago
It’s actually disgusting, and probably broken in several regards. Why is functionally so different between the native app, web and teams. How is this an industry standard? I edited a table, moved a picture and changed a footer. How can that be complex?
- aidos 5y ago
  We had to use Teams for the kids school over lockdown. What a dumpster fire. On a daily basis you could never tell which method of extracting a document would or wouldn’t work. Sometimes they wouldn’t open at all. Or would only open on web, but not desktop (or the other way around).

unfocussed_mike 5y ago

I really have trouble with the idea that VS Code is "clunky". Not least because one of the apps I used to use -- Panic's Coda -- had really severe keyboard lag issues in some situations, on hardware that should have been fine with it. In my experience VS Code is plenty quick enough, not least when I am editing something inside a VM or on a remote server using the Remote SSH mode. It might show a bit of keyboard latency but the Remote SSH mode more than makes up for this, for me; the sheer flexibility it offers me as a developer means I am going to ignore a bit of general latency. And we've put up with worse in IDEs and programmers' editors, for sure. One thing I would observe about speed complaints in VS Code is that they come from people who navigate through text mostly through keys; people with a vi or emacs back-story. There is no doubt at all that it repaints more slowly than some editors when scrolling down through code line-by-line or page-by-page with the arrow keys etc., because of all the code actions that fire off when the cursor moves. But it is not noticeably laggy when scrolling with a trackpad, because the cursor does not move. This difference probably explains people's very polarised and simultaneously valid responses to VS Code.