Fosstodon

0 posts0 participants0 posts today

bitspook<a href="https://infosec.exchange/tags/showerthoughts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#showerthoughts</a>: <a href="https://infosec.exchange/tags/lisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lisp</a> is much more compatible with my <a href="https://infosec.exchange/tags/adhd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#adhd</a> brain than anything else I've tried so far. Exploratory programming, ability to do ~fuck all~ whatever tf, evaluating code from comments, evaluating code from my org files; it all add up to a very fulfilling experience. Long ago, I tried <a href="https://infosec.exchange/tags/haskell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#haskell</a> with a similar goal. I love Haskell and it helped with managing the chaos in my head, but I am not always ready to lay my thoughts out in a coherent manner. In fact I never am until I reach the "gotcha" level where things click in and now I know which abstractions/types to keep. I am hoping <a href="https://infosec.exchange/tags/coalton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coalton</a> will be the bridge I hope it is. I've been reading its docs during commute and stuff, will hopefully try it soon.

frescoI've lost a bit of touch with the <a href="https://mastodon.social/tags/Lisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lisp</a> landscape. What are some new things happening? <a href="https://mastodon.social/tags/Coalton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Coalton</a> looks interesting: <a href="https://github.com/coalton-lang/coalton" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/coalton-lang/coalton</a><a href="https://mastodon.social/tags/LFE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LFE</a> has been here for a long time but overall is still the most exciting "new" Lisp to me.

きゅーけー最近 <a href="https://mastodon.tojo.tokyo/tags/Coalton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Coalton</a> を使っている理由は設計を明示するためで、クリーンアーキテクチャがうまくいくのか試験するにはよい型システムがあった方が嬉しい。 (なんでそもそも <a href="https://mastodon.tojo.tokyo/tags/Lisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lisp</a> なのかというと Lisp でないと趣味で書く気にならないからというのがあり……)

きゅーけー<a href="https://mastodon.tojo.tokyo/tags/Coalton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Coalton</a> で iter:drop! が何故かなかったので自分で定義する必要が生じ、実装の方法をだらだら考えていたら時間が過ぎていた。 <a href="https://mastodon.tojo.tokyo/tags/qkdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qkdev</a>

simendsjoI use <a href="https://fosstodon.org/tags/passwordstore" class="mention hashtag" rel="tag">#passwordstore</a>, but unfortunately, it's a bash script which doesn't work well on <a href="https://fosstodon.org/tags/windows" class="mention hashtag" rel="tag">#windows</a>. A good excuse to try out <a href="https://fosstodon.org/tags/coalton" class="mention hashtag" rel="tag">#coalton</a>, which is an embedded <a href="https://fosstodon.org/tags/haskell" class="mention hashtag" rel="tag">#haskell</a> like language for <a href="https://fosstodon.org/tags/commonlisp" class="mention hashtag" rel="tag">#commonlisp</a>! 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.<a href="https://github.com/simendsjo/passish" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://github.com/simendsjo/passish</a>

blake shaw 🇵🇸<a href="https://mastodon.sdf.org/@screwtape" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@screwtape</a> <a href="https://fosstodon.org/@svetlyak40wt" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@svetlyak40wt</a> <a href="https://emacs.ch/@galdor" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@galdor</a> <a href="https://mastodon.sdf.org/@ldbeth" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ldbeth</a>I think they are pretty similar actually, with the major differences imo being that <a href="https://functional.cafe/tags/scheme" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scheme</a> implementations typically reify stack frames as continuations, allowing you to step through program execution live without necessarily needing a macrostepper, while <a href="https://functional.cafe/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonLisp</a> 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 <a href="https://functional.cafe/tags/Lisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lisp</a>'s lack of a means to perform transformations over locations is one of the biggest obstacles to improving <a href="https://functional.cafe/tags/coalton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coalton</a>'s user experience: <a href="https://twitter.com/stylewarning/status/1574868014855380992" rel="nofollow noopener noreferrer" target="_blank">https://twitter.com/stylewarning/status/1574868014855380992</a>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 <a href="https://functional.cafe/tags/racket" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#racket</a> to pure scheme was at times daunting and very challenging, whereas I could pretty much pick up racket and roll with it.

coderfrogI've been looking into <a href="https://functional.cafe/tags/coalton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coalton</a> as a new language to learn, the way it interfaces with common <a href="https://functional.cafe/tags/lisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lisp</a> seems rad. Trying it out, I'm having some issues fitting it into my workflow. Normally in <a href="https://functional.cafe/tags/emacs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#emacs</a> I use "eval-last-sexp" to define and call functions. Everything in coalton either has to be within "coalton-toplevel" or a "coalton" wrapper, just evaluating raw expressions gives an error.Any ideas about how I can run Coalton code as easily as I can with regular Lisp? Maybe there's a hook I can use to automatically wrap expressions before they're sent to the REPL...

blake shaw 🇵🇸Using <a href="https://functional.cafe/tags/coalton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coalton</a> to implement a quantum compiler <a href="https://functional.cafe/tags/lisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lisp</a> <a href="https://t.co/mofSJ4IxYC" rel="nofollow noopener noreferrer" target="_blank">https://t.co/mofSJ4IxYC</a>

Recent searches

Search options

Administered by:

Server stats:

#coalton