One of the original authors also published a follow up with some additional details and analysis that may be of interest (still reading through it myself) [0]
yes I think that'd be a great addition. any publisher can, optionally, introduce a hub for their feed, so people get realtime update of their content, and even a social hub, where other authors reacting to their content can use to notify them (and ease the aggregation of these "reactions"). I suspect that can lead to a situation where there are a few hubs and social hubs that anyone can use for their choosing.
I started reading the book but haven't finished it yet. It's also been a while since I've been surfing. I enjoyed the video and it's a good reminder to both finish reading the book and go surfing.
What were your main takeaways of the book and how has it influenced your startup?
I did YC in W20. It's been almost 4 years since I incorporated the startup, and it has definitely not been easy — certainly not the rocket ship story.
The book discusses how progress can only be achieved through error correction and criticism. There are some companies where you can correct errors very quickly and iterate rapidly. However, we are building a cancer diagnostic test, and rapid iteration isn't so straightforward in our context.
The book helped me step out of my bubble, where I was too close to the problem. It allowed me to see that, in perspective, we are still error-correcting on a meaningful problem, even if the process takes years.
I hope you get back in the water and finish the book! Let me know how it goes and what you enjoy about it.
I just finished reading The Master Switch by Tim Wu. It includes the history of broadcasting including why it took so long for FM radio to succeed.
According to him, Sarnoff and Armstrong were friends at some point and RCA financed the development of FM radio initially although they just wanted a more efficient AM network.
The 3 biggest browser engines are Gecko, Webkit, and Blink.
Gecko is the engine behind Firefox and is maintained by Mozilla, so it has a good number of open source contributors that help fix issues when they are found. It also has some issues occasionally but since it has only a ~3% usage these days you don't get as many complaints.
Blink is used by Chromium (which includes Edge, Chrome, Opera, Brave, and Samsung browsers). It has the biggest market share and probably the most people actively paid to work on it.
Webkit is currently only used by Safari and maintained by Apple alone. (Also all iOS browsers have to use webkit which is why iOS chrome has a lot of the same bugs as iOS safari etc). Apple has a conservative approach to Webkit and doesn't implement as many new features or standards as quickly as the other engines. It has the biggest non blink engine market share so it's usually the outlier when it comes to support issues.
Before 2013 Chromium was webkit based, but that year they made a fork and took their engine in a new direction so Webkit lost some of its previous maintainers.
Google could let Chrome rot: Microsoft let Internet Explorer rot back in the days before Edge (primarily because Microsoft recognised that browsers would compete with their Windows monopoly: which is exactly what happened).
> In Internet culture, the 1% rule is a general rule of thumb pertaining to participation in an internet community, stating that only 1% of the users of a website add content, while the other 99% of the participants only lurk.
If you're interested in this topic, I highly suggest some of the talks and papers about the LMAX Disruptor [0] and Martin Thompson's latest project Aeron [1]. It targets the JVM, but the lessons are generally applicable since I don't think Concord/Aria are open source.
[0] https://eprint.iacr.org/2024/696