1. 4

“In d3 (or similar tools), once you have a rough napkin draft of what you want, you’re dealing with a file and trying to picture the data in your head while writing javascript code, and then refreshing the web browser to know if your imagination was right, and if not you’re on a static error trace trying to figure out what went wrong. By contrast, in Roassal, once you have a rough napkin draft of what you want, you benefit from the start of the Pharo live coding environment where Roassal inhabits. You begin with a model of the data objects in your domain and then you write a domain specific language for the things you want to do with that data model: importing information, defining prototype visualizations, extending color palettes, adding labels and so on… all while interacting with live data and views objects.”


  2. 3

    A great example of the original design principles, that Dan Ingalls described, in action.

    1. 3

      I know I have said it here before, but also check out Squeak if this sort of thing sounds interesting. Smalltalk environments are fascinatingly interwoven with development itself in beautiful ways that make getting from idea to product feel less like coding and more like building with literal tools and parts.