mapped my workspace so I can work directly within the chrome debugger. not the most petty way but it's darn effective since all objects and data are laid before my eyes and can be inspected and manipulated without braking context
That’s cool. I wonder why Google or Mozilla don’t create an IDE that uses their respective devtools to approximate the runtime introspection of a Lisp Machine. This feels like it should be the default solution given that the tools already exist.
I’d love to read a blog post about this. I often pause the chrome debugger and keep it open in a window next to my editor (VS Code, for those counting).
Comments
mapped my workspace so I can work directly within the chrome debugger. not the most petty way but it's darn effective since all objects and data are laid before my eyes and can be inspected and manipulated without braking context
That’s cool. I wonder why Google or Mozilla don’t create an IDE that uses their respective devtools to approximate the runtime introspection of a Lisp Machine. This feels like it should be the default solution given that the tools already exist.
I’d love to read a blog post about this. I often pause the chrome debugger and keep it open in a window next to my editor (VS Code, for those counting).
this is the gist of chrome configuration https://developers.google.com/web/tools/setup/setup-workflow
but the rest depends on your backend because you need the server to hot reload changes from the filesystem
Sweet. Thanks.