"... So I want to ask a favor from Arc users: I want to ask for tolerance when I break and change things in what may seem to be arbitrary, small ways. This wil

"... So I want to ask a favor from Arc users: I want to ask for tolerance when I break and change things in what may seem to be arbitrary, small ways. This will make Arc a pain in the ass to write programs on top of, I know, but the end result should be something worth having. ..." This is the bit that will cause a lot of flack. Is there any way to mitigate code breakage? Is it worth it? Maybe users should confine their coding to sketches in one problem domain re-solving it each time the language evolves. Concentrating on how Arc can be improved instead of just the application. The best bit I got from this post was re-reading "Design and Research". [0] So the research being done by users, design by pg? Changing the mindset from app builders to language researchers is difficult but not impossible. [0] http://paulgraham.com/desres.html http://paulgraham.com/desres.html