I posted a video showing how bad Visual Studio's stepping speed had become. There were dismissive commenters who actually claimed it was because it has syntax highlighting. People are really that confused about computers. Meanwhile, this is 30fps:https://youtu.be/Oh2oF-eZTD8?t=484 …
-
-
While it's both expected and reasonable for a programmer, especially a novice, to not know much about performance, it's another thing for people to be _sure_ they know how performance works enough to be dismissive, and yet be so incredibly uninformed as to be almost nonsensical.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I mean, if it WAS the syntax highlighting causing the slowness, that would be an even worse indictment of VS performance!
-
Not for programmers dismissing my criticism on Reddit, apparently! A few hundred hash lookups that return an RGB value is apparently something they think should take 500ms, because they're _just that good_.
End of conversation
New conversation -
-
-
When I was in college, I complained about Atom being slow. People asked me, "how fast did it startup?" I said, "2 seconds". Whole room bursts out laughing, and someone said sarcastically "yeah bro that's a total 2000ms, that's a lot of time!" The future is dark.
-
I've had something similar with VS Code, then when I showed how fast both
@4coderEditor and RemedyBG by @x13pixels are, people started to understand. Could you show people something running properly and show them what can be done?
End of conversation
New conversation -
-
-
@cmuratori , Is there a VS feedback item about this? Curious, since you mentioned that syntax highlighting is causing slowness. -
Where did I mention anything like that? The only thing I said in the tweet was that _someone on Reddit_ claimed that the fact it does syntax highlighting is a valid reason Visual Studio is extremely slow. Of course this is absurd; well-implemented syntax highlighting is instant.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.