Replying to @elonmusk
This is literally the dumbest thing I've ever read.
Replying to @hydo
Quite some work, I would think, since you'll have to keep up with the continuous changes to the project.
Anyway, if you do it make it open source so I can run lisp-to-dylan on it. Thanks!
Replying to @haxor @munificentbob
In a modern (circa the late '90s) Lisp, they are called head and tail.
For those who are interested in continuing to follow @DylanLanguage , we've moved to fosstodon.org/web/@DylanLang
We'll leave this account active for now, but posts will be on fosstodon.org. You can follow the above DylanLang account from most federated Mastodon servers.
Replying to @_julesh_
People don't seem to think Dylan is a Lisp so maybe it's the s-expressions that really matter to Lispers.
Dylan, because there's so much low-hanging fruit to implement. 😜
Working on improving the devx, with packages, a generalized build/install/update/status tool, a Lisp-like debugger/REPL, and LSP server.
Replying to @AgileSue
What tools are y'all using to write 6502 these days? I used to use the LISA assembler on Apple II+.
A post about current Dylan projects.
mastodon.technology/web/@Dyl…
We'll be posting from @[email protected] first, from now on, but will try and repost things here as well.
New (beta) package manager and package doc site: mastodon.social/web/@sigue/1…
Replying to @nickikt
heh, not sure about "mindy" per se, since Mindy still exists as a thing, but...and hear me out...what about "notbob"?
notbob new workspace foo 🤔
And I forgot there's @ArmyOfBruce 's name, "deft", although that probably had different design goals. Good name though.
A GitHub Action for all of your Dylan continuous integration needs. (Linux-only, for now. macOS and Windows coming soon.)
github.com/marketplace/actio…
Replying to @Apocryphon
In truth, since Dylan is supposed to be a portmanteau for Dynamic Language, we should really pronounce it the way Dave Chappelle does there.
I learned something here today.
So what's a good name for a tool that creates Dylan dev workspaces, builds/runs tests, lists available packages etc? Should we go with boring "dylan" (the current choice) or is there something more fun we could use?
Commence the bikeshedding!

