i'm not! i'm deciding whether or not to officially become one whilst playing with this project. i'm torn between IDE's that fall short of what i'm used to, or just a full-screen xterm invoking arcane magics that everyone assures me is what "real men" do. but i'm having fun. i like the elegance.
as for leaving it to me: who uses mono? NO ONE. who uses ruby? lots of people with cool haircuts.
i wasn't gonna say it, but since you mentioned real men: yeah, pretty much. it depends on what kind of software you write -- the java guys i know have fancy IDEs, but the backend hackers (which is pretty much everyone i know both computer-recreationally and professionally, with notable exceptions like snej) all use arcane magic. jeffr, one of the best hackers i know (see jeffr_tech), uses vi on an 80x25 screen and doesn't use colored syntax highlighting 'cause it's distracting.
Lots of people use mono to write programs. Almost nobody uses mono to run programs. Installing the mono runtime on anything but the mono developers' OS is usually fraught with annoying dependencies, oddball version incompatibilities, and other "growing pains" for a language/environment. I'm hoping it's gotten better in the last year or so, because i really enjoyed C# during my short exposure to it.
(And, though everyone seems to be loving the vim lately, i've been an XEmacs user for many years, and am very happy with it. There's a bit of a learning curve, but it's worth it. M-/ is almost as good as IntelliSense. I mean, it's not, but it's almost there. Still miss Visual Studio...)
Hi Evan, Alex here, the guy that sent you the email about my little hack to make posts a few weeks ago. I've been continuing to mess with ljrb, and I've found a little oddity in the way post-making is handled now. It looks to me like you go through trouble when LiveJournal::Request::PostEvent#run() is executed to make sure the anum and itemid are set properly in the Entry held inside the PostEvent, but there doesn't seem to be any way to access that Entry -- I think all you need is an accessor for the Entry, or have run() return the Entry object. Or am I just missing something?
Hm, you're right, sorta: maybe it ought to return that entry. But since it modifies the entry you passed in, you just need to hang on to the one you create. (That's why it goes to the trouble of saving it into @entry on the request object...) It's sorta like the login functionality, which modifies the user that you pass in.