I was debating over Job or Jonah for the second book, and decided on Jonah because it’s shorter. This doesn’t mean I’m lazy, it means I don’t want to dedicate a very large amount of my time to a new book when I don’t feel fully satisfied with Genesis. However, with the reader in a semi-stable state I’m ready to make the announcement.
There is still a large amount of work I want to do with the reader, but I have decided to create parallel readers. I made the mistake of updating the last reader in-place and took me three days to complete the new reader, during which the old one was unusable. So having different readers available will allow the user to read the text while I’m working on a new version. Yes, I know about revision control and test sites. I just don’t care — it’s a labour of love, not of money.
At any rate I should put a notice that the user has to click on the verse to get the notes. Or should I? I really like how the NET bible does things, but I also like the comparative columns view that biblegateway has. What I really want to do is merge those approaches, and I’m close — the new reader will combine the best features (in my mind, anyways) of both readers and then we will iterate on usability from there.
Why am I working so hard on the reader and not the text when people can just read the text on the wiki? Because having the notes beside the text allows me to easily edit the text and the notes together. This brings to light the following major issue, that of what exactly the NSV is. The NSV is not Rashi. I’ve merely attached Rashi to the translation as an added service. I have considered moving Rashi to it’s own separate document because of this but it is a very low priority thing.
It’s a thorny problem and I’d rather not worry about it. But with no money to hire a developer to work on an endgame-quality reader, I am stuck with inching foreward like this.
I have some ideas, I should get coding! Look for the book of Jonah sometime in April.