randfur

I wish it was more clear about the memory layout of nested variable sized data structures. As far as I can work out the max capacity is decided at construction time which makes the whole thing a lot less intriguing.

I remember a couple of these from a few years ago. Long gone now of course but a fun demo of AI hallucinating the internet endlessly, generated pages from URLs that had more URLs in them to navigate to.

interpolate-size: allow-keywords holy shit, didn't know I'd see the day...

I've never played those mobile ad games and this scratched my curiosity. Now you're telling me they don't deliver and I'm curious again, how do they fail their delivery?

Feature request: Peek the text on hover.

It really needed prev/next buttons, using the scroll wheel with such a long debounce was laborious.

Do people actually believe these dot points or are they just out of scope for most applications to tackle beyond letting the user try again?

This is a parody website that was created long before the recent Googlebook announcement back when it was known by the code name Aluminium.

It's easy to have that view when giving away something not that many people are interested in. Once you're a platform full of media, entertainment and social connection you have to find a way to keep serving billions of users.

No shoutout to P.G. Wodehouse for the IP?

Really looking forward to a how it works post. What is that READMEM_1??

I don't know D so I'm probably missing some basic syntax. If pointers cannot be copied how do you have multiple objects referencing the same shared object?

It's like how talking about the "hockey stick curve" in an exponential growth line is nonsensical. It's everywhere and the curve angles you see depend entirely on what scale you view it from.