Comments for halostatue

Comment on Mac Recipe Management Programs by Ben Lachman

Ben Lachman — Sun, 30 Nov 2008 04:41:20 +0000

Thanks for the good comparison. I’m the developer of SousChef and I’m definitely hoping SousChef will become the best of breed cooking software on the Mac. There are many features and tweaks planned for SousChef and since it’s only at 1.0.1 I think it has plenty of room to grow. I’d love to chat with you some offline about ideas for future priorities and features.

Comment on Revisiting the iPhone on Rogers/Fido by Tim Breitkreutz

Tim Breitkreutz — Sun, 13 Jul 2008 18:43:46 +0000

I was going to cave in too–until I phoned Fido and found out that I don’t qualify for a plan renewal for another 6 months (I signed a two year contract one year ago to get a “free” phone upgrade–to a fairly nice Nokia). I could tell the Fido rep on the phone was just doing her job, but there was no option except to wait for six months, she said.

How incredibly dumb.

I hope you enjoy yours, though! :)

Comment on Revisiting the iPhone on Rogers/Fido by Long Nguyen

Long Nguyen — Sun, 13 Jul 2008 16:22:09 +0000

I got the data plan with a 100 weekdays and 1000 evenings/weekends + $15 value pack, so it ends up being $70 + all the crap like system access fee.

Comment on A Legend Passes by Lyle Johnson

Lyle Johnson — Wed, 05 Mar 2008 03:21:25 +0000

I’m experiencing some heavy feelings of nostalgia the more I read this evening. I don’t remember as many of the details as you do—I had stopped playing D&D by the time I started college—but I do remember how it helped me overcome my shyness and make new friends. I wonder if I still have my old Monster Manual packed away in a box somewhere?

I remember Villains & Vigilantes, too. We also played a lot of Traveller, plus other games that I’ve since forgotten.

Comment on I Paid for Twitterrific by austin

austin — Wed, 09 Jan 2008 18:33:14 +0000

It’s not twitter-spam. It’s me importing my tweets into my blog and RubyCorner having been configured to follow my entire blog, not just Ruby entries. Since I’ve changed the use of my blog, but haven’t looked at RubyCorner in 18 months or more, I haven’t actually noticed. (I don’t use planets, for the most part.)

Just for you, I’ve changed the RubyCorner configuration. Happy now?

Comment on I Paid for Twitterrific by dlg

dlg — Wed, 09 Jan 2008 10:08:30 +0000

your twitterings get rss-ed to the rubycorner site. why do you think that anyone there is interested in your brown rice risotto? if i want to know, i’ll choose to follow you.

this is twitter-spam

please stop it

Comment on Save a Lemur: Club Thievey by Britgirl

Britgirl — Fri, 04 Jan 2008 01:57:23 +0000

This reminds me I need to renew my commitment to MSF… thanks for an interesting article.

Comment on I Paid for Twitterrific by Lyle Johnson

Lyle Johnson — Fri, 04 Jan 2008 01:49:02 +0000

I’ve been putting off paying for Twitterrific even though I too have it running most of the time. I have paid for a lot of other Mac shareware (more so than I ever used to when I ran Windows) and so I don’t know what’s keeping me from registering Twitterrific. I’ll add it to the list of New Year’s resolutions!

Comment on Optimize What? by Eugen

Eugen — Fri, 21 Dec 2007 14:46:21 +0000

There is no large causation between the size of the code and memory consumption. Write a tiny program which keeps mallocing to prove this, if you will. In any case the runtime linker loads in the necessary methods across a 4K page boundary - it doesn’t load in the entire object, unless needed ( there is a mechanism at link time , not well advertised by Apple , to create a link “order file” which places the code on disk - and pages - in the order they are called. This requires some empirical research beforehand to work out optimal oder). Linkers also strip out “dead code”, I dont think this will work for factory methods - one of the bugbears of the CTGradient haters.

Of course this 4K is insignificant - what makes a program big in ram is data, not code. The real memory cost of the CTGradient is the Apple based drawing routines which use video memory to draw on the screen. The bigger the gradient window, the bigger this cost. So rather than optimizing the CTGradiant class the lad could have made more impact on runtime memory by using less gradiant, which is far more significant than any memory increase caused by the use of a large class most of which will not be loaded in by the loader - and even if the rest of the 4K page loaded in was redundant the real memory cost is less than 4K memory, because some of that code *was* needed after all.

We are not coding for calculators anymore.

Comment on Amnesty Condemns Canada on Death Penalty by Pit Capitain

Pit Capitain — Fri, 09 Nov 2007 16:25:03 +0000

Austin: thank you very much for this post.
Anonymous: human rights have nothing to do with left- or right-wing.