I wish they included the right way to do the stuff. <i>Then</i> it would be fun and useful too, and that would be a great way to teach best practices and coding techniques.
From the readme file on GitHub.<p><i>If you're someone that runs an enterprise-level website (>100 hits per day), you've probably had to deal with the pains of scaling and maintaining your code.<p>Enterprises have dealt with these problems for years -- this is an attempt at gathering all of that knowledge and to share it with the world.</i><p>The sarcasm is so think I can almost taste it.
I'm bothered that when I saw the code on <a href="http://enterprise-html.com" rel="nofollow">http://enterprise-html.com</a> for rounded corners, the first thing I thought was "You forget to set cell spacing, padding, and borders..."
The text is so huge and stretched that it is hard to read. The code is so small and uses such a bad colour scheme that I often cannot read it.<p>Your CSS3 is "using every feature available because you can"?
I spent a summer interning at a large financial data company, and I was surprised to see javascript was used quite a bit internally, so I can attest that "enterprise javascript" really does exist.<p>My coworkers wrote very good code, however the quality of my JS was terrible. Of course. I only knew C++ and Java at the time, so I treated javascript like it was "Java without types"
I realize things are a little different in JS, but when you're working on a massive product with a small team, no matter how great the code is, eventually you learn that the variables DO have to be descriptive and properly organized namespaces ARE very important.<p>Many of these conventions evolved, in my opinion, because it's difficult to create large applications, period. No matter how much effort you put into abstracting everything and modularizing components into smaller components.<p>Anyway, these were the only ones that I thought were a little out of place.
I really hope the recommended method of suggesting tips (fork, modify, pull request) and the overcomplicated backend (complete with four dependencies!) is an attempt at meta-humor. Maybe we need an opensource-js.com.