Short answer: I don’t know. That sounds like a good idea, but how would that access local variables in the caller (to inspect state)?
I remember the Lua C API exposes a lot of information, but I didn’t think it was accessible from scripts. Of course, it was a long time ago and I could have easily missed something at the time. Happy to be corrected!
Edit: you might also run into difficulties trying to redefine non-global functions to add the call to “repl”.
Thanks! Most of those seem like a fair trade-off for portability… for an app.
I’m not sure it’s a great idea for an OS as in the OP, but I do like that they claim accurate incremental rebuilds, to ensure everything get updated. Certainly an interesting experiment!
Edit: just to clarify, I meant "app" as in "something that isn't part of the OS/distribution".
It sounds like how the pedals react and one-pedal driving are the reasons they suspect? I was expecting touchscreen-only controls to be mentioned, but for all I know new ICE vehicles are like that too.
What are some current examples of lean software, esp. related to developing and deploying software?
i3? SourceHut? QuickJS? Edit: BusyBox!
I know it’s an open-ended question, but I’m curious to see thoughts from others.
For context, possibly in reaction to porting an app via Electron, I’ve been trying to repent by finding a minimal development environment for hobby projects. I’m not sure it qualifies as “lean”, but Emacs and SBCL strike a nice balance for me right now.
How paranoid should I be about routers from companies like Cudy that I’m not familiar with? My intuition is “very paranoid, even if I replace the firmware with OpenWRT”.
This is schemescape signing off.