in reply to On moving forward and breaking compatibility

I'm sure this node will be referred to many times, as SOPW nodes come in about Mech not working, so its good.

My thoughts on this are 2.

First, html has been changing so fast, with all this javascript and flash, that I wouldn't expect any script older than a year to actually work. Just look at the history of the attempts at YouTube video downloader scripts. Each attempt works for awhile, until some invisible smart guy upstairs figures out a way to defeat the scripts, to force you to use a browser to get the video. Why? So they can force you to view their ads. I still don't think anyone has found a way to reliably trigger the little flash cws file, which they now send you as a loader for the real video, containing a well hidden, dynamic url. I wonder how Gtk2::Webkit::Mechanize handles it?, since it has a browser built-in.

Second, always check the examples that come with new modules, for the skeletons of your new programs.

So things are moving fast forward right now, and we the scripters need to stay agile.... not locked into old methods good 5 or 10 years ago.


I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku
  • Comment on Re: On moving forward and breaking compatibility

Replies are listed 'Best First'.
Re^2: On moving forward and breaking compatibility
by Corion (Patriarch) on Feb 10, 2010 at 11:28 UTC

    Note that the change to WWW::Mechanize happened 18 months ago:

    1.49_01 Sat Sep 27 23:50:04 CDT 2008

    ... and I think, it went mostly without problems, or was shadowed by larger problems due to LWP changing its callback infrastructure :).

Re^2: On moving forward and breaking compatibility
by Anonymous Monk on Feb 10, 2010 at 11:18 UTC
    They probably execute the flash ... I heard the xbmc folks do that as well (for hulu and such)