Web

Collections

The Valley of Code
Web Almanac - HTTP Archive’s annual state of the web report 2022 - HTTP Archive’s annual state of the web report
Have Single-Page Apps Ruined the Web? | Transitional Apps with Rich Harris, NYTimes
Move over JavaScript: Back-end languages are coming to the front-end: A NEW CROP OF SERVER-SIDE TOOLS IS MAKING IT POSSIBLE TO BUILD WEB UIS WITHOUT JAVASCRIPT.
Why Efficient Hydration in JavaScript Frameworks is so Challenging
Web Quality Assurance: From User Requirements To Web Risk Management
- The Web Quality Assurance Checklist: 240 rules to improve your sites and take better care of your users - Version 4 - 2020-2025
The Future Of The Web
HTTP Status Dogs
Safari isn't protecting the web, it's killing it
Front-End System Design Guide. Web developer interview cheat sheet
A Response To "Have Single-Page Apps Ruined the Web?"
When Should You Use Hypermedia?
HTTP/3 From A To Z: Core Concepts (Part 1)
Web Incubator Community Group (WICG) is a community group of the World Wide Web Consortium (W3C) that incubates new web platform features.
View Transitions Break Incremental Rendering
Why HTTP/3 is eating the world

HTTP/3 has seen rapid adoption due to being used by major companies like Google and Meta. It uses the QUIC protocol, which improves on TCP by more extensively encrypting metadata and enabling faster connection setup. QUIC also enhances performance by eliminating issues like head-of-line blocking and improving network handling. While HTTP/3 was created to work over QUIC, the true innovation was QUIC itself, which updates TCP with security and efficiency improvements. QUIC encryption makes it easier to update features, since middleboxes cannot access metadata. Overall, QUIC and HTTP/3 enhance web performance and security by modernizing core Internet protocols.
Write code for the web
- Apple doesn’t care for me as a developer
- The best approach is to write code for the web, where no single company has control.
- https://news.ycombinator.com/item?id=39250406
Dear Developer, the Web Isn’t About You
- The web was originally simple, robust and accessible to all due to technologies like HTML working together in a layered manner.
- Over-engineering websites with complex JavaScript frameworks makes the web fragile and excludes many users.
- Performance and accessibility are major issues for many users but not priorities for most developers.
- "Moving fast and breaking things" prioritizes developers over users and can exclude people from the web.
- Researching user needs upfront through UX instead of just coding could lead to more useful websites.
- The web is heterogeneous, not a controlled platform, so it requires an approach that acknowledges its diversity.
- Simple, progressive techniques like serving HTML first make sites robust and usable for all.
- The goal is caring for all people who use the web, not prioritizing new technologies.
The Wax and the Wane of the Web
"Web components" considered harmful

It's better to use the specific names (custom elements, shadow DOM, templates) instead of the umbrella term "web components" to avoid confusion and make these APIs more approachable.
HTTP Status Codes Glossary

Webview Case

Inspecting Web Views in macOS

Images

WebP is so great… except it’s not

WebP was more prone to posterization and artifacts, especially on photos with smooth gradients.
For similar visual quality on a portrait photo, WebP was actually 30-39% heavier than JPEG.
WebP is not necessarily better than JPEG for all photographic use cases.

Children

Collections

Webview Case

Images