If Troy is going to do the implementation, I think the options are Java,
C, and C++. He seems to have religious objections to Perl and PHP. :)
Since JSword is not at the level needed (most of the module drivers and
filters still being absent I believe) I think you can probably expect
something in C/C++. It's just a guess, but I'd bet money on it (except
that now Troy would implement in something else just to make me lose I'm
sure). So I think portability issues won't be any problem.
My suggestion is to use perl/php for fast prototype. And then use C/C++ to replace the implementation to speed up the performance. perl or php is very good for fast prototyping, but I am sure it is not scaleable to huge amount of user. But since we just start to develop this. It is ok to start prototype with it. And once we find out it is too slow because there are too many users, we can choose to to switch to use C/C++ to speed up the performance.
A good Bible software should also offer map. Not sure how many people check my
http://chinesebiblesrc.sourceforge.net/maptest.html
Wonder how can text base browser ever support map....
