[views_lazy_load] Views Lazy Load

Based on latest issues, we have a first port/ patch of the module done by stborchert. I updated the issue description and hope to find some reviewers for the patch to "get 8.x-1.x out in the wild" ;)

views_lazy_load-8.x-1.x-dev has no D8 standart code and even files` extensions.

Indeed, no surprise there with #2843216: Port to Drupal 8 needing review !
Despite that, Status should be Needs work considering there is a dev release and the port is in progress.

I don't understand what the utility is of putting the Drupal *7* version of the module as the Drupal *8* dev version, and asking people to apply gargantuan patches to turn it into an actual working Drupal 8 module. The Drupal 8 dev module has zero reason to exist in the first place if all it is is Drupal 7 code. If a Drupal 8 dev version is listed, it has zero reason not to reflect the current state of the Drupal 8 patch fully applied (especially considering that patch is now 2-3 years old!), even if it hasn't been "reviewed" and may not be ready for a stable release. Why did anyone ever create this as a "patch" in the first place? That makes no sense to me. I thought that's why dev versions were dev versions? (Do we still use "alpha" versioning in Drupal land?) I mean how is it even a "patch" if like every line of code is completely replaced, plus whole new filenames? This is an invitation for 90% of Drupal developers to throw up their hands and tell their clients "Drupal 8 can't do that and probably won't be able to any time soon," because it's just not worth the time wrestling with this stuff. Building a Drupal site already takes an inordinate amount of time, nobody wants to deal with stuff like this on top of it.

I also might not be so frustrated if this problem of patches to long-standing known bugs languishing in issue queues for YEARS without ever being reflected in the shipping module wasn't so common. Every time someone hesitates to apply these patches to the shipping code (often just a single line change that fixes a WHITE SCREEN OF DEATH or some other serious problem), it wastes THOUSANDS OF HOURS of end developer time. Apparently end developers have all the time in the world to deal with all these problems and patches, and apparently maintainers and contributors have endless time to discuss every issue for years on end, but nobody has time to get these patches into production? Even if the patch doesn't fix everything, or occasionally breaks something else, that's what the process of iteration is about. Sitting in a moribund and forgotten issue queue for years on end does nobody any good, because that known (and patched) bug is still there in every single download, just waiting to waste the time of yet another poor unsuspecting web developer out there, and meanwhile whatever developer worked on the patch has probably forgotten all about it.

Steve Jobs famously said "real artists ship" and I'd like to challenge the Drupal community to start SHIPPING fixes instead of populating issue queues with them. As a web developer I tried to fix problems almost as soon as I discovered them, and most often pushed the fix the same day. At companies like Facebook, developers can famously push code to production all the time, and do. (Not sure of the current state of affairs though.) So this reluctance to apply fixes to production code (ie the shipping module available for download) for years on end mystifies me. I'd be embarrassed as shit if my module shipped with known bugs for years and I never did anything about it. (Or do all these modules really just not have real maintainers any more?)

Just to echo what matthewv789 said 11 MONTH ago guys, I really think you should delete the dev version since it is only D7 code.

If you cant find time to update it then at least don't leave a version up that is broken by design.