|
|
Written by Hash
|
|
Monday, 21 April 2008 11:30 |
|
Just read a great article over at Classically Liberal, which neatly exposes the hypocrisy of those who claim to be "Libertarian" and yet favor immigration controls on the basis that as long as a welfare system exists, immigrants get something for nothing and so must be controlled and limited.
The article begins by pointing out the obvious, that further assaults on liberty are no solution for the problems caused precisely by previous statist assaults on liberty. It then takes off on a train of thought that blows away all the smoke and mirrors around the issue of immigrants and welfare, in much the same way as Bastiat puffed away the gaseous sophisms used to justify trade protectionism. |
|
Read more...
|
|
Written by Hash
|
|
Friday, 18 April 2008 05:29 |
|
It's official. As reported by IWR, "Google's board is asking shareholders to vote down attempts to set up a review body to examine the company's role in human rights and to take any steps to stop web censorship." |
|
Read more...
|
|
Written by Hash
|
|
Monday, 07 April 2008 10:15 |
|
My trusted Nokia N800 developed a serious screen malfunction, just about 6 months after purchase. It started with a few vertical stripes down the left edge of the screen, and soon progressed to full fledged mayhem on the screen. In the few months that it worked fine, I'd already become quite dependent on the N800, and am sorely disappointed about the screen crapping out so early in its operating life. I see that a lot of people who bought their N800s from Amazon had similar screen issues. The N800 is within its warranty period, so I'm going to ship it back to Nokia for repair. Meanwhile I'm now the happy owner of a Nokia N810, which is even cooler than the N800, thanks to its smaller size and its slide-out keyboard. |
|
Written by Hash
|
|
Saturday, 08 March 2008 15:32 |
|
|
|
Written by Hash
|
|
Friday, 01 February 2008 06:40 |
|
The OS X bug which was the subject of my last post turned out not to have anything to do with Parallels after all, but with Airport. In certain ad-hoc networks, joining the network makes kernel_task eat up real memory very fast, till the machine becomes unusable. On Panther, it would also cause mouse and keyboard freezes, but on Leopard this hasn't been happening. Turning off airport stops the memory leak, and even releases a chunk of real memory, but doesn't release all of it. I've found that if I create the ad-hoc network through the MacBook, and then have the Zaurus join it, I don't trip up this bug, but if the Zaurus is already connected to the network, and I have the MacBook join it (or create it - in case it isn't detected) that sends kernel_task gobbling memory. It's irritating, but as long as I'm careful about the order in which I have the machines join the network, I can avoid it. It does feel great to have Parallels back in action. |
|
Written by Hash
|
|
Saturday, 15 December 2007 11:08 |
|
Recently my MacBook started crashing very frequently. It would hardly stay up 30 minutes. I noticed that the fans would be on at full speed whenever it crashed, and other symptoms of VM thrashing, such as sluggish trackpad / keyboard response. Checking with top and Activity Monitor showed that kernel_task, PID 0, was in normal use fairly quickly consuming over 600MB of RAM on the 1GB MacBook.
Checking on a PowerBook, I saw kernel_task was using less than 100M of RAM. I didn't have a clue why kernel_task was consuming so much RAM on my MacBook, but after a couple of clean reinstalls of OS X from the original install discs (and immediate application of the 10.4.11 update) I figured maybe it's something in the 10.4.11 update. The PowerBook was running 10.4.10. |
|
Read more...
|
|
|
|
|
<< Start < Prev 1 2 3 Next > End >>
|
|
Page 1 of 3 |
