Roi Danton
2009-11-19, 12:50:50
Ein JavaScript Programmierer hat sich kritisch gegenüber einer neuen JS-Bibliothek seitens Google ausgesprochen, da die Entwickler zu viele Dinge direkt von Java auf Javascript übertragen. Im Gegenzug hat er etwa jQuery gelobt.
Google Closure: How to not write Javascript (mit vielen Beispielen zu den Gründen) (http://www.sitepoint.com/blogs/2009/11/12/google-closure-how-not-to-write-javascript/)
Motivation für den Artikel wird unten erwähnt:
Google’s Responsibility to Code Quality
By this point I hope you’re convinced that Closure Library is not a shining example of the best JavaScript code the Web has to offer. If you’re looking for that, might I recommend more established players like jQuery (http://jquery.com/)?
But you might be thinking “So what? Google can release crappy code if it wants to—nobody’s forcing you to use it.” And if this were a personal project released by some googler on the side under his or her own name, I’d agree with you, but Google has endorsed Closure Library by stamping it with the Google brand.
The truth is, developers will switch to Closure because it bears the Google name, and that’s the real tragedy here. Like it or not, Google is a trusted name in the development community, and it has a responsibility to that community to do a little homework before deciding a library like Closure deserves public exposure.
Google Closure: How to not write Javascript (mit vielen Beispielen zu den Gründen) (http://www.sitepoint.com/blogs/2009/11/12/google-closure-how-not-to-write-javascript/)
Motivation für den Artikel wird unten erwähnt:
Google’s Responsibility to Code Quality
By this point I hope you’re convinced that Closure Library is not a shining example of the best JavaScript code the Web has to offer. If you’re looking for that, might I recommend more established players like jQuery (http://jquery.com/)?
But you might be thinking “So what? Google can release crappy code if it wants to—nobody’s forcing you to use it.” And if this were a personal project released by some googler on the side under his or her own name, I’d agree with you, but Google has endorsed Closure Library by stamping it with the Google brand.
The truth is, developers will switch to Closure because it bears the Google name, and that’s the real tragedy here. Like it or not, Google is a trusted name in the development community, and it has a responsibility to that community to do a little homework before deciding a library like Closure deserves public exposure.