When I studied at HPI I had a course where we would hack on features for the Lively Kernel. I'm not sure how far they've come and if they got the performance problems solved. (Lively used to work at halfway acceptable speeds in Chrome and Safari only, but I'm not sure if this was because of Webkit or the JavaScript engine.)
I have to admit, I didn't like it much. I couldn't wrap my brain around why I should create a live coding environment which would be destroyed on a reload. Then it is only used as a fancy REPL.
For my day to day programming I prefer regular JavaScript or languages which compile to JavaScript.
Comments
When I studied at HPI I had a course where we would hack on features for the Lively Kernel. I'm not sure how far they've come and if they got the performance problems solved. (Lively used to work at halfway acceptable speeds in Chrome and Safari only, but I'm not sure if this was because of Webkit or the JavaScript engine.)
I have to admit, I didn't like it much. I couldn't wrap my brain around why I should create a live coding environment which would be destroyed on a reload. Then it is only used as a fancy REPL.
For my day to day programming I prefer regular JavaScript or languages which compile to JavaScript.