I appreciate when some of these older threads get resurfaced for us newcomers… good read and reinforces some things I’ve been thinking about:
- Focus on scientific and engineering app development, particularly sharing of internal tools
- Leverage the existing, well-understood Julia UI ecosystem players, e.g. Makie and Genie, rather than reinventing yet-another-widget-system
- Be cross-platform. Your practical list of options isn’t too big to explore (and I’ve explored most of them at this point…)
- More recently, I’ve been thinking about the “liveness” aspect and how that is a more Julian experience in parallel with our REPL-based workflows. The discussion here about tools like GUIDE resonates with some things I’ve been looking at this week such as tools like the Pharo Smalltalk environment; I’ve found myself easily able to substitute “Julia” for “Pharo” in many of the threads describing the philosophy behind the environment.
In conjunction with (but, importantly, not dependent upon) improvements in the compilation environment, I agree with the sentiment that such a capability could contribute to a step function in Julia adoption.