Home RSS [oo]<

Musings of a Madman

Why the title?  It all started with a chance meeting, and the opportunity to help a stranger and a response that left me feeling the need to write about it.

Full index

Article: 20140818 (Mon, 18-Aug-2014, 20:41)

Share on Facebook
Web site "developers" ... who can't.

Java clue?

Possibly repeating a rant of old

It's incredible how much sites are relying using Javascript to get your browser to do their work these days.  It's astounding the sheer quantity of this crap your machine is having to process just to assemble what should be a simple web page, for things like Facebook, Google, YouTube; in fact pretty much every major site around these days.  But what is truly shocking is just how much of it is appallingly broken code.  I'm sitting watching the errors (that users do not normally see) streaming up the console as I simply reload a Facebook page, watch a YouTube video, or post a Tweet.

[Warning: nerdy bit.] I'm not just seeing simple unimportant unassigned values.  These are user functions which return inconsistent values and cause errors to be thrown.  Or clear syntactic errors which the interpreter is doing it's best to second-guess and correct.  By the look of it, these days even run-testing your own code is considered a step too far and the words "Quality Assurance" don't belong in polite society.

Case in point (and this is just a tiny fragment from one Facebook page update):

JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yj/r/mmNmKx1moAp.js, line 45: anonymous function does not always return a value
JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yj/r/mmNmKx1moAp.js, line 20: reference to undefined property this.props.staticNotifs
JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yA/r/Xh9cjdeWTbX.js, line 43: reference to undefined property this.props.className
JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yj/r/mmNmKx1moAp.js, line 44: reference to undefined property v.lazyonload
JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yr/r/4cZTaNjKJZz.js, line 28: function q does not always return a value
JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yr/r/4cZTaNjKJZz.js, line 31: anonymous function does not always return a value
JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yr/r/4cZTaNjKJZz.js, line 31: anonymous function does not always return a value
JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yr/r/4cZTaNjKJZz.js, line 31: anonymous function does not always return a value
JavaScript strict warning: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yH/r/SYVvo2JqLOp.js, line 17: reference to undefined property this._deferredTransition

If you ever wondered why some pages seem to take a glacial age to finish loading, or some just get terminally stuck, odds are it's the fault of some crap second-rate programming by a clueless monkey.  It looks like some of these "developers" couldn't even complete a newbie's assignment.  I don't write JavaScript, as a rule, and even I could fix some of this shit.