MobileRead Forums - View Single Post - Websocket on a K3

NiLuJe · 08-07-2013, 12:03 PM

@twobob: Chromium's sandbox requires a bit of relatively recent (I think? At least it's stuff I didn't roll into my own kernels until chromium started complaining about it) stuff in the Kernel (PID_NS NET_NS).

Not to start an holy war, but I'm firmly in the Firefox camp here

. It's much, much, much better than before, both in terms of CPU & RAM. Although, to be frank, I initially gave up on Chromium because I was tired of patching it all to hell to get decent font rendering out of it on Linux. At least Firefox has always mostly obeyed my fontconfig settings

.

Nothing to do with embedded though, so, err, *whistles*

.

08-07-2013, 12:03 PM	#16
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@twobob: Chromium's sandbox requires a bit of relatively recent (I think? At least it's stuff I didn't roll into my own kernels until chromium started complaining about it) stuff in the Kernel (PID_NS NET_NS). Not to start an holy war, but I'm firmly in the Firefox camp here . It's much, much, much better than before, both in terms of CPU & RAM. Although, to be frank, I initially gave up on Chromium because I was tired of patching it all to hell to get decent font rendering out of it on Linux. At least Firefox has always mostly obeyed my fontconfig settings . Nothing to do with embedded though, so, err, whistles . Last edited by NiLuJe; 08-07-2013 at 12:07 PM.