News for hackers. Stuff that matters.
Re:What’s Next for Multi-Process Firefox by ploxiln on Wednesday August 03, 2016 @02:11AM (#12215953)
Notice also that the Raw Log loads instantly and is very responsive, in the same Firefox that struggles so much with the fancy travis log page.

I think it is unfortunate that insanely heavy web applications, which can kinda get away with it in Chrome, are forcing everyone to Chrome.

Re:What’s Next for Multi-Process Firefox by bzbarsky on Wednesday August 03, 2016 @12:17PM (#12219072)
It's not just insanely heavy web applications that are a problem.

It's people writing stuff, then it being slow in all browsers, then them optimizing it in Chrome only (basically changing stupid stuff they did that ended up slow in Chrome but maybe fast in other browsers, but not changing stupid stuff that was fast in Chrome but slow in other browsers) and shipping the results.

Re:What’s Next for Multi-Process Firefox by tracker1 on Wednesday August 03, 2016 @02:29AM (#12216018)
It's hard... though, if you work in a mixed environment where different devs use different browsers, some things are better.

Just the same, it's hard to convince people not to bring in the jungle for the banana (appropriated analogy). With today's tooling, it's very easy to use smaller frameworks, and piece together what you need.. but in goes angular, jQuery, lodash and a few other large libraries for good measure. About the only one I'm guilty of bringing in these days is moment... and most of that is because the internals for Date are poorly lacking (maybe it's time to standardize some non-mutating, moment-like ES extensions to Date already).

Re:What’s Next for Multi-Process Firefox by lcarlson on Friday August 05, 2016 @09:14AM (#12232031)
Ugh I just had this debate recently about moment. I opted out of using it as I felt it was just too big for its use case.