home.social

#coalton — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #coalton, aggregated by home.social.

fetched live
  1. Hype for the Future 230D: Jackson County, Ohio

    Overview Jackson County is a notable county in the southern portion of the State of Ohio home to culturally significant communities such as Jackson and Wellston and associated with the Roundhouse and Lillian Jones Museums of Jackson, the Limestone Furnace in the rural southeastern portion of the county, and the World’s Largest Acorn and Welsh American Heritage Museum of Oak Hill. While Jackson and Wellston officially qualify as cities within the county, Coalton and Oak Hill are each […]

    novatopflex.wordpress.com/2026

  2. 🚀 Oh joy, another #language mashup! #Coalton combines all your favorite parts of #Haskell, #OCaml, and #Lisp to create... well, something nobody asked for. 😂 Just what we needed: Common Lisp with a personality crisis. 🤔
    coalton-lang.github.io/ #mashup #programming #humor #HackerNews #ngated

  3. 🚀🎉 Wow, hold onto your keyboards, folks! Another #IDE nobody asked for has arrived to make the already-arcane #Coalton and Common Lisp *easier*—because we all know how desperately the world craves more obscure language tools. 🙄💻 Just what we needed: a one-stop shop for debugging esoterica, now with more hot-reloading than you can shake a dead language at! 🔥🔄
    coalton-lang.github.io/2026042 #Launch #ObscureLanguages #CommonLisp #HotReloading #HackerNews #ngated

  4. Coalton is a typed language build on top of CommonLisp, which takes inspiration from Haskell, Scheme and Ocaml. It supports type classes and in general is fairly enjoyable to use as it integrates well into the existing Lisp tool support. I wrote a small optics library with it (WIP). github.com/justjoheinz/lens

    Leave a comment if you tried coalton too, please.

    #coalton #commonlisp #lisp #optics #library #programming

  5. @kototama They have this disclaimer on potential "substandard user experience" on Github. Robert joked that he'd tag it 1.0 as soon as he could place a published paper somewhere.
    Technically, I think #Coalton is very usable. And as I heard yesterday, it's used in production.

  6. Robert Smith just gave a keynote on #Coalton at the European Common Lisp Symposium, focusing on how Coalton can improve performance while allowing your code to remain more generic than pure Common Lisp code.
    github.com/coalton-lang/coalton
    #Lisp

  7. 🚀 Just when you thought quantum computing couldn't get more convoluted, here's a riveting tale of using a language called "Coalton" to build a #compiler. 🤯 Because if there's anything quantum computing needs, it's the added #complexity of a niche language nobody's heard of. 🙄
    coalton-lang.github.io/2022090 #quantumcomputing #Coalton #technews #innovation #HackerNews #ngated

  8. I've lost a bit of touch with the #Lisp landscape. What are some new things happening?
    #Coalton looks interesting: github.com/coalton-lang/coalto

    #LFE has been here for a long time but overall is still the most exciting "new" Lisp to me.

  9. 最近 #Coalton を使っている理由は設計を明示するためで、クリーンアーキテクチャがうまくいくのか試験するにはよい型システムがあった方が嬉しい。
    (なんでそもそも #Lisp なのかというと Lisp でないと趣味で書く気にならないからというのがあり……)

  10. #Coalton で iter:drop! が何故かなかったので自分で定義する必要が生じ、実装の方法をだらだら考えていたら時間が過ぎていた。 #qkdev

  11. I use , but unfortunately, it's a bash script which doesn't work well on . A good excuse to try out , which is an embedded like language for ! Not exactly production ready quality, but good enough for me.

    Coalton is a really nice pragmatic language and gives the "best of both worlds" feeling.

    github.com/simendsjo/passish

  12. @screwtape @svetlyak40wt @galdor @ldbeth

    I think they are pretty similar actually, with the major differences imo being that #scheme implementations typically reify stack frames as continuations, allowing you to step through program execution live without necessarily needing a macrostepper, while #CommonLisp offers the SLIME/Sly experience on top of countless battle hardened tools & techniques developed over decades, with of course the downsides of a dynamic lexical environments and lack of hygiene that can lead to particularly funky debugging situations.

    Most schemes have let-syntax, which I believe is like macrolet but with syntax-objects, which is another distinguishing difference. Syntax-objects are like records with an AST & source location information. It's worth noting that Robert Smith said that Common #Lisp's lack of a means to perform transformations over locations is one of the biggest obstacles to improving #coalton's user experience: twitter.com/stylewarning/statu

    But overall, scheme systems are typically very bare bones, you're often expected to roll ad-hoc debugging tools that I believe common lisp ships with. But the attraction of this is that our systems are easy to decompose and mold into whatever you need, and tools you simply can't imagine elsewhere (because of lack of first-class continuations) simply fall out the bottom once you get the hand of it. But I'll admit, moving from #racket to pure scheme was at times daunting and very challenging, whereas I could pretty much pick up racket and roll with it.