Great concept. The text editor is broken for me (I place the caret, then try to type, and it only works half the time and jumps around to other spots the other half of the time without inputting any text). Also, I'd like to see results directly, à la CSS editor in Chrome devtools rather than having to run the code.
For me, transparent meaning is far easier for understanding systems than, for example, visual programming (I'm thinking the Unreal Blueprint[1] system)
Yes, it does remind me of Bret Victor's work. Seamlessly moving between coding and manual modes is really cool. I think it requires learning a new LISP like programming language called little.
This is pretty cool and I definitely think direct manipulation is essential to learnable programming.
That being said, direct manipulation should ideally work both ways: it's awesome that changes to the image update the code in real time, but code updates should also instantly update the image. The "run code" workflow is very clunky, especially when popular tools in production today actually do hot code reloading.
it's just a IDE for a programmatic manipulation. Nothing else.
the very thing they show on the 1st video as a flaw of the old approach (run script, then delete some random nodes) still can't happen on their solution.
14 comments
[ 3.4 ms ] story [ 43.5 ms ] threadlink to demo: http://ravichugh.github.io/sketch-n-sketch/releases/index.ht... (click on v0.4 link)
http://ravichugh.github.io/sketch-n-sketch/blog/03-user-stud...
I hope this is really the future
For me, transparent meaning is far easier for understanding systems than, for example, visual programming (I'm thinking the Unreal Blueprint[1] system)
[1]: https://docs.unrealengine.com/latest/INT/Engine/Blueprints/i...
Yes, it does remind me of Bret Victor's work. Seamlessly moving between coding and manual modes is really cool. I think it requires learning a new LISP like programming language called little.
http://www.webcodeapp.com/
That being said, direct manipulation should ideally work both ways: it's awesome that changes to the image update the code in real time, but code updates should also instantly update the image. The "run code" workflow is very clunky, especially when popular tools in production today actually do hot code reloading.
the very thing they show on the 1st video as a flaw of the old approach (run script, then delete some random nodes) still can't happen on their solution.