HN user

jogloran

11 karma
Posts1
Comments13
View on HN

I have an early 2011 and have had this problem twice. The latest time I was working in SF and didn't think they would replace the logic board again for free, it being three years out of warranty. They did, which suggests to me that internally Apple has been aware of this problem for quite some time. This program gives me relief because I can see the problem happening again.

If I remember correctly the store said it was due to loose connections between the logic board and the discrete graphics. It originally manifested as lockups as soon as the discrete GPU kicked in. For anyone else seeing this problem, I was able to manage that using a tool called gfxCardStatus which disables the discrete GPU.

I'm pleased that Apple is doing the right thing by their customers and offering to reimburse historical repairs.

Are developers allowed to use these resources freely in their own apps? I ask because "look and feel conflicts with first-party apps" has been grounds for rejection in the past.

Apart from the special meaning of the underscore in interactive mode, and the function _() in Django, I don't think it's common to use _ as a placeholder in Python. I sometimes do it regardless, hoping its meaning should be clear enough, but it's less suitable than in Ruby because you can't use it to ignore multiple arguments.

Ruby also lets you do this in function definitions. Python doesn't special-case the underscore like Ruby does -- while I have occasionally wished otherwise, it is at least consistent with Python's language design principles that the special case doesn't exist.