I'm using the onboard/ondie Intel HD4000 and it works. You might have a driver that is blacklisted. Chrome and I think other browsers have a list of drivers known to allow execution of dangerous shader code and block WebGL in those cases.
"There is some concern that Apple will have a hard time recruiting a top-notch CEO because of Jobs's presence." reads quite ironically too given how things panned out.
It looks like it made it into WebKit on an experimental basis: http://trac.webkit.org/changeset/125201. This was over a year ago, though; don't know about its current status.
Objective-C is a dynamic language in every sense of the term.
As examples, at runtime, you can:
- change an existing class' superclass
- swizzle methods
- create a class ex nihilo (though it'd be a better idea to inherit from NSObject)
- give that class (or even an existing one) methods, ivars, and properties
.. and much more
Visit the runtime reference[1] and jump into a running Objective-C app with GDB or F-Script. It's a lot of fun.
It would've been nice to have an 'I don't care, proceed anyway' button. The check excludes Safari 7, which runs the demo just as well as Chrome.
http://jsfiddle.net/bYHfh
^ removes the hasWebGLSupport() invocation.
Very nice demo, though!