I consider LinkedIn to be one of the few genuinely useful things to come out of the whole Web 2.0 gold rush, since it’s a business-oriented, generally ‘fluffless’ site (if I see one more virtual gift or stupid time-wasting Facebook application, I’ll lose all will to live) - as such I actually do use it fairly regularly. I finally got around to creating an OGRE Group - feel free to join if you’re a professional OGRE user / contributor.
I had to chuckle at these comments from Microsoft’s VP for “Windows Consumer Product Marketing” Brad Brooks on what they’re going to do about Vista’s current image problem. He says all the bad things people are saying about Vista are lies: “There’s a conversation in the market place right now and it’s plain wrong,” he claimed. Ah, I see now Brad. As a paying customer I’ve bought several Vista licenses and been totally underwhelmed by what I got for the money, and have been far more engaged with OS X in almost the same period, but I’m just plain wrong.
I’m going to risk being called a dunce for not picking up on this until now, because I think there are probably other people with this annoying problem too. When you’re debugging in VC++, by default raw pointers only display a single item when you expand them, like this: Now, if you know this pointer is actually a series of items and not just one, you really want to inspect them all - you can add array indices (pFoo[n]) but this is awkward if you want to browse rather than cherry-pick single items.
My venerable MX510 has served me well but after a few years of concentrated (ab)use it was somewhat the worse for wear - the scroll wheel died a few months back, and more and more of the low-friction feet had become detached, making it start to limp like a wounded animal. I finally caved this week and took it out to the barn with a 12-gauge. I thought about getting a wireless mouse this time around, but I concluded that I really can’t be arsed to charge yet another wireless device or keep it stocked with batteries, so I stuck with a traditional wired rodent.
I’ve been having a bit of a crappy week, with a particular project taking way longer than I had expected and causing me to explore the darkest crevices of my mind looking for new and creative ways to swear at it, with only mixed success. Cue long hours, too much coffee and Red Bull, and some seriously knotted shoulder muscles. That’s why it was an especially nice surprise this morning to find a box on my doorstep, containing an unexpected gift from a friend & long-time Ogre user in France (tuan kuranes) - a bottle of Champagne and also a bottle of a local speciality, Chartreuse.
Gears of War and Resistance are obviously quite similar game franchises, exclusive on different platforms, and as such rivalry between the teams is to be expected. But I couldn’t help but laugh at the blatant one-upmanship in one of the latest Resistance 2 screens (GOW on the left, for the uninitiated): I can just see the Resistance 2 team sticking their toungues out and going ‘nyaa’ 😀 It’s all irrelevant of course since they’re all pipsqueaks compared to my well-nurtured Katamari.
Oho, I haven’t been rocking out that long to the original yet, but Harmonix unleashed the worst kept secret in music gaming today by confirming Rock Band 2. What they’ve announced isn’t that surprising, but it’s good to have official confirmation that: The instruments from RB1 will work DLC from both titles will be interchangeable Now, really Harmonix would be off their rocker if they didn’t hit these 2 feature points, but it’s worth noting that in particular the cross-title DLC is actually a first, and Harmonix had to liaise with Microsoft and Sony to make sure it happened.
The Muppets were cool. But, times have changed and now we have Fur TV, a distinctly adult, brazen take on the kind of belly laughs you can get out of glorified sock puppets. I’ve caught it a couple of times on TV recently and the first time I randomly came across it I almost choked on my late-night cup of tea. Like all shock-comedy I’m not sure it’ll be long-lasting, but damn is it funny right now.
We’ve had ‘custom memory allocators’ on our upcoming features list for a while. Last year a student did some work on this during the Summer of Code, but the system ended up being a little too ambitious with its use of templates and got a bit too costly in terms of the template instantiation requirements. Unfortunately the student never returned, so I picked up the baton recently, and I felt it was worth writing about some of the things I’ve done, since most of the C++ allocator discussions on the net are pretty shallow and only deal with the simple cases. This is quite a big and fairly technical discussion, so I’ve placed the bulk of it after the jump to spare those who don’t care about this sort of thing! 😀