From: John Carter Date: 2013-04-10T06:51:41+09:00 Subject: Re: Seeking ideas for new Ruby projects... On Wed, Apr 10, 2013 at 8:12 AM, Hal Fulton wrote: > 3. An embedded mini-language for regular expressions that permits us to > write really complex regular expressions "more as if they were programs" If you going to do that... start off with a PEG, way more powerful. There is a PEG library for ruby somewhere. > 7. A different/better ORM. My personal favorite is Sequel, but I have at > times longed for one that was "inside out" from ActiveRecord. At one time, > Ezra Zygmuntowicz and I brainstormed this idea a little, calling it > PassiveRecord (a name that has since been taken, I think). Have you come across the Object Role Modelling variant of that acronym... http://www.orm.net/ Got bought out by microsoft, they didn't know what to do with it... Seems to be languishing. Now mash that up with http://www.thethirdmanifesto.com/ and you have a killer. > 8. I'm a big believer in dev tools. Anything that measures or diagrams > Ruby code, especially large systems, is interesting to me. As soon as a "round trippable" language of the power of ruby, but more automagically analyzable/provable appears on the horizon... I'm learning it. > 9. A mockup of what "better reflection" might look like in Ruby (think Ruby > 2.2 or later). I have some notes and ideas here. See comment above. I also believe static / strict typing is inverted. Programmers should write code dynamically as per Ruby dynamic / duck typing... but the compiler should infer what types are required by the signatures of the methods applied to them, and then check that the code would work. ie. 99% of code could be statically checked to detect NoMethodError exceptions. (Of course the very dynamic nature of ruby makes it impossible to detect 100%) > 10. A web app (gasp!) for authors (print and web). I believe enough in > the commercial possibilities of this that I won't specify details here. > BTW - the "gasp" is because I normally don't like web coding in general, > and I'm a little disappointed by the giant chunk of time and energy in our > profession that is devoted to it. And I don't like being referred to as a > "backend" developer. Fifteen years ago, essentially ALL computer science > was "backend." Recruiters who think the web is the entire universe can, > well, kiss my backend. End of micro-rant. :) Being playing with client side webby stuff recently... I half like half hate http://d3js.org/ > Comments are welcome... *especially* if you are interested in helping. :) See your comments about developers, ahhh, umm, "agility" at top of your post... :-)) -- ------------------------------ This email, including any attachments, is only for the intended recipient. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If you are not an intended recipient, you may not use, disseminate, distribute or reproduce such email, any attachments, or any part thereof. If you have received a message in error, please notify the sender immediately and erase all copies of the message and any attachments. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission nor can we guarantee that any email or any attachments are free from computer viruses or other conditions which may damage or interfere with recipient data, hardware or software. The recipient relies upon its own procedures and assumes all risk of use and of opening any attachments. ------------------------------