3 ms·

Yours is a beautiful site, I'm impressed! There's a few reasons why I think I took so long. Listed, in order of time taken: 1. Going off on many, many tangent

by csytan 17y ago

Yours is a beautiful site, I'm impressed! There's a few reasons why I think I took so long. Listed, in order of time taken: 1. Going off on many, many tangents before buckling down and focusing on the core product. 2. Design. I'm a poor designer, and it took me about 7 iterations to get to the version you see now. 3. Fixing bugs. There's just so many of them. 4. Learning about, and implementing custom localization on appengine (needed because there are no filesystem writes for .mo/.po files) 5. Working on it part time

tigerthink 17y ago
"Yours is a beautiful site, I'm impressed!" Thanks. Actually I did everything but the design :-P "1. Going off on many, many tangents before buckling down and focusing on the core product." Yeah, if I had counted those tangents it would have taken me longer too :-) It took me a little over a month starting from scratch, but there were a few weeks of learning before that. "4. Learning about, and implementing custom localization on appengine (needed because there are no filesystem writes for .mo/.po files)" Nice. I actually initially built my site for App Engine, but I decided I needed to have control over my IP address (Amazon's Product API, which I will probably integrate with if I continue working on the site, throttles requests by IP address.) So I went with Linode, which gives you your own IP and the option of renting more for $1/month/IP. I'll bet people would appreciate it if you open-sourced your app engine localization solution, especially if no solutions are currently available.