Before everyone out there starts crying HuddleChat, I'd like to point out that the authors have undertaken a major effort to redesign the site to make it look less "cuil-ish". They even thought of the branding and renamed it from "yuil" to "4hoursearch". Why 4hoursearch? Well, let's ask the authors:
It took 4 hours to write the initial code, 4 hours for it to go from unknown to 20 hits / second, 4 hours looking for a domain name and 4 hours to build the brand new UI. Fortunately, it won’t take 4 hours to find something with itSo, why would I (who doesn't even personally work in search) care enough to blog about this? For a couple of simple reasons:
- Not only did the authors "claim" that doing the port was easy, they also provide the proof: you can download the source code and study it. It is a beautiful little piece of code. I probably couldn't have done it in this timeframe, but I can see how someone familiar with the APIs could. Kudos to the engineering work!
- From the first launch of App Engine on, there has been a lot of discussion on the matter of lock in and whether using this environment would force developers to do it the "Google way" and never be able to switch to another platform. 4hoursearch is a great example on how pieces in the cloud can be woven together, interact and enhance each other. This service is using Google infrastructure to perform Yahoo searches -- how more open could the cloud be?!?
- When I originally started this blog, I wanted to focus on how App Engine can be used to develop commercially successful apps with little rampup time or cost. Now, I might have strayed from that path a little bit, but this opportunity is just too good to pass up. If this would not have been a Yahoo executive but a regular garage startup guy, he or she could have promoted the heck out of this and make good money just through ad revenue. Instead, lots of little cookiecutter enterpreneurs now have a perfect template for building their own search engines -- it will be interesting to see how they will make use of it.
0 comments:
Post a Comment