hencq

Reading this made me realize the Dutch 'bloemlezing' is literally the same word.

I really love this one on dynamic documents as well:

Potluck: Dynamic documents as personal software https://www.inkandswitch.com/potluck/

I think you're confusing Spotify and Shopify.

Haha, yes. I think Silicon Valley (the show ), made fun of the same thing. "Not so long ago, people called the idea of sending a man to the moon a moonshot"

Right, except they mean the exact opposite in this case: they're actually advocating for slowing down the pace. Hence the criticism of the language, because your interpretation would be completely valid.

Yes, same. Initially this seemed like an article I should love, but it was basically impossible to get through, so I stopped reading.

Spot on. Another thing these experts fail to mention is that a lot of the data on the Pacific Garbage patch actually comes from the Ocean Cleanup, since, you know, they actually went out there to look.

I know, but the point is that in Clojure there's a bit of a culture of not writing macros unless you have to, while in Racket there's no such thing. Agreed that you can write macros just fine in other lisps.

Meh, that seems to be a bit of a clojure thing. In the Racket world, with hygienic macros and phase separation, they'll routinely write macros returning macros, etc.

Yeah, when you fail, maybe it could offer a "continue playing" option? Then you can still finish the words, but it doesn't add to your score.

What a great writeup! I really enjoyed reading the whole process and problem solving approach. This is why I come to Hacker news.

I studied in Trondheim for a semester and learned some Norwegian. Whenever I didn't know a word, I just pronounced the Dutch or English word in a 'Norwegian way'. Most of the time people didn't even blink. So much so that I'd then ask them if the word I just used existed and invariably the answer was that that was the correct word.

I think the website does an amazing job explaining it, but it basically takes an interpreter written in C and turns it into a JIT with minimal changes to the code of the interpreter (i.e. not to the code of the program you're running in the interpreter). For example they took the Lua interpreter and with minimal changes were able to turn it into a JIT, which runs Lua programs about 2x faster.

I bought Crumpler messenger bag about 15 years ago (in San Francisco when they still had a store there). Can confirm it’s indestructible. I’m glad to hear they’ve kept up their standards to this day!

I also remember how frustrating and depressing it was that they wouldn’t allow foreign teams to help with the rescue effort. At the time it was clear that the Russians lacked the capabilities to do it. I also think in hindsight it was a sign how little interest Russia had in being part of the West.

Hmm, maybe my memory is betraying me. I remember our first family computer was an XT and then later we had a 386. Maybe I'm misremembering and it was the 386 that had the turbo button or maybe the earlier one was a clone. My first own PC was a 486 as well that I built together with my dad. Good memories.

I think ours had a turbo button that would double/half the clock speed. Good times indeed :)

I think there's something to this. And while America has always had this can-do attitude (just look at the number of self help books), it does seem to be in another gear recently. I don't know what caused it, but I think there have been a number of indicators: Trump ignoring Congress and introducing wild tariffs, Musk firing half of Twitter's staff and then later repeating this with DOGE, the quick roll-out of LLMs. There seems to be this prevailing attitude of "we can just do stuff, damn the consequences".

It appears to come with a lot of corruption and anti-intellectualism. Like you say there are also benefits to this. I think the break through of mRNA vaccines was an early indicator. I just hope we can steer this attitude back to a more optimistic world-view instead of the blatant self serving one that is currently prevailing.

A friend of mine used to once a year hang all his shirts with the open end of the cloth hangers' hooks facing forward. After wearing and washing them he'd hang them back with the hanger facing the other way. After a year he'd toss out any shirts that were still facing the original way and had thus not been worn.

Very cool stuff and great written article. Lone looks very interesting!

Are you planning to use your design to support things like exceptions as well? I think that's where that multi-prompt ability becomes important (yielding from a nested coroutine). Racket has prompts and aborts, which is essentially a 'yield to' primitive.

I like the overview given in this Stackoverflow answer [1] (based on an even earlier comment) which classifies different types of continuations:

- Asymmetric or symmetric

- Stackful or stackless

- Delimited or undelimited

- Multi-prompt or single prompt

- Reentrant or non-reentrant

- Clonable or not

Based on that these generators (or semi-coroutines as the article also calls them) seem to be asymmetric, stackful, delimited, single prompt(?), non-reentrant continuations.

[1] - https://stackoverflow.com/questions/62817878/what-are-the-sp...

Yes! I was racking my brain trying to remember what it was called. Back in the early 2000s I ran BeOS on my desktop and absolutely loved it. Then when they went under, I followed the effort to come up with an open source version with guest interest. There was one effort that wanted to build everything from scratch. That's what was later renamed into Haiku (I think initially openBeOS maybe?). There was also BlueEyedOS who thought you could get there faster by building on Linux and X11.

I think Haiku got more traction because at the time people felt that it should run BeOS software without recompiling. I have long wondered what would have happened if BlueEyedOS would have gotten most of the effort.

Yeah, in the Netherlands 2 finger widths is the norm. But if it's more than that, people will get upset that you're pouring them milk.

Clojure also has the anonymous function syntax with #(foo a b %) where you essentially get exactly this hole functionality (but with % instead of $). Additionally there’s partial that does partial application, so you could also do (partial foo a b).

J++ predates C#. It was Microsoft's version of Java that wasn't quite compatible.

I think that should work in racket-mode as well. You can easily send individual sexps to the repl and add to the live state. However, one thing that CL does that Racket doesn't do (afaik) is when you change a data type (e.g. alter a struct), it automatically ensures live code uses the new types. In Racket by contrast I have to either carefully go through all affected forms and send them to the repl, or send the whole buffer to the repl. This does make the whole experience feel more static than in CL.

Exactly who I immediately had to think of.

> by the bushel

Well played

No, ASML was spun out of Philips (as was e.g. NXP)

I remember at the time it felt a little bit suspicious to me. Only after everyone already knew it had imploded, the navy came out to say their hyper advanced detection system for enemy submarines had of course also detected it.