Live data from Hacker News

I Wrote a Scheme in 2025

maplant.com

61–66 of 66 posts

Re: I Wrote a Scheme in 2025

#61

Earlier quoted context omitted.

- Ease of setup and install. Turnkey. Good defaults. - Non-buffer based workflows. - Easy access to settings. - Easy ways to change or switch my compiler. - Integrated with typical lisp tooling for library, system, and package management. (For example, what Emacs button do I press to set or clear my ASDF compile cache?) - Better integration of the profiler and debugger. When a Lisp error happens, yet another buffer p…

JetBrains IDE plugin for Common Lisp: https://github.com/Enerccio/SLT (I'm sure you saw it before and I don't know how polish it is, and I'm pretty sure it has less features than Emacs&SLIME, yet, but I must link it for reference. Because yes, before 2023 we could complain there were no JetBrains IDE plugin for Common Lisp, since 2023, we have one.)

We all can google. Have you tried to install the plugin? It doesn't support the current version of the IDE and as the last commit was 8 months ago there is no hope it will get such a support soon.

Re: I Wrote a Scheme in 2025

#62

Earlier quoted context omitted.

Please forward your complaints to Martin Richards @ https://www.cl.cam.ac.uk/~mr10/ for making this decision. Also, why?

Sorry, where did Martin Richards supposedly make this decision?

That's how variables are declared in BCPL, the language he designed and implemented in 1967. Keyword "LET", comma-separated list of names, "=", comma-separated list of expressions (that will be used to initialize the variables). For rare cases when one deliberately wants to leave a variable uninitialized, constant-valued expression "?" exists.

Anyway, why is this syntax atrocious?

Re: I Wrote a Scheme in 2025

#63

Earlier quoted context omitted.

JetBrains IDE plugin for Common Lisp: https://github.com/Enerccio/SLT (I'm sure you saw it before and I don't know how polish it is, and I'm pretty sure it has less features than Emacs&SLIME, yet, but I must link it for reference. Because yes, before 2023 we could complain there were no JetBrains IDE plugin for Common Lisp, since 2023, we have one.)

I mean the following with all due respect—and I have a lot of respect for your many efforts and contributions—but it will sound a little blunt, especially as a written comment. "We have one," no, this is a consistent problem with people who evangelize Lisp. We have had "IDEs" for decades. Most of them, except the couple commercially supported ones, were "experimental", "incomplete", "buggy", etc. This includes the on…

ACK, allright. I just want to point people to stuff. Create emulation. Show that the ecosystem is evolving -in the right direction even, maybe. That we are not doomed to stay with Emacs&SLIME. A few years ago, we didn't have SLIMA, the VSCode plugin, Jupyter and JupyterLite kernels, the very useful ICL, nor CLOG, nor these incomplete IDE attempts (Intellij, Sublime…). How good is the new Zed plugin BTW? https://github.com/etyurkin/zed-cl

(I'm not even evangelizing in these comments so thanks for the feedback I guess!)

Re: I Wrote a Scheme in 2025

#64
post #61

Earlier quoted context omitted.

JetBrains IDE plugin for Common Lisp: https://github.com/Enerccio/SLT (I'm sure you saw it before and I don't know how polish it is, and I'm pretty sure it has less features than Emacs&SLIME, yet, but I must link it for reference. Because yes, before 2023 we could complain there were no JetBrains IDE plugin for Common Lisp, since 2023, we have one.)

We all can google. Have you tried to install the plugin? It doesn't support the current version of the IDE and as the last commit was 8 months ago there is no hope it will get such a support soon.

TBH no people don't google (what they don't expect to see), repetition and showing links is necessary. I hadn't followed along. Hope it will get contributors.

Re: I Wrote a Scheme in 2025

#65
post #30
post #25

Earlier quoted context omitted.

I've been playing around with dropping most of the parens, but keeping the rest. https://gitlab.com/codr7/shik

People have played around with those exact ideas for decades. No-one has ever come close to making it work.

It's working just fine here; but I'm not simply changing syntax, this is a ground up redesign.

Re: I Wrote a Scheme in 2025

#66
post #43
post #25

Earlier quoted context omitted.

I've been playing around with dropping most of the parens, but keeping the rest. https://gitlab.com/codr7/shik

Any thoughts on SRFI-119's syntax? https://srfi.schemers.org/srfi-119/srfi-119.html

I don't think this is something that will happen inside of an existing language.

It needs to be a complete redesign where all parts pulls in the same direction.

Post reply on HN