I tried to swim away from the island in Proteus. Wanted to see what would happen. Nothing. Nothing happens. Beautiful, miraculous nothing. I swam, and swam, and the island receded and receded. Sometime during the night, I lost sight of the island, and when the sun rose,…
- Me: Just great, now we're gonna have to use sourceforge! *sarcasm*
Watching a Riak presentation! Distributed, no-sql database. Very interesting stuff.
All weekend is Maine Civic Hack Day, and essentially what that means is that for the next 30 hours straight, several groups are going to be working on free, open-source projects for the community of Bangor, Maine (and possibly adaptable to other communities).
My group (me, two student from my university, and one of their brothers) are working on a project to use gps to track snow plows and give information such as what streets haven’t been plowed in a while (so we could make a web service where people could go and see where to drive and not to drive). This could be extended to any s
I’ll probably post more throughout the weekend about this, too.
who the hell thought making blocking functions was a good idea?
someone who realized that maybe it’s not always necessary or even a good idea to have your code multithreaded
someone who realized that purely synchronous applications of networks might exist at some point
take your pick
still, I figure it’s better to loop and check this every now and then.
I like blocking more often than not, it’s more useful more often than non-blocking. Worse case scenario you can wrap the blocking function in a thread and use a queue to store data from the function, or something along those lines. Just access the thread’s data from another thread as if it was the same function, non-blocking.