remotesynth

I didn't cover that because I think the criteria changes depending on your role and the type of company you work for. For instance, when I was at a large financial company, it needed to be something that was well established, with solid documentation and with professional support options (so, often this was something along the lines of professional open source). When I was with a consulting company, I was much more open to new frameworks as I might encounter clients using them or they might be suitable for some project.

When I am compiling my weekly update, it ends up being something that appears to have at least some decent documentation and the description sounds both useful and makes sense (you won't believe how many libraries/frameworks I come across that I simply have no idea what they actually do or how they are different).

Anyway, all that is to say, I don't know that there is one set of criteria that works for everyone and it is subjective anyway. Sorry if that sounds like a cop out.

I don't think I am saying this is a bad thing either. However many people find it overwhelming causing them to react negatively. My goal was, in fact, to turn it into a good thing by helping with strategies to cope.

I've looked into what it would take just to dump jQuery for DOM traversal and manipulation. It can be done in plain JS, but you end up rewriting a lot of methods to fill in the gaps already filled by jQuery. My conclusion was, it's still easier and more productive to use jQuery.

Thanks! I wasn't aware of those.

If those were the only choices that need to be made, then perhaps it would be easy.

Great point. I added a link to the project page at the beginning of the article and a link to the downloads at the end.

Site is back up. Sorry for the issues. Had to throw a ton of resources at it due to the traffic surge.

Site is back up. Sorry about the issues.

Sorry. We have two articles that made the Hacker News home page and it is more than my server can handle. It's back up now.

The author of this library wrote an article about how it was built with some new demos at http://flippinawesome.org/2013/09/23/creating-a-realistic-ra...

Sorry. Traffic spike took down the site temporarily...coming back up now.

I've looked into this internally and here is the official response from the security team:

While Adobe did resolve the vulnerabilities addressed in the security bulletin you are referencing below (APSB12-11) in the Adobe Photoshop CS6 major release, no dot release was scheduled or released for Adobe Photoshop CS5 or CS5.5. In looking at all aspects, including the vulnerabilities themselves and the threat landscape, the team did not believe the real-world risk to customers warranted an out-of-band release for the CS5 and CS5.5 versions to resolve these issues. The security bulletin for Photoshop is rated as a Priority 3 update, indicating that it is a product that has historically not been a target for attackers, and in this case we are not aware of any exploits targeting any of the issues fixed. Installation of the upgrade is therefore at the user’s/administrator’s discretion.

I have sent some emails internally at Adobe to clarify the message here and hopefully this will be addressed soon. The bulletin notes a security update to CS5.5 and earlier versions as well as this issue being resolved in CS6. I suspect that it is really a matter of poor wording within the bulletin but, as this isn't my area of expertise within the company, I am trying to confirm.