gecko

let's be serious, chromium and firefox are more 90s style codebases than 2010s. There's thousands of raw malloc calls when I grep in the chromium source tree, and let's not even start talking about firefox where in the same file you've got : - raw mallocs : https://github.com/mozilla/gecko/blob/central/dom/plugins/ip... - new / delete : https://github.com/mozilla/gecko/blob/central/dom/plugins/ip... - "whatever.Allocate<T>" : https://github.com/mozilla/gecko/blob/central/dom/plugins/ip... and that's not limited to a single file... look at this : https://github.com/mozilla/gecko/blob/3e6d6e013400af38f85ceb... - some malloc and new, again - you also get some unique_ptr (because "modern" m'see) : https://github.com/mozilla/gecko/blob/3e6d6e013400af38f85ceb... - moz_xmalloc because why not ? https://github.com/mozilla/gecko/blob/3e6d6e013400a

> then many years later 'box-sizing: border-box' was introduced and widely praised and adopted by frameworks Well, IE implemented their version of the box model in '97 (coincidently, NN4 did the same); the box-sizing property was first proposed in 1999[1], and first appeared in a draft in 1999[2], and implemented in Gecko in 1999[3] and in IE5/Mac in 2000[4]. That's two years from IE/NN shipping the non-standard box model (the standard one was defined before IE4 and NN4 shipped) to having a property to toggle between them. To me, that isn't "many years". Really what makes it seem like many years is the fact that IE didn't implement box-sizing until IE8 which shipped in 2009. [1]: https://lists.w3.org/Archives/Member/w3c-css-wg/1999JanMar/0... (sorry, W3C MO space, but I think at this point nobody cares if I mention that publicly) [2]: htt

One of the major vectors for fingerprinting in various ways is font rendering. It's extremely surprising how integrated with the OS font rendering is, considering it's something that can be done completely seamlessly in userspace for most applications. I spent a long time integrating libpango/cairo (http://www.pango.org/ and https://www.cairographics.org/) into a semi-toy opengl game engine I wrote which had a Windows target, and was baffled at the level of complexity/interdependency required to build it. Gecko (firefox's rendering engine) maintains a fork of cairo https://github.com/mozilla/gecko/blob/0ea4c5812c2adecbed1d84... , which is as far as I can tell the only way to statically link it. Both these libraries require Glib. There isn't an alternate minimalist open-source font rendering library as far as I'm aware, simply because the