Mine, an IDE for Coalton and Common Lisp
72 points
8 hours ago
| 7 comments
| coalton-lang.github.io
| HN
MarsIronPI
3 hours ago
[-]
Huh, I wonder why they made their own IDE instead of integrating with Sly/SLIME. Not trying to knock the project, just genuinely curious. Writing a whole editor sounds like a lot of work.

I like the choice of Iosevka as a font, though.

Edit: One value I do see myself getting from Mine is as an example Coalton project. Last time I tried Coalton I couldn't figure out how to get ASDF to load standalone Coalton files. Now I have a working example to copy.

reply
mepian
3 hours ago
[-]
There is an explanation in the blog: https://coalton-lang.github.io/20260424-mine/

> However, the above is a tall order for someone just wanting to dip their toes in, to see if they have any interest in Coalton or Common Lisp. A couple hours on the weekend is easily sunk into getting configurations right, and the right subsystems installed, and the right paths setup, just so the first line of code can be executed.

> mine is not Emacs. It aims to eliminate all of that, and be a Coalton/Lisp-first development environment, whose only job is to be a Coalton/Lisp-first development environment. But more than that, it needs to be accessible. A non-programmer should find it easy to download, install, and run mine with nothing more than a download link.

reply
bitwize
46 minutes ago
[-]
Iosevka is the king of scalable terminal/programming fonts. I'm not sure why, maybe it's because the glyphs have lines and angles that look "terminal-y" in the same pleasing way Terminus and the 3270 font do whilst avoiding the problems that accompany trying to scale a pixel font.
reply
mark_l_watson
2 hours ago
[-]
I live in Emacs, but I will give Mine a try when get a free hour. I read about Coalton in X and follow the author but I haven't invested time yet to try out.
reply
sctb
5 hours ago
[-]
Interesting! Looks like the IDE itself is written in Coalton (https://github.com/coalton-lang/coalton/tree/main/mine) and you can either bring your own terminal or use the standalone version which uses Tauri and Xterm.js.
reply
arikrahman
1 hour ago
[-]
Very cool project and welcome edition to the CL community!
reply
armitron
3 hours ago
[-]
If you're a power user, the sooner you learn Emacs the better as the synergies with any Lisp language (particularly Common Lisp) are simply too strong to be ignored and there is no contemporary alternative that rivals it.

For new users, this looks like a welcome alternative to messy things like Lem that never really worked very well for me.

reply
vfclists
2 hours ago
[-]
Lem doesn't claim to be a Lisp development environment or IDE. It describes itself as

General-purpose editor/IDE with high expansibility in Common Lisp

reply
bitwize
2 hours ago
[-]
I keep hoping the Common Lisp community will step up and deliver better Visual Studio Code support. Asking new devs to learn Emacs, alongside all of Lisp's idiosyncrasies, is too tall an order. I bro'd through it in the 90s but today's new devs have been spoiled by modern UIs (and that's a good thing) and shouldn't have to cope with Emacs and its stubborn retroness.

Seeing something like this is a step in the right direction.

reply
skydhash
46 minutes ago
[-]
> today's new devs have been spoiled by modern UIs (and that's a good thing) and shouldn't have to cope with Emacs and its stubborn retroness.

Two words: Programmable editor.

One of the best advantages of Lisp is the ability to metaprogram. After solving a problem, you find that your code can fit other cases and then you you write a program that will produce the relevant code for those cases. In most other PL you would have to write the slightly different code again or use a template language.

Once you get accustomed to that, you will start to decompose other parts of your workflow in smaller building blocks and realize that only a few parts differ, but they all fits the same workflow. And one of the main realization 99% of them are text, act on text, and produce text. So what you really need is a framework around text, not a bespoke assemblage of tools.

With Unix, you have the text processing tools and vi (some would say ed). All centered around the terminal, the shell and files. Emacs is another version with a lisp vm, a collection of functions and the buffer as the interface. A third version is acme with buffers and mouse clicks as commands. The idea here is to be able to build small tools that can take care of the misc. things we need to do while writing programs. From navigation to analyzing, from formatting to building, and the myriads things in between.

Modern UIs are good for beginner and light usage. Or if you're lucky, they have your specific workflow neatly packaged in some plugins. But when you get tired of having another helpful "update" messing your muscle memory, or want to establish an efficient workflow with some external program (A CL lisp runtime in your case), that's when the weakness appears.

reply
vfclists
1 hour ago
[-]
If Lisp developers want a better editor and IDE they can support Lem.

VS Code doesn't provide the liveness and extensibility Emacs and Lisp developers enjoy in their environments.

reply
bitwize
48 minutes ago
[-]
Lem is still too Emacs-like.

I'm talking about beginners, not seasoned Lisp hands, most of whom—until the great boomer dieoff occurs at least—are already comfortable in Emacs. If you're still just finding your feet in Lisp, you're not aware enough of its tremendous power to miss it from your IDE. You're just wondering why you have to Escape Meta Alt Control Shift to get anything done instead of, you know, just using the menu and mouse commands and keyboard shortcuts that literally everyone else uses.

reply
skydhash
38 minutes ago
[-]
You can always start the REPL on its own and start playing that way.

Or use something like:

  sbcl --load <filename>
Sly/Slime is not essential to play around with Lisp. Emacs just has the right architecture for an REPL workflow. You can do REPL development with Sql and various other programs in Emacs.
reply
threethirtytwo
3 hours ago
[-]
As a programmer for over 2 decades, I permanently stopped using IDEs and text editors this year. It’s really cool to see projects support legacy concepts and ideas though. Love this!
reply
girvo
1 hour ago
[-]
Two decades professionally here too (and nearly three in terms of programming as a whole), and I still use ‘em. Reviewing and adjusting, they make for quite a good experience even in agent-first development with the various nice extensions.

Also I still have to write code by hand, because there’s a whole bunch of edits and adjustments that I’m far faster at shrug

reply
bitwize
51 minutes ago
[-]
Then you are probably not interested in this work at all. It is meant to develop Lisp­—a language whose primary advantage in 2026 is ergonomics to humans, particularly a certain kind of human. If you're doing 100% agentic development, that advantage disappears and you might as well use something popular and statically typed, like Rust or TypeScript.
reply
wild_egg
5 minutes ago
[-]
Technically, I think this is meant to develop Coalton, which is also statically typed and incredibly effective as a language for agents. All those ergonomic benefits that humans enjoy also allow AIs to develop lisp systems quite rapidly and robustly.
reply
greggroth
3 hours ago
[-]
Same. It's an awkward time to develop a new IDE.
reply
nocman
1 hour ago
[-]
nothing awkward about it.

IMHO, It's a better time than ever to develop a new IDE. Just make one that cares deeply about performance (i.e loads instantly, and always has a snappy response). Make features easy to control. Allow me to turn on only the things I care about and to shut the rest off.

I can't even remember the last time I was impressed by the speed of an IDE, though we have more computing power now than ever. I'd love to see someone new come in and wipe the floor with all of the current contenders.

reply
threethirtytwo
2 hours ago
[-]
It’s not awkward at all. It’s a fun project and neat. I support these types of projects. I guess I’m being voted down because people hate IDEs and text editors now.

I think it’s wrong to trash this project just because it’s an older concept.

reply
eikenberry
2 hours ago
[-]
You are being downvoted for calling IDEs and text editors legacy, which is seen as signalling and not contributing to the conversation.
reply