Google Did Not Unilaterally Decide to Kill XSLT(meyerweb.com)

60 points by bkardell 1 year ago | 43 comments

Leaked Google document: “We Have No Moat, And Neither Does OpenAI”(simonwillison.net)

65 points by cube2222 3 years ago | 10 comments

Avoiding HTTP/3 (for a while) as a pragmatic default(utcc.utoronto.ca)

82 points by pabs3 3 years ago | 80 comments

The Linux kernel will fix some peculiar argv usage in execve(2)(utcc.utoronto.ca)

41 points by ingve 3 years ago | 37 comments

OpenWrt 23.05(openwrt.org)

162 points by arcxyz 3 years ago | 61 comments

Google Sidewiki(en.wikipedia.org)

114 points by r721 3 years ago | 76 comments

Google vs. the Open Web(interpeer.io)

463 points by ColinWright 3 years ago | 147 comments

Interpeer Project blog post expanding on a social media post about Google's actions versus the Open Web.

Bypassing Google's big anti-adblock update(0x44.xyz)

941 points by deryilz 1 year ago | 816 comments

Blog post describing a Chrome bug that let extensions keep using webRequestBlocking to bypass Manifest V3's restrictions on adblockers.

Write code for the web(mrmr.io)

384 points by mnvrth 2 years ago | 281 comments

A personal blog post arguing that Apple doesn't care for developers and that the author should write code for the web instead.

The browser's main thread is expensive(kciter.so)

408 points by kciter 1 month ago | 141 comments

A devlog post on kciter.so explaining why work on the browser's main thread is costly and how it affects web app responsiveness.

Dead Internet Theory(kudmitry.com)

597 points by skwee357 9 months ago | 638 comments

A personal blog post by Dmitry Kudryavtsev reflecting on the Dead Internet Theory, starting from his experience browsing Hacker News.

What to Know About JavaScript in 2026(blog.master.dev)

17 points by eustoria 1 month ago | 2 comments

A blog post outlining what developers should know about the JavaScript language and ecosystem in 2026.