Another fun fact - lodash/fp doesn't deduplicate with lodash when bundled. For a couple of months I was wondering why our app had bundled two copies of lodash. I dismissed it as a measurement artifact at first. It took so long to realize there was actually two copies of lodash and it was because one developer on our team had a preference for fp syntax.

Links can have that as their href and it will also work as you'd expect. It's the telephone equivalent of the more well-known mailto: scheme

Now we should add a ?message= query string to be read out loud in the users voice.

It's not random, setting the query string to a new value on every fetch is a cache busting technique - it's trying to prevent the browser from caching the page, presumably to increase bandwidth usage.

It's trying to prevent the server from caching the search. Thousands of different searches will cause high CPU load and the WordPress might decide to suspend the blog.

Pretty sure that blog is hosted on Wordpress.com infrastructure so it's not like the blog owner would even notice unless it generates so much traffic that WP itself notices.

That said I don't think there's many non-malicious explanation for this, I would suggest writing to HN and see about blocking submissions from the domain [email protected]

Note that this is 51kb, it's not exactly lightweight https://bundlephobia.com/package/@js-temporal/[email protected]. Still good for forward compatibility or on the server, but for smaller apps it's significant.

Yep, I’ve been using this one which is lighter (20kB): https://github.com/fullcalendar/temporal-polyfill/

Yeah, supporting iOS 12 in 2025 is odd. I was investigating browser support levels just recently for a library and also settled on iOS 16 as a reasonable level.

For reference, iOS 12.x and below are used 0.33% globally https://browsersl.ist/#q=safari+%3C+13+or+ios+%3C+13. Selecting iOS 16 would still exclude less than 1% globally https://browsersl.ist/#q=safari+%3C+16+or+ios+%3C+16. In both cases the vast majority would be older iOS which is unfortunate because I assume they're on older devices with no upgrade path, but you have to decide on the transpile/polyfill cutoff at some point and browser support has an extremely long tail.

For anyone confused by why the text says the performance is improving between each graph but the lines don't seem to show that - the color for each key and the scale changes between graphs.

Since it didn't gain traction the first time round, I'll just leave this here:

> Clad Labs launches Chad IDE, the first ever "brainrot IDE" https://www.ycombinator.com/launches/OgV-chad-ide-the-first-...

I might be too middle aged to understand. Is this a joke? It's absurd. How did this get funded?

It's because the website is using cufon, a very early attempt at supporting custom fonts on the web using HTML canvas - basically every word you see is rendered as an image rather than text. The end result does not look good on hi-dpi screens like modern Macbook displays, probably they did not exist back then. The site mentions Google Font has a hosted version of it now and you can look at how it is meant to be rendered https://fonts.google.com/specimen/Averia+Libre

Wow, that looks completely different than how Safari rendered the site. Thanks for the link. I like the look of it hosted at Google.

Aaahhh, thank you.

It still looks a little funky but way more readable.

It's the scanline effect, here's three lines of JS to disable it from the developer console

    s=document.createElement('style');
    s.textContent='body::after{display: none !important}';
    document.body.appendChild(s)