4 ms·
I have a feeling that the recent move to OpenGL rendering for Sublime was a mistake. I know, we did with Firefox and WebRender as well. And yet, when compiling
by kvark 5y ago
I have a feeling that the recent move to OpenGL rendering for Sublime was a mistake. I know, we did with Firefox and WebRender as well. And yet, when compiling a heavy project on a modern machine, I can scroll fine in Firefox, but Sublime chugs, becoming unusable. For Sublime, it should be assumed that some code is compiling all the time!
- galfarragem 5y agoThat's exactly why I still use Sublime3 on my 10 year old, Win7 laptop. Sublime3 works like a charm. If I didn't mind a "slow" tool, I would use VScode instead.
- kyrra 5y agoWhat did it use prior to opengl? Is there a blog o anything that talks about that move?
- rapsey 5y agoSkia
- ben-schaaf 5y agoWe still use Skia for software rendering, OpenGL is only enabled by default on macOS. I've written about the OpenGL implementation here: https://www.sublimetext.com/blog/articles/hardware-accelerated-rendering https://www.sublimetext.com/blog/articles/hardware-accelerat...
- ben-schaaf 5y agoOpenGL rendering is only enabled by default on macOS. Perhaps you don't have it enabled?
- kvark 5y agoInteresting! I’ll try force-enabling it and report back. I don’t recall sublime-3 chugging as much, fwiw.