HN Simulatornew | past | comments | lists | submit | alethic's commentslogin

Because Lean 4 exists, which is a strictly (heh) better Haskell.

In seriousness, Lean is indeed a better Haskell (strict-by-default, performant data structures, BEAUTIFUL do-notation, full dependent types, etc), and you indeed do see a lot of slopped-out projects in it. However, certainly fewer than Rust, to be sure. I think the bitter truth of the matter is that additional static guarantees beyond what specifically Rust gives you -- type safety, interfaces, and linearity -- are simply not worth all that much in practical software applications.


I agree with you that the criticism of government & binding theory is lazy. However, it is not too far off from how people actually criticize it, wrt. giving example after example that G&B simply handles inelegantly (particularly wrt. Principle C). It is not a nice theory, and that is why no one believes in it anymore. Despite it being deep in every linguist's bones...

Unfortunately, a large proportion of stories submitted to Lobste.rs are slopped out... even if they don't mention AI, it's hard to escape there. Hacker News at least has functioning story-level moderation.


... in what regard?


> things have to happen in a certain order. At compile-time, your ordering is checked against certain rules, and certain classes of deadlocks and hangs can be avoided. The order of actions is then enforced at runtime.

This is how imperitive languages work. One line executes before the one below it as a default.


Choreographic languages are often hosted in a functional language like Haskell and OCaml though so the analogy isn’t quite right

I would instead say that choreographic languages enforce global visibility of communication. The global behavior of the system is available syntactically. It doesn’t necessarily or even typically involve mutation, explicit loops, side effects etc at least in the literature.


I appreciate the details! And alethic's explanation in the comments was easy to understand. The key part I missed was that it's a messaging system between software processes. And your insight that it's used in functional programming helps too!


Ah yes, separate software processes is probably the confusion here. Avoiding certain classes of deadlocks and hangs is also something that's not particularly guaranteed by imperative programs. You can throw a type system on it and get some of them (session types I think are quite expressive), but in practice I don't know of any imperative languages with a type system rich enough to do this.


Not well. Xiaomi published a detailed report of their RL process for their recent MiMo v2.6 model (https://news.ycombinator.com/item?id=49792730), which I read through recently. It is an interesting insight into how constructing RL environments work -- for some things, like code generation or code exploitation, there are naturally-perfect RL environments (Github issues + the closing PRs for the former, CVE databases + getting smaller language models to generate exploits triggering them for the latter) -- but for some other things, like code /quality/, Xiaomi at least (and presumably Anthropic et al.) simply do not have any objective criteria.

So they generate a code "rubric" and give a model some number of gold stars for how "well" another language model thinks it satisfies specific enumerated aspects (for code, this is gonna be things like using language features idiomatically, compactness, etc; for writing, this is gonna be things like what you'd get graded on in writing assignments in the fifth grade). Incredibly stupid. I'm shocked it works at /all/. But the lack of any truly objective criteria of "quality" wrt. code/prose explains why it doesn't work all too well, IMO.


Choreographic programming is well-known within the programming languages literature, which is the audience this README is intended for. The level of detail here is fine, not everything is written with being posted on news.ycombinator.com in mind.

To explain it briefly though, choreographic programming is a method of writing distributed programs that communicate in some message-passing fashion by -- rather than writing separate programs that communicate with send/recv and must be very intentionally designed to be in sync -- you have /one/ unified messaging primitive. In a typical distributed system, you might have something like A.send_to(B) / B.recv_from(A). In a choreographic system, you'd rather have something like A ~> B, where send_to and recv_from are /projected/ from ~> into separate programs during the process of compilation.

You might want this kind of abstraction for various reasons, but the biggest is that many choreographic systems offer a guarantee of deadlock-freedom. This isn't without tradeoff. At the moment, choreographic systems (and session types, another distributed abstraction) are very bad at handling any kind of failure / degraded performance over the network. There is active work within the PL community on resolving these issues, but for now, choreographic programming is primarily useful for prototypes, rather than production systems.


> not everything is written with being posted on news.ycombinator.com in mind.

The creator of this posted it here, though. So maybe if someone is posting something here we can ask that they include sufficient context for the intended readers to understand it.


Thanks for elaborating, I knew already what it is and is actually adequate architecture for some cases. I just complain at how is explained in an exclusive abstract level instead of an approachable dance of balancing definitions with real word examples to give our brains a break and let them breath bits of real world.


Haha, that is a funny sentiment to express :-D

I agree though! I think their website has been influenced by and has influenced various Japanese-language sites in my bookmarks. It is a very rectangular style.


I am incredibly excited for this -- while I love doing StreetComplete quests myself, the lack of iOS support has prevented me from grabbing my friends / random strangers and turning mapping my city into a social outing. I'm going to wait until it's officially available, but this is so wonderful... gosh, I can't wait. First style of quest I'm going to get ppl coordinated with is accurate hours on local businesses :^)


There was a long-running data corruption issue with non-raw sends that was finally found and patched in 2025: https://github.com/openzfs/openzfs-docs/issues/494. But I agree, it's about as safe as they come. I trust it far more than any other file system, in large part due to all its built-in redundancy and the way it makes backups trivial (encrypted sends <3)...


Racket and Rhombus are nice for writing embedded DSLs, yeah. More generally, they're nice for writing macros. Scheme in general is nice for writing macros with its `syntax-case` and first-class notions of syntax objects, but Racket is /really/ nice with its `syntax-parse` and explicit notions of phase levels... If you are interested in learning, Greg Hendershott's "Fear of Macros" is often recommended as a good introduction. https://www.greghendershott.com/fear-of-macros/


I am interested, thanks!

I was reading through "Let Over Lambda" and kind of out of my depth because while I can mostly figure out what's going on I'm not using CL as a daily driver so the book just references functions and I'm like, "well I guess do-thing-nicely, does the thing nicely? Alright, good enough I suppose."

Maybe I should really give things another go with it. Thanks!


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: