Show HN: Turbo Lisp – A Common Lisp IDE for macOS and the Terminal
When Apple left Clozure Common Lisp behind by switching to Apple Silicon, I started kicking around the idea of building my own Lisp/Objective-C bridge by combining Apple Documentation, the clang AST, and introspection of the Objective-C runtime. There was a CCL porting effort, but I really wanted to use SBCL anyway. Truth be told — what I really wanted was a 21st-century CLIM variant on top of modern AppKit 26. So I let that idea rattle around in my skull for a while — and eventually it bounced
阅读原始来源
来源记录
指标快照
points · 6 votes
2026-11-05 16:03:39.457Z
cumulative since publication
研究分析
变化记录
来源描述：When Apple left Clozure Common Lisp behind by switching to Apple Silicon, I started kicking around the idea of building my own Lisp/Objective-C bridge by combining Apple Documentation, the clang AST, and introspection of the Objective-C runtime. There was a CCL porting effort, but I really wanted to use SBCL anyway. Truth be told — what I really wanted was a 21st-century CLIM variant on top of modern AppKit 26. So I let that idea rattle around in my skull for a while — and eventually it bounced
版本与成本证据
来源票数: 6 votes (2026年11月5日 UTC; cumulative since publication)；前次同口径记录为 6（2026年11月5日 UTC），两个观测值不等于需求增长。
适用与受影响对象
先明确变化影响的现有工作流，再判断是否升级。发布热度不证明效果提升；接口、价格或可用性变化也可能增加迁移工作。
缺失的比较信息
待补齐：新旧行为、受影响套餐与地区、生效时间、兼容性、回退路径及同一工作量下的成本。
采用与迁移验证
保存发布或政策原文，对新旧方案运行同一个任务并比较结果与完整账单；若涉及停服，先核验截止时间再安排迁移。