3 ms·
"it’s actually really fast and responsive" Is everyone today equipped with at least 4-core 3GHz i7s or what? Text Edit demo is barely responsive on my Athlon
by przemoc 14y ago
"it’s actually really fast and responsive"
Is everyone today equipped with at least 4-core 3GHz i7s or what?
Text Edit demo is barely responsive on my Athlon 64 X2 4600+ in recent Google Chrome beta (25.0.1364.84) on up-to-date debian wheezy. To the point it's unusable, unfortunately.
I admire the project, it must have been a great fun to build it and it is impressive achievement. Really!
I still hope it may be optimized more, so it will be truly responsive. Even then it doesn't mean it's the right way to go. Web developers, please, do not write your websites as Qt apps to compile them later with emscripten-qt!
- stuffihavemade 14y agoI have a 4 core 2GHZ i7, and it locks up Firefox for me as well.
- azakai 14y agoIt is not optimized at all yet - still using software rendering in pure JS. Will be more interesting with hardware acceleration, I intend to work on that with the author of these ports.
- devongovett 14y agoInteresting. I did find it pretty fast or I wouldn't have written that. I was using Chrome 24 on Mac OS X 10.8 on a 2010 i5 MacBook Pro, so my computer is definitely not the latest and greatest. I guess there must be some difference between the rendering engine on the Mac and on Linux, but I don't know enough to say what.
- sp332 14y agoI've got a 2.8GHz AMD proc running Windows 7. Even Firefox was able to keep up with just a bit of lag, and Chrome was nice and quick.