> On Apr 16, 2019, at 4:02 PM, Brian Goetz <brian.go...@oracle.com> wrote: > > Indeed, it does solve a number of "figure out what was the user thinking" > questions. > > You hit the nail on the head regarding IDE support. Our original thinking > was that it should be easy to cut and paste between a (say) JSON document and > a Java source program, without having to mangle it up in an annoying and > error-prone way. > > I think what you're saying is, in the age of IDEs, that this is not such a > problem, and we should focus on what yields the most _readable_ code, on the > theory that writing is the job of the IDE?
Yes, exactly. Though, as I pointed out in my subsequent message, it’s easy to give the programmer a choice between a quick-and-easy way to cut-and-paste that is easy to write, and a more labor-intensive or IDE-intensive version that may be easier to read (at least in some situations). At least we should explore such options. —Guy
