Sign Language and a web cam...LOL!
Yeah, so maybe I'm dreaming, but still, there has to be some next generation for this stuff. It's just too wordy and redundant, no matter how much we squash it down and build frameworks to simplify things.
In general, I still find that writing SQL queries is much more succinct than LLBL 1.1 or 2.0, but I rarely use them, because LLBL is so powerful. This is especially true of predicate expressions. Offhand, I don't know how I'd append SQL "language" to support something like prefetch paths, but if I could (haven't really thought about it), it would at least be more pleasant....I think. Something like:
"select company, people by companyID"
would get me the company by companyID and all of the related people. Like I mentioned earlier, even something that would get me half way there for more complex fetches would be a real time saver.
I haven't looked at other ORM products lately, but I do remember seeing some more succinct syntax. What I'd want, though, is something that would just eliminate the copy-paste-adjust stuff I find myself doing frequently for fetches that have the same basic pattern, but on different entities with different prefetch paths.
Re: a community library, y, that would be sweet, but offhand I'm not sure how it would apply to the copy-paste-adjust world of cranking out DAL methods for a slew of different fetches against different tables with different prefetch path and filtering needs.