Recent submissions

Comment · 11 days ago
Comment · 1 year ago
Light gray text on white??
Comment · 1 year ago
> The fires in HSS in Germany were determined using web crawling for the year 2023 because no other data was available. All other probabilities were calculated using researched data. The results show a significantly lower probability of an HSS fire compared to a general house fire.

Seems legit.

Comment · 2 years ago
> covid

I don't understand this part. The people who left X after Musk's takeover seem to be mostly people who were on the winning side of Covid, i.e. the side that used the state and media apparatus to coerce people to participate in a medical experiment.

Comment · 2 years ago
You can put the actual definition on page 4, or you can make it easy for the reader and just say "hypermedia controls (like links and buttons)" the first time you mention the term in the abstract.
Comment · 2 years ago
So I've read the title and the abstract, and I still have no idea what a "hypermedia control" is.
Comment · 2 years ago
Maybe address any of the issues raised in the post?
Comment · 2 years ago
Actually, I built this because I don't really understand async/await. Now that I understand generators (somewhat), I might be able to grok async/await ;-)
Comment · 2 years ago
IOW, there isn't any real stack growth, it just appears that way when running in the devtools with the "async call stacks" feature enabled.
Comment · 2 years ago
This appears to be an artefact of the "async call stacks" feature.

To turn it off in Firefox, go to about:config and set "javascript.options.asyncstack" to false.

In Chrome, in Devtools enter ctrl+shift+p and search for "async stack traces".

Comment · 2 years ago
Comment · 2 years ago
Overall I agree: yes, with fexprs you lose some code introspection ability compared to macros. I haven't found it to be a big deal in my fexpr-based hobby Lisp so far.

Re your two points:

You could have "symbol fexprs", analogous to symbol macros, I guess.

For places I think the first-class solution as employed by T and others is better, and would work fine with fexprs: (set (name-of person-1) "sam") simply stands for ((setter name-of) person-1 "sam").

IOW, name-of is expected to be a reader function. Every reader function has a writer function attached to it, that we extract with (setter name-of). Then we call that writer function with the rest of the original arguments.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton