Browsers are quite slow at rendering _web pages_. What you're talking about is when people don't use the actual 2D page layout and rendering features of the browser, and instead roll their own.
-
-
Replying to @cmuratori @syranide
Well then I try differently. VSCode is fast enough for many devs to use as their primary IDE. And it doesn’t feel slower than VisualStudio which is native. In fact it feels faster.
2 replies 0 retweets 0 likes -
Replying to @gottfired @syranide
It would be helpful if you researched your examples before posting them to this thread, so we don't have to keep repeating ourselves. VSCode is an example of _my point_, not yours:https://code.visualstudio.com/blogs/2017/10/03/terminal-renderer …
1 reply 0 retweets 1 like -
The VSCode team _literally says the DOM is too slow_, right in their own posts:pic.twitter.com/y7t6t7YsU0
1 reply 0 retweets 3 likes -
The reason VSCode feels "fast" - which is kind of absurd, in my opinion, because I've done timings on it, but that's a separate issue - is because they do a lot of work to _avoid_ the actual 2D page layout process in the browser _because it is too slow_. Which is the point.
1 reply 0 retweets 3 likes -
Replying to @cmuratori @syranide
But using web tech VSCode still feels faster than VSPro with Visual Assist. And that's my point UI is not as you claim a solved problem and native not automatically better. I'd take VSC over IntelliJ, Xcode or VSPro any day. I only use those out of necessity.
1 reply 0 retweets 0 likes -
Replying to @gottfired @syranide
I guess me asking you to "please research before posting" is just going in one eye and out the other. Modern VSPro (post-2000) ISN'T NATIVE. It was exactly like VSCode: written in an interpreted language (C#) with a crappy page layout system.
1 reply 0 retweets 2 likes -
If you actually go profile the _last_ Visual Studio that _was_ native, it is _much faster than both current Visual Studio and VSCode_. I know because unlike you, _I actually did that_.
1 reply 0 retweets 3 likes -
You can watch me compare new and old here: https://youtu.be/GC-0tCy4P1U?t=1516 … The results are pretty dramatic. I have also done this test with VSCode's debugger, and it updates _slower than both versions of Pro_ (not that that has anything to do with page layout).
1 reply 0 retweets 7 likes -
Now for the love of god, before you reply to this thread again, can you please go do something quantitative if you'd actually like to add something constructive to this conversation, instead of posting off-the-cuff opinions about things you obviously never actually investigated?
1 reply 0 retweets 5 likes
(And in case it's not clear, the way I do this quantitatively is that I take videos through HDMI and I count the number of frames of lag for recordings of each program, so I can see exactly how latent they are when responding to user input).
-
-
Replying to @cmuratori @syranide
I’ll give you this one. By that definition of performance the Dom is shitty. I would never have thought of doing this because I don’t care if my static text renders at 60.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.