Late 2006, I posted a rant on the state of concurrent processing on Python.
Looking back, I don't really think I was thinking very clearly that day. I imagine I was contemplating a multi-threaded raytracer in Python. A fun idea, but kind of pointless really. Stupid even.
Since that post, I've implemented exactly one program where I had to explicitly use threads. Why did I need threads? Simply because I wanted non-blocking IO, and couldn't be bothered using other asynchronous mechanisms.
The lesson? YAGNI.
Subscribe to:
Post Comments (Atom)
Popular Posts
-
These are the robots I've been working on for the last 12 months. They each weigh about 11 tonnes and have a 17 meter reach. The control... -
This hard-to-see screenshot is a Generic Node Graph Editing framework I'm building. I'm hoping it can be used for any kind of node... -
So, you've created a car prefab using WheelCollider components, and now you can apply a motorTorque to make the whole thing move along. ... -
MiddleMan: A Pub/Sub and Request/Response server in Go. This is my first Go project. It is a rewrite of an existing Python server, based o...
-
Often, when building a game, you need to test if objects are colliding. The objects could be spaceships, rocks, mouse pointers, laser beams....
-
I've just read a newspaper article (courtesy of Kranzky ) from WA Business News documenting the malfeasance, gross negligence and misc...
-
Unfortunately I've not secured a venue for the GGJ. With 9 days left, things are not looking hopeful. It could be that GGJ Perth will no...
-
After my last post, I decided to benchmark the scaling properties of Stackless, Kamaelia, Fibra using the same hackysack algorithm. Left axi... -
Possibly slightly more correct lighting. The rim light is now only applied in the direction of the sun, rather than being purely based on vi... -
Update: This is another planet shader, with more physical fidelity. Shader "Planet" { Properties { _MainTex ("Diff...
2 comments:
> I ... couldn't be bothered using
> other asynchronous mechanisms.
That's a pity. Sure, at first it's not easy wrapping one's head around Twisted Deferreds, but once you do, you feel peculiarly... empowered. ;-)
There's a donwside to async code: the inside-out appearance it takes on. That can now be minimized, thanks to Python 2.5, Twisted 2.5, and the new inline callbacks.
Give it a spin, you'll not regret it.
Of course there are some users who really do need concurrency across multiple processors, and they are maybe beginning to wonder about their migration path as multicore processors and multiprocessor architectures become more common.
So, while it may be true that you aren't going to need it, that doesn't mean that nobody is going to need it. The stackless environment with its ability to pickle tasklets on one machine and unpickle and activate them on another looks like a potentially usable solution. There may be others.
Post a Comment