From: Hal Fulton Date: 2013-04-10T05:12:08+09:00 Subject: Seeking ideas for new Ruby projects... --089e01228e426b0b2804d9f32a0b Content-Type: text/plain; charset=ISO-8859-1 I have a bad habit of skipping from one project to another. Actually, many developers I know have the same habit, but I may be worse than most. I am trying to think of an idea that - is interesting to me - is potentially useful - might attract the interest of other developers. Some of my rough ideas are: 1. A todo-list manager (yes, yet another one) with emphasis on extreme extensibility (and with certain optional features that I have never seen all in one place) 2. An old-fashioned text formatter that takes plain text and produces a document. Ruby code may be embedded in it. Adapters permit exporting as HTML, as an ODT, as a PDF, as a Word doc, as XML/RSS/Atom, and so on. 3. An embedded mini-language for regular expressions that permits us to write really complex regular expressions "more as if they were programs" 4. A graphics DSL on top of ImageMagick (like a sophisticated layer on top of RMagick) 5. A "better, more powerful" Ruby interface for Evernote. (The library I have seen is a fairly "thin" wrapper, too thin for my tastes.) 6. A Ruby interface for LibreOffice (as I mentioned in another email). I don't know what's involved in this. 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). 8. I'm a big believer in dev tools. Anything that measures or diagrams Ruby code, especially large systems, is interesting to me. 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. 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. :) Comments are welcome... *especially* if you are interested in helping. :) Cheers, Hal --089e01228e426b0b2804d9f32a0b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I have a bad habit of skipping from one project to another= . Actually, many
developers I know have the same habit, but I may be wo= rse than most.

I am trying to think of an id= ea that
=A0 - is interesting to me
=A0 - is potentially = useful
=A0 - might attract the interest of other developers= .

Some of my rough ideas are:

1. A todo-list manager (yes, yet another one) with emp= hasis on extreme
extensibility (and with certain optional f= eatures that I have never seen=A0
all in one place)

2. An old-fashioned text formatter that tak= es plain text and produces a=A0
document. Ruby code may be = embedded in it. Adapters permit exporting
as HTML, as an OD= T, as a PDF, as a Word doc, as XML/RSS/Atom, and
so on.

3. An embedded mini-= language for regular expressions that permits us to
write r= eally complex regular expressions "more as if they were programs"=

4. A graphics DSL on top of ImageMagick (li= ke a sophisticated layer on top
of RMagick)

5. A "better, more powerful" Ruby interface= for Evernote. (The library I=A0
have seen is a fairly "thin" wrapper, too thin for my = tastes.)

6. A Ruby interface for Libre= Office (as I mentioned in another email). I
don't know = what's involved in this.

7. A different/better ORM. My personal favo= rite 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).
8. I'm a big believer in dev tools. Anyth= ing that measures or diagrams
Ruby code, especially large systems, is interesting to me.
=

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.

10. A web app (gasp!) for authors (print an= d web). I believe enough in
the commercial possibilities of= this that I won't specify details here.=A0
BTW - the &= quot;gasp" is=A0because=A0I normally don't like web coding in gene= ral,=A0
and I'm a little=A0disappointed by=A0the giant chunk of time= and energy in=A0our=A0
profession that=A0is devoted to it.= =A0And I don't like being referred to as a=A0
"bac= kend" developer.=A0Fifteen years=A0ago, essentially ALL computer scien= ce
was "backend." =A0Recruiters who=A0think the web is th= e entire universe can,
well, kiss my=A0backend. End of=A0mi= cro-rant. :)

Comments are welcome... *= especially* if you are interested in helping. :)

Cheers,
Hal

--089e01228e426b0b2804d9f32a0b--