jmgrosen's comments

On: A 7k-Pound Car Smashed Through a Guardrail. That's...

[jmgrosen]

Even at 23mph, a pedestrian's chance of death in a collision, in the US over the years 1994-1998, was only 10%: https://aaafoundation.org/impact-speed-pedestrians-risk-seve...

I don't mean to imply that that is a low risk, only that speed is quite a crucial factor.

[sonicanatidae → jmgrosen]

Oh, I agree 100%. Speed kills.

On: A mechanical keyboard with programmable knobs and ...

[jmgrosen]

Especially the Field model!

[Cockbrand → jmgrosen]

Keycap design was probably inspired by 1970s/80s Siemens keyboards, e.g. https://preview.redd.it/6gqyzdshdfp01.jpg?width=1080&crop=sm...

On: A slightly longer Lean 4 proof tour

[jmgrosen]

given the crackpot proofs received by coq-club, i imagine it would indeed

On: FBI warns against using public USB charging ports

[jmgrosen]

are there any documented cases of this actually happening in the wild?

On: Ardour 8.0

[jmgrosen]

Thank you for the self-promotion, Scheme for Max looks like something I’ve been wishing for for a long time!

[iainctduncan → jmgrosen]

thanks! prob the best place to get a sense of it is the youtube videos.

http://youtube.com/c/musicwithlisp

On: The AST Typing Problem

[jmgrosen]

Use an existential type, usually called Some in Haskell: https://hackage.haskell.org/package/some-1.0.5/docs/Data-Som... The implementation of this type one has in their head (a GADT) adds a boxing overhead, but the actual implementation in this library uses a newtype.

That way if you have a type Expr a, you can have a list type [Some Expr].

On: Are you a “harbinger of failure”? (2015)

[jmgrosen]

yes: https://dspace.mit.edu/bitstream/handle/1721.1/130136/The%20...

(sorry for lack of details in my post, on mobile)

On: A Flexible Type System for Fearless Concurrency (2...

[jmgrosen]

No, it’s not—-they’re passing in a “node”, not a list, which always contains both a head element and a (nullable) tail pointer. That’s why it can’t separate the head in the case of size one: the node must maintain a non-null head.

On: Why split lexing and parsing into two separate pha...

[jmgrosen]

Some of you may enjoy this fantastic recent paper on how to win both the comprehension benefits of splitting lexer and parser AND the performance benefits of fusing them: https://www.cl.cam.ac.uk/~jdy22/papers/flap-a-deterministic-...

[e4m2 → jmgrosen]

There is an extended version on arXiv: https://arxiv.org/abs/2304.05276.

Also, the artifact (Docker image + some guides, CC BY 4.0) for the OCaml library: https://zenodo.org/record/7824835.

Edit: The opam file actually says the license is MIT. I'd be more inclined to believe that over CC BY 4.0 as far as source code licensing goes.

[ThatGeoGuy → jmgrosen]

In addition to this, I always think about Matt Might's "Parsing with Derivatives." [1]

I'll have to read about flap, as it seems to utilize a lexer based on derivatives.

[1]: https://www.youtube.com/watch?v=ZzsK8Am6dKU

[ratmice → ThatGeoGuy]

Matt Might also did an article about lexing with regex derivatives.

https://matt.might.net/articles/nonblocking-lexing-toolkit-b...

On: Show HN: Building musical synthesizers with SQL qu...

[jmgrosen]

This is absolutely ridiculous. I love it.