Post AziNfbejpBG7Ur3fsG by dougmerritt@mathstodon.xyz
 (DIR) More posts by dougmerritt@mathstodon.xyz
 (DIR) Post #AzXyPCiSFJq5wq7psO by nixCraft@mastodon.social
       2025-10-24T21:41:36Z
       
       1 likes, 0 repeats
       
       lmao
       
 (DIR) Post #AziNfbejpBG7Ur3fsG by dougmerritt@mathstodon.xyz
       2025-10-24T21:43:25Z
       
       0 likes, 0 repeats
       
       @nixCraft There are in fact browser-from-scratch projects, but the general problem is that backward compatibility issues are huge, and always have been, and just get worse each year.
       
 (DIR) Post #AziNfcmZdX7YzRjRj6 by tezoatlipoca@mas.to
       2025-10-24T21:48:07Z
       
       0 likes, 0 repeats
       
       @dougmerritt @nixCraft well, I mean @lisamelton could cause she already did. Be interesting to know if she were asked to do so again, could one write a browser engine from scratch in this day and age.
       
 (DIR) Post #AziNfdTp2jiR9Zxz8a by lisamelton@mastodon.social
       2025-10-24T22:10:47Z
       
       1 likes, 0 repeats
       
       @tezoatlipoca Safari and WebKit weren't written from scratch. They were based on the simple KHTML and KJS codebases from KDE. Even back in 2001, I knew better than to try conjuring a Web browser out of thin air.Mind you, we (not just I, it was a team effort) could have done that but it would have taken many years instead of the mere 18 months we were given.And I knew that if I took longer, well, I would have been fired. So practical engineering was the smarter path.@dougmerritt @nixCraft