533 karma · joined November 14, 2010
Aid climbing means using ropes as aid - you can pull yourself up on ropes (and associated tools).
Quibble about the details as much as you like, it is still the hardest multipitch, bigwall, free climb ever achieved.
Just because it is C doesn't mean you've got a sane libc. Let alone the luxury of a debugger. Just seeing that simple string on the screen/logfile can be a blessed relief.
More recent VxWorks - i.e. anything 6.x, since 2004 - has memory protection.
http://www.vaildaily.com/article/20101104/NEWS/101109939/107...
http://www.smh.com.au/it-pro/business-it/do-as-we-say-not-as...
It took me a little while to track that down as the cause on one of my MacBooks.
http://airlied.livejournal.com/76383.html
"really what they've released is totally useless to anyone who uses or develops this stuff."
It is an interesting system though.
The font is pretty ugly too - I can't easily tell the difference between q and g.
However, it is a neat hack, if not very usable.
GCC 4.5, using popcnt on my Core-i7 860 takes the trivial loop mentioned using "Complement and Compare" from ~10.5s to ~7.5s
And I've even lost a birthday flying back in the other direction. Great scheduling, that.
This isn't helped by the current trend for their articles to be link bait or scraped off a real tech source, rather than anything approximating journalism.
One of the strengths of threads is that they don't have strong protection. If he wants runtime safety like that he should learn what a process is.
Sure, it has been cleaned up a bunch, but doesn't seem like a massive entrepreneurial success (other than as a vehicle for self-promotion).