Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/nekohayo/statuses/115747290552272112">Jeff Fortin T. (風の庭園のNekohayo) (nekohayo@mastodon.social)'s status on Sunday, 21-Dec-2025 06:07:33 JST</a><a href="https://mastodon.social/@nekohayo" title="nekohayo@mastodon.social"><img src="https://gnusocial.jp/avatar/156994-48-20250723193659.webp" width="48" height="48" alt="Jeff Fortin T. (風の庭園のNekohayo)" style="position: absolute; left: 0; top: 0;">Jeff Fortin T. (風の庭園のNekohayo)</a><div><ul><li></ul></div></section><article><p><a href="https://mastodon.social/tags/Mozilla" rel="tag">#Mozilla</a> choosing to kill embeddable Gecko (make it a <a href="https://mastodon.social/tags/Firefox" rel="tag">#Firefox</a> only engine, essentially) over a decade ago was such a tragic mistake.</p><p>Alternative browsers &amp; desktop apps had no choice but to go with WebKit or Blink/Electron.</p><p>As a result, Mozilla have nobody to blame but themselves for their minuscule marketshare and nil developer mindshare today.</p><p>Further readings:<br>* <a href="https://lwn.net/Articles/436412/" rel="nofollow">https://lwn.net/Articles/436412/</a> (circa 2011)<br>* <a href="https://www.chrislord.net/2016/02/24/the-case-for-an-embeddable-gecko/" rel="nofollow">https://www.chrislord.net/2016/02/24/the-case-for-an-embeddable-gecko/</a> from <a href="https://mastodon.social/@Cwiiis">@Cwiiis</a> <br>* <a href="https://dutherenverseauborddelatable.wordpress.com/2016/03/07/the-gecko-monoculture/" rel="nofollow">https://dutherenverseauborddelatable.wordpress.com/2016/03/07/the-gecko-monoculture/</a> from <a href="https://tabletop.social/@Yoric">@Yoric</a></p><p><a href="https://mastodon.social/tags/OpenWeb" rel="tag">#OpenWeb</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/5974887#notice-11755149">In conversation</a><time datetime="2025-12-21T06:07:33+09:00" title="Sunday, 21-Dec-2025 06:07:33 JST">about 7 months ago</time> <span>from <span><a href="https://mastodon.social/@nekohayo/115747290552272112" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@nekohayo/115747290552272112">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://www.chrislord.net/2016/02/24/the-case-for-an-embeddable-gecko/">The case for an embeddable Gecko</a></h5><div> from <span>Chris Lord</span></div></header><div></div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: static.lwn.net</div><h5><a href="https://lwn.net/Articles/436412/">Mozilla kills embedding support for Gecko layout engine (The H)</a></h5><div></div></header><div>The H describes Mozilla's plans to remove the ability to embed the Gecko layout engine into oth [...]</div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: s0.wp.com</div><h5><a href="https://dutherenverseauborddelatable.wordpress.com/2016/03/07/the-gecko-monoculture/">The Gecko monoculture</a></h5><div> from <span>yoric</span></div></header><div>I remember a time, not so very long ago, when Gecko powered 4 or 5 non-Mozilla browsers, some of them on exotic platforms, as well as GPS devices, wysiwyg editors, geographic platforms, email clien…</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Jeff Fortin T. (風の庭園のNekohayo) (nekohayo@mastodon.social)'s status on Sunday, 21-Dec-2025 06:07:33 JSTJeff Fortin T. (風の庭園のNekohayo)
- Cwiiis
#Mozilla choosing to kill embeddable Gecko (make it a #Firefox only engine, essentially) over a decade ago was such a tragic mistake.
Alternative browsers & desktop apps had no choice but to go with WebKit or Blink/Electron.
As a result, Mozilla have nobody to blame but themselves for their minuscule marketshare and nil developer mindshare today.
Further readings:
* https://lwn.net/Articles/436412/ (circa 2011)
* https://www.chrislord.net/2016/02/24/the-case-for-an-embeddable-gecko/ from @Cwiiis
* https://dutherenverseauborddelatable.wordpress.com/2016/03/07/the-gecko-monoculture/ from @Yoric
#OpenWeb
In conversationabout 7 months ago from mastodon.socialpermalink
Attachments
1. No result found on File_thumbnail lookup.
  The case for an embeddable Gecko
  from Chris Lord
2. Domain not in remote thumbnail source whitelist: static.lwn.net
  Mozilla kills embedding support for Gecko layout engine (The H)
  The H describes Mozilla's plans to remove the ability to embed the Gecko layout engine into oth [...]
3. Domain not in remote thumbnail source whitelist: s0.wp.com
  The Gecko monoculture
  from yoric
  I remember a time, not so very long ago, when Gecko powered 4 or 5 non-Mozilla browsers, some of them on exotic platforms, as well as GPS devices, wysiwyg editors, geographic platforms, email clien…

Public

Embed Notice

HTML Code

Corresponding Notice