<story><title>The Ladybird browser project</title><url>https://ladybird.dev/</url></story><parent_chain><item><author>grey_earthling</author><text>&amp;gt; if it works in Chrome, all web developers will adopt it&lt;p&gt;This is why we, tech nerds who understand the problem, must resist monopolies: object to using such APIs. Chrome wouldn&amp;#x27;t be in quite this position if, instead of embracing the monopolist, more techies had warned their non-techy friends and family away from it, like they did with IE.</text></item><item><author>sph</author><text>It is not any easier, because we still have a monopoly running the show, only it&amp;#x27;s not called Microsoft anymore.&lt;p&gt;If anyone threatens Google position, they can literally throw money at the problem, invent some overcomplicated standard, implement it in Blink, and have the competition chase them. It doesn&amp;#x27;t need to go through W3C either, if it works in Chrome, all web developers will adopt it and any smaller engine will necessarily have to support it or risk losing whatever little market share they have left.&lt;p&gt;Having control of the internet now is of greater strategic importance than it was 20-30 years ago when Microsoft was king of the hill.</text></item><item><author>jug</author><text>It&amp;#x27;s been so inspiring to see him and his crew of hackers build a new, independent browser from scratch. I must admit I didn&amp;#x27;t think it was possible on this small scale in terms of man hours and funding.&lt;p&gt;However, the thought has also crossed my mind if we&amp;#x27;re finally seeing fruits of browsers being better standardized on &amp;quot;95%&amp;quot;+ of the popular features -- and if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back. While the web is of course still evolving, it feels more &amp;quot;settled in&amp;quot; than 10-15 years ago.&lt;p&gt;There&amp;#x27;s also the factor that past developers didn&amp;#x27;t have the more complete roadmap set when they initially planned browser design, but now we have huge amounts of web standards already there AND also know how popular they got over time i.e. what to prioritize to support a modern web. One might superficially think there&amp;#x27;s simply more of everything, but I also think ideas that can be discarded. Just imagine that Internet Explorer had XSLT support, and FTP was common once upon a time!&lt;p&gt;It would be interesting to hear more about their own thoughts on these topics!&lt;p&gt;Edit: My bad; XSLT is still commonly supported and by all major browsers but a rarely used feature and stuck in limbo in XSLT 1.0. So it&amp;#x27;s probably among those things that can be safely omitted for quite some time.</text></item></parent_chain><comment><author>scblock</author><text>&amp;quot;Tech nerds&amp;quot; built web sites that only worked in IE back then and &amp;quot;tech nerds&amp;quot; are building websites now that only work in Chrome. Didn&amp;#x27;t have a clue back then, and don&amp;#x27;t have a clue now. Forget warning &amp;quot;non-techy&amp;quot; people and clean your own house first.</text></comment>
<story><title>The Ladybird browser project</title><url>https://ladybird.dev/</url></story><parent_chain><item><author>grey_earthling</author><text>&amp;gt; if it works in Chrome, all web developers will adopt it&lt;p&gt;This is why we, tech nerds who understand the problem, must resist monopolies: object to using such APIs. Chrome wouldn&amp;#x27;t be in quite this position if, instead of embracing the monopolist, more techies had warned their non-techy friends and family away from it, like they did with IE.</text></item><item><author>sph</author><text>It is not any easier, because we still have a monopoly running the show, only it&amp;#x27;s not called Microsoft anymore.&lt;p&gt;If anyone threatens Google position, they can literally throw money at the problem, invent some overcomplicated standard, implement it in Blink, and have the competition chase them. It doesn&amp;#x27;t need to go through W3C either, if it works in Chrome, all web developers will adopt it and any smaller engine will necessarily have to support it or risk losing whatever little market share they have left.&lt;p&gt;Having control of the internet now is of greater strategic importance than it was 20-30 years ago when Microsoft was king of the hill.</text></item><item><author>jug</author><text>It&amp;#x27;s been so inspiring to see him and his crew of hackers build a new, independent browser from scratch. I must admit I didn&amp;#x27;t think it was possible on this small scale in terms of man hours and funding.&lt;p&gt;However, the thought has also crossed my mind if we&amp;#x27;re finally seeing fruits of browsers being better standardized on &amp;quot;95%&amp;quot;+ of the popular features -- and if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back. While the web is of course still evolving, it feels more &amp;quot;settled in&amp;quot; than 10-15 years ago.&lt;p&gt;There&amp;#x27;s also the factor that past developers didn&amp;#x27;t have the more complete roadmap set when they initially planned browser design, but now we have huge amounts of web standards already there AND also know how popular they got over time i.e. what to prioritize to support a modern web. One might superficially think there&amp;#x27;s simply more of everything, but I also think ideas that can be discarded. Just imagine that Internet Explorer had XSLT support, and FTP was common once upon a time!&lt;p&gt;It would be interesting to hear more about their own thoughts on these topics!&lt;p&gt;Edit: My bad; XSLT is still commonly supported and by all major browsers but a rarely used feature and stuck in limbo in XSLT 1.0. So it&amp;#x27;s probably among those things that can be safely omitted for quite some time.</text></item></parent_chain><comment><author>razakel</author><text>We warned people that the government was snooping on everything you transmitted or received.&lt;p&gt;They didn&amp;#x27;t listen or care.</text></comment>