This continues to drive me crazy. The file-based approach won because it’s *better*. You can’t compete with the existing tooling for files.
-
-
"integrated set of reflective tooling with immediate feedback" doesn't seem to depend on this very much?
-
Unless your scope is first-class and names there late-bound, you can't change it without VM hacks (e.g.: what Chrome debugger does)
-
Ruby `binding` and hacks like Binding.of_caller get you there.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.