The problem with new URL(), and how URL.parse() fixes that (kilianvalkhof.com) | HN Screenshots

YHacker Newsscreenshots

Screenshot of kilianvalkhof.com: The problem with new URL(), and how URL.parse() fixes that

First screen, captured 2 years ago.

Looks similar

Screenshot of lemire.me: Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL parsing benchmark

Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL parsing benchmark (lemire.me)

146 points by ibobev 3 years ago | 86 comments

Screenshot of openui.com: We rewrote our Rust WASM parser in TypeScript and it got faster

We rewrote our Rust WASM parser in TypeScript and it got faster (openui.com)

271 points by zahlekhan 7 months ago | 176 comments

Screenshot of mattrighetti.com: You probably don't need query builders

You probably don't need query builders (mattrighetti.com)

133 points by mattrighetti 1 year ago | 129 comments

Screenshot of danielchasehooper.com: The Swift compiler is slow due to how types are inferred

The Swift compiler is slow due to how types are inferred (danielchasehooper.com)

176 points by paraboul 2 years ago | 123 comments

Screenshot of swagnik.netlify.app: How Raw sockets behave differently in macOS and Linux

How Raw sockets behave differently in macOS and Linux (swagnik.netlify.app)

99 points by adityaathalye 2 years ago | 37 comments

Screenshot of whynothugo.nl: Man pages are great, man readers are the problem

Man pages are great, man readers are the problem (whynothugo.nl)

106 points by WhyNotHugo 1 year ago | 132 comments