That's what I did with uMatrix. It exposes all its parameters and you have to know which ones do what. So I worked it out. Musicians call this woodshedding. Working on fundamentals.
I was thinking more of the uproar over the missed release dates for NoScript than the sudden switch to Firefox 57, though some people seem to think that's a plot too. It's not. It's just a great example of how not to do a rollout of drastically changed code. I actually would have given a B- except for the badly botched API thing, because that means they weren't really ready. So they get a D.
Had the programmer, who has a solid rep in that community, simply said he was working on it, and the fabled version 10.0 would have come when it functioned properly, quite a bit of this kerfuffle might have been avoided. It was all about the whole string of missed release dates. The especially humorous part for me was when everyone was checking their time zone maps to see when it was midnight in Italy, when apparently he would turn into a pumpkin. I didn't do that either. It's 9 hours before L.A.. These are things one learns from doing business back at home from over there.
Can totally imagine that the programmer is working frantically, 'round the clock, to get it done.
It's good to have deadlines, but when it comes to things of this nature, especially an open-source code and radically underpaid venture, the deadlines need to be flexible.
No doubt, this dude is working as hard and as fast as he possibly can on this project. I'd say that folks should lighten up and give him some room to operate.
In the end, this bit of software is likely to be as good and probably better than anything else that exists, which is pretty much par for the course for Mozilla products.