Yes, and neither is any of Rust, Go, Nim, Crystal, Haskell, or similar programming "languages". The future is "programming systems" where the UI, views, and workflow designed in tandem with any language and semantics bits within it.https://twitter.com/dabeaz/status/1226918468911534112 …
-
Show this thread
-
To elaborate: It's like everyone has decided "lets organize system behavior by writing text source files, modified in editors, built by batch compilers and run as single processes with ephemeral state". Then all innovation is happening within this frame:
3 replies 8 retweets 29 likesShow this thread -
What if the text looked different? New language! What if we had too many files? Build systems! What if the editors emulated hypermedia? IDEs! What if we wanted to scale beyond one process size? Orchestration! Instead: What if we looked outside this frame? Any creative solutions?
5 replies 1 retweet 30 likesShow this thread -
Replying to @chatur_shalabh
Text is the core on which the whole ecosystem is built (incl. Ides
). And that's a pretty cool thing.
But to look further, I like the attitude of #NoCode. I would just interpret it as Not only Code.1 reply 0 retweets 2 likes -
Replying to @derjan
I'm not saying no-text. I'm saying no-text-files. Eg. spreadsheets, pharo, darklang, lamdu, subtext all have plenty of text but are outside the frame of "text file editing".
4 replies 1 retweet 7 likes
For programming beyond text, see also projectured, by a former collaborator of Simonyi's Intentional Programming. And Cyrus Omar's Hazel. For persisting code and data without files, see Orthogonal Persistence, and of course, my blog http://ngnghm.github.io .
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!