Visual Studio has edit-and-continue, interactive REPL, visualizers, some sort of backtracking and now from Xamarin Interactive Workbooks.
Then you have the whole INotebook trend which started out with Python and nowadays supports multiple languages.
However all these tools are actually catching up with many of the features that Smalltalk-80, Interlip-D, Mesa/Cedar, Lisp Machines, Oberon already had.
This is what Bret Victor jokes about in another presentation of him, where he pretends we are in the 70's making predictions how the world of computers will look like in the 21st century.
The future of programming, https://www.youtube.com/watch?v=8pTEmbeENF4
You can definitely do "something" in smalltalk, lisp machine, but the experience was always hazily defined, and anyways, is quite niche. So as you resort to in your post, people tend to list technical features other than describe experiences, which, even after many of Bret's essays, still need further development before they are realized in production systems (we still don't really know what we want to do, especially what will scale beyond say playgrounds). Experience first, features that can realize it second.
I have been exploring it in the past week and am very impressed.
https://mobile.twitter.com/ontouchstart/status/7584320300362...
Since Swift3 feature list is now finalized (https://apple.github.io/swift-evolution/), many of them will go into iPad playgrounds soon.
I am sure it will become great tool to learn Swift language as well as UIKit at many different levels.
Given that many prefer to build something with duct tape than to pay for tools, the only ones left are the enterprise customers which hardly blink when they compare the tool's prices versus overall project costs.
One just needs to see the angry mobs on HN when JetBrains, Unity, Microsoft and others announce price changes.
Whereas on most enterprises I worked for, it is just a request to the Controller overseeing the project area.
Many of the variables can be changed live in the REPL or with sliders as the code is running. Images can be dragged and dropped into the browser for sprites.
I built reactive (pre-React) Pixi components to make this possible. Victor's work is definitely an inspiration.
In the end I used the components and knowledge to build a touch-compatible shelf-configurator for a client selling shelving products.
https://www.youtube.com/watch?v=vS3yzUo7l8Y
Never really worked well in practice though, it falls apart once you use a 'port'. This was all back then not sure if things have changed.
The point is not that this is the UI of the future, the point is that there are other ways to conceptualize doing knowledge work with a machine, this is one.
Real innovation takes time...
Here's the man himself, Alan Kay, on the topic.
http://www.fastcodesign.com/3046437/5-steps-to-recreate-xero...
Many of his ideas were already possible on the workstation OSes created there.