2,029 karma · joined July 18, 2011
And
https://peering.google.com/#/learn-more/faq
And specifically the section on: "What content can Google serve from an edge node?"
Though GitHub will probably have all the same features eventually and cheaper too.
There's pros and cons to that, most folks don't enjoy being inside such a restricted sandbox.
You can see the linked list insertion right below that too.
First, kling worked on WebKit so he's familiar with browser arch already. Fun fact: the AK library in SerenityOS is basically a reimplementation of the WTF library in WebKit (though it's evolved a lot since then). :)
Second, web standards have come a long way since the early days of browsers. If you read through the LadyBird code lots of it is spec language converted to code. That's a testament to the huge amount of work that's gone into web standards in the past 10 years.
Third, the web is designed around the idea that not every browser supports every API and that things should mostly degrade gracefully. So lots of sites probably fall back to slower paths or feature emulation in LadyBird, or just don't render the advanced effects. That's part of the power of the web.
Fourth, the LadyBird browser doesn't try very hard to be fast. Ex. getElementById is O(n): https://github.com/SerenityOS/serenity/blob/f532f9d27935f508...
Similarly LibJS doesn't JIT. Lots of effort in modern browsers is about speed.
Fifth, LadyBird doesn't implement a lot of the modern web. There's stubs for a bunch of APIs:
https://github.com/SerenityOS/serenity/blob/f532f9d27935f508...
https://github.com/SerenityOS/serenity/blob/f532f9d27935f508...
None of that is to negate how awesome SerenityOS and LadyBird are though, I'm a huge fan.
Link lists that use separate nodes (like the project in TFA) are rarely the best choice due to the performance trade offs and way modern CPUs work.
This article explains it well: https://www.data-structures-in-practice.com/intrusive-linked...
See also:
https://github.com/trekhleb/javascript-algorithms/blob/bbbfd...
https://github.com/trekhleb/javascript-algorithms/blob/bbbfd...
Vs what React does:
https://github.com/facebook/react/blob/657698e48d5b093b4ea5a...
For example many of the data structures are implemented with a LinkedList, but the allocations and pointer chasing is likely slower than just using arrays.
In the years that followed folks left Google and joined other companies and created similar build systems because blaze had a lot of advantages at scale. Facebook made Buck, Twitter made Pants. Blaze was still closed source inside Google. They all used the same python looking language.
In 2012 Twitter open sourced Pants: https://blog.twitter.com/engineering/en_us/a/2016/the-releas...
In 2013 Facebook open sourced Buck: https://en.m.wikipedia.org/wiki/Buck_(software)
In 2015 Google finally open sourced most of blaze, but renamed it bazel for copyright reasons. Some might argue they waited too long because clearly there was a lot of demand for such a system. :)
After that Twitter (mostly?) migrated to bazel and Facebook sort of stalled out on Buck. But then recently they decided to rewrite it from scratch to fix a lot of the architecture problems resulting in Buck2.
Buck2 looks pretty impressive and hopefully it gets the bazel folks moving faster. For example the analysis phase in bazel is very slow even inside Google, and Buck2 shows an alternative design that's much faster.
The data says the opposite, the safe browsing list is very effective* which is why many other browsers and systems use the same list to block malicious pages.
Google publishes data about the frequency of warnings displayed too: https://transparencyreport.google.com/safe-browsing/overview
* Of course it could be better.
That doesn't take into account the vastly different cost of living across the world. Sure, 35k USD is a lot compared to some countries, but it's barely scraping by in most US metros.
US wages have not kept pace with the increase in cost of living and goods and services for decades.
Even if folks somehow managed to save 15% of the 35k every year for 40 years (which is really hard) they're left just touching a million with a guaranteed 8% return, and that's their retirement funds. After using those funds to live for the next ~20+ years extremely modestly doesn't leave much of anything for "generational wealth".
Unless you're already in the upper 20% the best bet remaining is to help your kids get through college and hope they get a higher paying job than you. Which is increasingly difficult as the cost of education has skyrocketed compared to wages.
Separately it'll probably get less coverage than things like the incubator shutting down, but I suspect more external impact will be felt as a result of them firing the head of Open Source who's been there for 19 years. :/ Tech press hasn't picked that up yet though.