All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Technical Critique of WebKit: Development Challenges and Why Hopp is Moving to Rust

By

birdculture

2mo ago· 8 min readenInsight

Summary

The article is a critical analysis of WebKit (Safari's browser engine) based on the author's experience building Hopp, a screensharing application. The author details numerous technical issues and limitations with WebKit, including poor WebRTC support, inconsistent CSS/JavaScript implementation, and performance problems. The piece explains why the Hopp team is moving away from WebKit and building their screensharing UI in Rust instead, citing reliability and performance concerns. The article combines technical critique with practical development experience.

Key quotes

· 4 pulled
There is an 80% chance, based on a quick Fermi estimate, that the browser was Safari (WebKit).
In this post, I will explain, based on my own experience, why I hate WebKit and the problems we keep hitting while building Hopp.
At the end, I will explain why we are committed to building the screensharing UI inside Hopp's app in Rust, without being Rust-pilled.
Early in our journey, we had to decide between building a web-based solution or a native application.
Snippet from the RSS feed
My experience working with WebKit, and why we are almost ditching it at Hopp

You might also wanna read