[SuperSU] Chainfire:
Well there's a few considerations here. First is that many root devs are using custom ROMs like CM and are thus primarily exposed to Superuser, not SuperSU. This while I think the average root end-user is more likely to run SuperSU.

I think a similar divide will occur with L, as SuperSU will try to break SELinux only as little as absolutely needed, while various ROM and kernel releasers (and even tech-savvy end-users) will simply switch SELinux to permissive. Security vs convenience. It is better security wise to not break all the security (sounds obvious), but it's a lot easier for root app devs as they won't have to deal with figuring out these SELinux quirks. A lot of users will actually want that as well, because more apps will work without their devs having to fix them up first.

I'm not sure how or why SuperSU broke Fahrbot's app, but it sounds like an odd workaround. Like he needs to run as init_shell or something to get some commands to work (not all that strange by itself). He's going to have a bad time if that is the case, as the init_shell context is being removed for L final, most likely. If that is the case, he needs to address the actual problem, instead of wrapping his commands in another shell call. But I'm just throwing random words out there, because I don't know what the issue is, or if your comment accurately describes the fix he implemented.

That's one odd thing though. People are really bad at properly reporting things. Devs will complain in their changelogs or their G+ about some change breaking something for them, but they never bother actually reporting it to me. Users post new and interesting issues on vague websites rather than here where I will actually read/find them. It's not just SuperSU, it's with all apps.

As an example, take my beta releases. I track the downloads and installs, and many of them reach into the hundreds of thousands of installs before the next (beta) release is out. And they will have glaring issues with popup boxes and crashes and slowdowns and chainsaw massacres and explosions, and even if a thousand of them experience the issue, I'd be lucky if more than three people actually report it, and if one of those will actually assist in tracking down the issue. That is, unless you count 1-starring the app on Play as giving feedback. Of course, I do not have the time to track down every single little thing in the order it comes in, and some tiny things may take ages to be addressed (if ever). But most big things I like to keep fixed.

Back to the devs though. With things like the new security issues, I do not think it is odd they are actually waiting before porting. L retail will be out very soon, and there have been so many changes the past year of which most are not really relevant at all to 4.x devices, only full AOSP builds and upcoming L, that it would not be very efficient use of their time to continuously keep up with these things. I do, but I have to. But look at my other apps - due to all this development and getting stuff fixed in SuperSU, many of my other apps are way overdue for their own updates. I've even pulled half a dozen from the Play store a few weeks ago because of this, maybe with more to follow.

Long story short, I'm not surprised many root app devs are waiting around a bit to see what's going to happen with retail L before investing more time on getting up to speed. Don't blame 'em. And people are odd. The end :)

Take into account for this rant that it is past midnight, and I've had some wine (hurrah).