1,827 karma · joined January 25, 2008
Then here is what happened:
People started using the tray, taking them as well as leaving them. Then one day a guy started showing up at the store. He would intermittently dump the tray into his knapsack whenever there were enough pennies. Not only he did this for many days, but later he also proudly publicly announced that how he did it. Since all the people who show up at the store are rich and wealthy, it makes more sense to give that money to poor in some other parts of the world.
If this logic is acceptable then I should be allowed to break apart any petty charity collection box and use the money for the purpose I deem more noble.
Fast-forwarding four years and coming to 2011 with django 1.3 and Rails 3.0: I happened to work in another team to build a product in RoR from scrach. I was blown away by what Rails community has achieved while django is lagging behind a lot and is least likely to catch up.
Here are a few highlights:
* As a generic statement, to achieve anything in RoR, usually there is one clear and simple way of doing it. On the other hand in django you can do in many ways and most of the programmers have their own preferable ways. This is ironic considering Python endorses the very same principle but Ruby has a flexible syntax to cater different styles.
* In RoR, you can find a gem for almost anything. Plugging gem in your app is usually extremely simple. On the other, comparatively there are very few usable django apps and integrating them in your django project usually turns out to be painful. * Resolving and maintaining gem dependencies across the team is a piece of cake with bundler. However when it comes to django, I couldn't find a good tool. There is virtualenv but I couldn't find it comparable with the power of bundler.
* Deployment is fun in Rails. In django, it was and still is painful.
* Rails has a far better support for Backend databases, including some support for NoSQL. On the other hand it was just a while back django started supporing multiple databases and that too is hackish approach.
* Databases migrations in Rails are straightforward and explicity. django doesn't have anything like that builtin but does have a django-evolution app which can be really troublesome in some cases.
* Django's restrictive templating system theoretically lets you not shoot yourself in the foot by imposing a new language. But having to learn a new language and dealing with its quirks sometimes makes you pull your hair. Rails approach of embedding Ruby in templates is much more powerful and practically useful. Sure you can override templating systems in both frameworks but defaults are the ones almost everyone uses.
* There are very few hosting services specifically tailored for django. But Rails community boasts services such as heroku which save you so much time that a django fanatic cannot understand.
* I haven't seen testing in Rails in depth but from the bird's eyeview, automated test-cases in Rails seem much more powerful than in django. I might be wrong here.
* Rails has much better documentation and a much stronger community. Compare the Rails and django books on Amazon, questions asked on SO, blogs, tweets, everywhere Rails now dominates.
Its just that I really love Python and prefer it much more over Ruby. Even then I'll probably completely switch to Rails.
What to Submit
On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.
Off-Topic: Most stories about politics, or crime, or sports, unless they're evidence of some interesting new phenomenon. Videos of pratfalls or disasters, or cute animal pictures. If they'd cover it on TV news, it's probably off-topic.
I launched an app back in May 2007 right after their platform launch. After the four years the app is quite broken now and every now and then a user sends me a message about it. Today I decided to spend a day to translate all those "old" API calls into "new & improvides" API calls but due to lack of documentation, unavailability of search results due to all that legacy documentation better SEO'ed and the hectic task of re-testing all the workflows I've previously tested thoroughly, I gave up!
Why should I put in so much effort in re-writing my code just because you don't like a function name or you think same functionality could be achieved by another one so this should be dropped?
I've been doing a startup for years and I never made it to front page of HackerNews, TechCrunch, NY Observer and many other hot places at the same time.
I've advised him to launch a product ASAP. Its gonna be hot and I'm definitely gonna invest :P
ShedSkin: http://shed-skin.blogspot.com/ - A restricted Python-to-C++ compiler.
Cython: http://cython.org/ - A super-set of Python language for writing C extensions.
PS: This post is going to my delicious account
http://techcrunch.com/2009/07/14/in-our-inbox-hundreds-of-co...
It was developed with years of efforts and in 6.5 Microsoft got it much right.
However just because Apple's marketing strategy worked really well, it didn't mean you needed to scrap your well built-in well tested platform in favour of a copy of iPhone called Windows Phone. It has so far not been able to create any excitement in the market yet but on the other hand Windows Mobile has a lot of fans.
Windows Mobile has thousands of useful applications which help so many people around the world. On the other hand, Windows Phone is just a new platform: do you really think scrapping away will convince those hundreds of thousands of Windows Mobile users to upgrade to something on which their favourite apps are no more available?
You need to encash the already built hype and following rather than pretending that you don't have anything at all and starting all over.