Threadinology

From ridiculus_fish:

There, that’s the noisome little pitch everyone’s been spreading like so much thermal paste. As if multiprocessing is something new! But of course it’s not - heck, I remember Apple shipping dualies more than ten years ago, as the Power Macintosh 9500. Multiprocessing is more accessible (read: cheaper) now, but it’s anything save new. It’s been around long enough that we should have it figured out by now.
So what’s my excuse? I admit it - I don’t get multiprocessing, not, you know, really get it, and that’s gone on long enough. It’s time to get to the bottom of it - or if not to the bottom, at least deep enough that my ears start popping.

I’m still working my way through today’s post, but whenever this site gets updated you’re always guaranteed a good read. Incidentally, this seems to be one of the few sites done by someone in computer science with a mathematical background, or at least a bent towards math, that I know of (the other basically being Steve Yeggie’s site.) Are there many more out there?

Technorati:

Powered by Bleezer

Comments

Post a Comment

Popular posts from this blog

Xcode 3 language specification changes

So much has changed in Leopard that I am not surprised I cannot find anything about this yet. Basically, the plugin interface for Xcode 3 has severely changed. In particular, over the past few days I have been trying to make a *.pblangspec file for the programming language used by my group for software verification purposes (who, it ought to be noted, I do not speak for on this website). It turns out, that’s not what I really wanted to do. I am still trying to figure out what all has changed, but here are a few key differences: The file format is totally different. This is somewhat superficially noted by the fact that the file’s extension should now be xclangspec as opposed to pblangspec . For instance, I am using Resolve.xclangspec . The file format is totally different. I’m mentioning it twice, mainly to point out that there are no guides out there for it yet. It seems to make sense, if you realize that Xcode is now doing a lot more than just keyword matching and using regular
Read more

Redux on iPhone and iPod Touch, 802.1X and LEAP

Strangely, this from October seems to be getting a lot (well, for me) traffic lately. That’s not really interesting enough to post about, but it seemed that it did make the following note more… well, noteworthy. While I don’t have either an iPhone or an iPod Touch, I do at least know someone who has an iPod Touch and could check this for me. So: It still doesn’t work in version 1.1.3. Although I haven’t seen anything about the iPhone, I would be heavily surprised if it weren’t the same deal there. Technorati Tags: iPhone , iPod
Read more

iPhone and iPod Touch, 802.1X and LEAP

This is more a note for people who were wondering like myself: the current OS X that comes with the iPod Touch and iPhone cannot handle either 802.1X or LEAP (before anyone tells me it handles 802.11x just fine, please remember that 802.1X and LEAP are specific forms of encrypting a wireless connection, not types of wireless connections. 802.1 1 x is instead a generic term used for the varying speeds of wireless, i.e. 802.11a, 802.11b, 802.11g, 802.11n, ….) This is really too bad, as both are have been built in to Mac OS X since at least version 10.3, and also both are the main ways I can get wireless at OSU . I have every intent on finding out if this gets fixed with subsequent OS updates. Incidentally, a big reason I am posting this is due to some Apple Store employees erroneously telling me it should work on the iPhone and iPod Touch, since it is built in to Mac OS X, which shares a lot of common code with the OS X on both devices (as far as anyone seems to know). I don’t fault th
Read more