[renownedmedia]

I frequently see members of the Firefox, Chrome, and Edge teams at various JavaScript Meetups (in the Bay Area) as well as conferences, though I've yet to meet someone from the Safari team.

Perhaps this is due to the secretive nature of Apple, and as a result I'm always surprised when new Safari features come out. By the time a feature lands in a different browser, we already know it's coming.

[sandstrom]

I wish they would be more flexible with their secrecy. The open-source pieces of Apple (the CLI-stuff in OS X, Safari, etc) would gain much by being less secretive.

(and it wouldn't hinder them from being gold silent on other matters; hardware, business, etc)

[dak1]

WebKit, which is the heart of Safari, is open source: http://webkit.org

I've been tracking many of these issues on the WebKit bug tracker: https://bug.webkit.org

For example: https://bug.webkit.org/show_bug.cgi?id=80559 (Bug 80559 - [ES6] Add support for ES6 Harmony).

The release notes linked to also links to the public commit that implemented each noted fix/update/new feature.

[sandstrom]

I know much of it is open source (darwin is, too).

It's just that they don't engage much and it doesn't feel prioritized.

Take this website for example: http://opensource.apple.com/

The design feels like it's from the early 2000. There is almost no documentation besides the raw data/files.

[alwillis]

Perhaps you noticed that they open sourced their Apple Pay JavaScript code, which was demonstrated a few weeks ago at WWDC: https://developer.apple.com/videos/play/wwdc2016/703/.

[gsnedders]

I expect some of it is just down to comparative size: Apple nowadays have pretty few people working on WebKit (and the JavaScriptCore team is really small—though I doubt V8 people, now mostly in Munich, appear in the Bay Area often!).