From: "Grant Griffin" <not.this at seebelow.org> > . . . > The essential trade in using Python is that you give up some run-time > speed to pick up development-time speed--and that's almost always a good > trade. In any application where minimizing run-time speed isn't > important, Python's your man. Actually python is a perfectly good choice for applications where run-time speed -is- important, provided that the 2% of the code where significant CPU cycles are actually burnt are written in C or C++. In many cases this doesn't even require writing extensions since most time is spent inside existing libraries. For example many scientists are using python for serious number- crunching (using numeric python and related libraries). I use python to trade irrelevant run-time speed for development-time speed. And that is always a good trade. :-)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4