I did one myself for a while (before people dropping out whittled it down to me writing 15 articles in a weekend - I was just meant to be the designer/developer!);

http://www.plaaayed.com/issue/march-2016/

PC / Win 10 / 64-bit. I'm stuck on the ESR release verison of FF at work, but it might be something else specific to me. I'll look again when I'm at home.

Really nice, but your homepage scroll effect is completely broken for me in FireFox 45.7.0 - it has some weird rendering artifacts (white boxes everywhere), and even breaks the scrollbar!

+1 for the ascii art name in the source though. =]

For renaming? There's no default set on Windows for renaming layers, never has been, from what I can remember...

Very slick - love it when games have this level of craft spent on menus.

As an aside, I love the logo - whoever twigged that 'Climb' fit in to a mountain shape is a genius...

'bg' for 'background' is a standard, but apart from that I'm a bit of a layer name OCD-er, and the best thing I've ever done to keep it in check is to change one of the shortcuts; Ctrl-R now renames a layer, rather than toggling the rulers (because who uses them?). It's the first tip I share with any other designer, and changed my life. Also, you can use emoji in layer names, so [ghost][poop] (DN won't show the real emoji) is valid too...

Bitbucket offers unlimited public and private repos, it's just the number of users is limited to 5. I'm up to 7 repos so far and haven't paid a dime...

The DestroyToday Twitter app was awesome, and I miss it every day (being a Windows user). If Twitter ever revert their anti-developer stance, can we get an updated version, or is it dead to you?

One of the images is a 3.4MB .png when I load the homepage. That's... unexpected. Given the market widget is an internal DN thing, you'd hope they can fix it fairly easily (though the market homepage itself is an incredible 29MB currently). Someone needs a slap on the wrist with a web performance textbook...

Really nice - will certainly replace waypoints for me where only simple reveal stuff is required.

It would be nice if you could chain siblings together, rather than explicitly referencing them, though. Something like;

sr.reveal('.foo').each('.child);