I'm not sure, but my submissions are being marked as dead automatically now.. So I guess HN thinks I'm a spammer. What's interested is one submission that got 10 upvotes before getting dead'ed
careful submitting to HN. My submissions are now all marked dead automatically for the past 2 weeks... Even one of my blog submissions got 10 upvotes before being marked dead.. No idea why this is happening / how I can stop it.
From what I read at the time, (january 2011) sandforce based SSDs got much better performance on mac systems. I think this was to do with OSX's lack of support for TRIM.
On the other hand, right after I upgraded my SSD, I went to ruby 1.9.2 and rails 3, which are much slower due in part to a bug that makes requiring files take forever.
Not sure about others, but in my case (10 MBP 13" w/ Vertex2 in optibay), I had occasional stalls (anywhere from 2-30 sec) until the TRIM Enabler ( http://www.groths.org/?p=308 ) showed up and I installed it (OSX Lion supports TRIM on this drive natively, it seems).
I think this is because, although sandforce drives have native garbage collection, it can sometimes happen at a very inopportune moment (like say, a 20s "pause" during critical moments of a SC2 game).
What this does is actually pretty simple, it replaces the string “Apple SSD” (used to identify for which drives trim is turned on) in a file in the relevant kernel extension with zeros. It also creates a backup copy of the original file.
The Trim Enabler you linked to replaces a whole kernel extension (meaning you might end up with an older version of a kernel extension) which is obviously monumentally stupid.
I back up with time machine too. I used it once when I had to send my macbook pro in for maintenance. I just hooked up my timemachine drive to my wife's macbook pro, and it worked great.
Cool - good to see other people have thought about this aspect too. I guess the pro of locking it down to a version is that you know it's not going to change until you make an active decision to upgrade. The downside being you don't necessarily get any bug fixes or performance increases of minor version updates. Although that's less of an issue if you don't encounter the bugs.
This is exactly what I've been doing since the start of this year - though not for security, but for reliability. I just feel more comfortable knowing that all my developers will be running the exact same specified version of the gems as every body else.
The big downside to this is that by missing out on the small incremental updates, when you do decide to update (or are forced to), then the chances of something breaking are pretty high as you suddenly leap up 27 versions of the gem. (Which of course makes you want to upgrade less often, which just makes the problem worse =)
I really hadn't thought too much about the security implications of the Gems - this is definitely something I'll need to start considering...
This looks awesome. As somebody who has considered getting into iOS programming, but hasn't taken the dive yet (more focused on ruby based websites / mobile websites right now), thanks for making it open source.
You're welcome - i really hope you get something out of reading through the source. I used to be a ruby guy before this too, so i think you should find the transition not too difficult. Good luck.
This is cool just for fun, but practically there are sites like http://ajaxload.info/ that generate spinners for you, if you don't know how to do it yourself
I tried them and they produced poor quality. They couldn't even get the white background correct! I suppose their #1 ranking on Google is making them complacent.
http://www.loadinfo.net/ is much better presented and actually respects the color values you type in! (And no, I don't have any relationship with them.)