Could the defenders of Stackless Python please explain _why_ this is such a great idea? Just and Christian seem to swear by it, but I'd like to hear of some simple examples of programming tasks that will be programmable in 50% less code with it (or 50% more understandable code, for that matter). And, similarly, could the detractors of Stackless Python explain why it is such a bad idea. A lot of core-pythoneers seem to have misgivings about it, even though issues of compatability and efficiency have been countered many times here by its champions (at least, it seems that way to a clueless bystander like myself). I'd really like to be able to take a firm standpoint myself, that's part of my personality, but I really don't know which firm standpoint at the moment:-) -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | ++++ see http://www.xs4all.nl/~tank/ ++++
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