2,023 karma · joined July 18, 2011
""" Liebeck went into shock and was taken to an emergency room at a hospital. She suffered third-degree burns on six percent of her skin and lesser burns over sixteen percent.[14][13] She remained in the hospital for eight days while she underwent skin grafting. During this period, Liebeck lost 20 pounds (9.1 kg), nearly 20 percent of her body weight, reducing her to 83 pounds (38 kg). After the hospital stay, Liebeck needed care for three weeks, which was provided by her daughter.[15] Liebeck suffered permanent disfigurement after the incident and was partially disabled for two years.[16][17] """
https://en.m.wikipedia.org/wiki/Liebeck_v._McDonald%27s_Rest...
As a reminder given the recent polyfill io attack, don't use public CDN hosted JS without also setting SRI attributes [1]. It's a marginal perf benefit because the cache is partitioned by top level domains now and it opens you up to attacks from the CDN owners.
https://github.com/vshymanskyy/ViperIDE/issues/14
As a bonus set CSP headers and a nonce when you can too, but definitely set SRI on any 3p scripts.
[1]: https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
One of Google's major cultural challenges is imposing the move slow and carefully culture on everything though.
There's something really special about the community and openness of folks who work on web browsers. Maybe it traces it's way back to the newsgroups.
The picture quality on the KV-40XBR700 was amazing for the era (~2003). My Dad cleverly cut a hole into the wall up high and stuck the TV into it, then put a picture frame around it giving us one of the first "high definition flat screens" even if it was an illusion.
Of course these days our 43in TV weighs less than 20lbs and is mounted with a couple small wall anchors.
> The parser core compiles on Google Web Toolkit *and* can be automatically translated into C++
For example:
- Servo vs Blink vs Cobalt do selector matching and style resolution very differently.
- WebKit has a selector JIT, no one else does though.
- WebKit and Blink do layout super differently (with LayoutNG shipped).
- Firefox's html parser is written in Java and converted to C++ at build time.
The big value in folks trying to write new engines is finding these alternate paths. We can't depend on the big three for all the innovation.
That's what's great about Ladybird. Sure it'll need a lot of sophisticated sandbox improvements to get us to a big four situation, but it's more likely its value will be in finding another road the other engines didn't travel across the huge universe of specs, content and features.
There's a fair number of other engines though like Sciter, Flow, Cobalt and Servo.
https://www.figma.com/blog/speeding-up-build-times/
I'm surprised TFA didn't see any improvement though. It makes me wonder if there's bigger opportunities with the build graph shape preventing them from getting optimal incremental rebuilds.
https://github.com/golang/go/commit/af43932c20d5b59cdffca454...
I'd be interesting to see the benchmark after that.
if err == nil || target == nil {
return err == target
}
So the overhead is the function call and 2 comparisons. I wonder if the `isComparable := reflectlite.TypeOf(target).Comparable()` line was moved into a separate function if the compiler would inline Is() reducing the perf impact.Possibly related: https://github.com/golang/go/issues/61502
Looks like they're working on improving the inliner.
It's right to be concerned that a bunch of teams might be a wasting time implementing the same thing slightly differently, or that you'll end up fixing the same bug across all these "copies".
Often that kind of duplication is good for the business though, and the platform team doesn't have the insight to see all the divergent requirements on the horizon. Letting the teams innovate separately without having to coordinate changes in all these DRY-ied up systems can be the best way to support them.
Or even more abstractly, zero codebase chaos is not the optimal amount.