That's exactly what I'm trying to find out, hence the chicken and egg problem. You're not going to get people interested in writing clients unless there's a game there but the point of getting people interested in writing clients is avoiding doing the clients in the first place. Nasty spiral, that.
I had no intention of starting down the road of recruiting client writers before having a fully-functional server, a fleshed-out (and implemented) protocol, sample client libraries, and a simple (though hopefully functional) sample baseline implementation that would be used for both demonstrating the system to potential client writers and for testing and debugging the server.
A fair amount of the architecture is complete (although it would have to be retasked for the new goal), but my question was really whether in the abstract sense people would be interested in writing clients -- given a fully functional server -- since if nobody would be interested there's no point in doing it.
Slashdot Mirror
My Model 100 died of unknown causes; it just wouldn't turn on anymore. So I bought a new one via eBay for nostalgia's sake.
It wasn't that great, anyway. Certainly it doesn't shine a candle to Simpsons or Family Guy.
This is true -- the only way to know for sure is to try it and see what happens. I was hoping to get a feel for what people thought of the idea first.
That's exactly what I'm trying to find out, hence the chicken and egg problem. You're not going to get people interested in writing clients unless there's a game there but the point of getting people interested in writing clients is avoiding doing the clients in the first place. Nasty spiral, that.
A fair amount of the architecture is complete (although it would have to be retasked for the new goal), but my question was really whether in the abstract sense people would be interested in writing clients -- given a fully functional server -- since if nobody would be interested there's no point in doing it.