I wonder if there's anyone here from SauceLabs or or any other company that does browser automation as a service -- was this easy to see coming? Is everything pants-on-fire there at the moment?
Sauce Labs donated Selenium Builder (nee Sauce Builder) to the project to try and help. Applitools have recently leant some engineering muscle to the problem. The problem breaks down into two main areas:
* Technical: the underpinnings have switched from the XPI model to Web Components. Mozilla are doing what they think is best for their browser, and I know that they make their choices with thought and data.
* People: every successful OSS project has a company or person acting as its champion. The selenium project has people working flat out for the language bindings, the w3c "WebDriver" spec, grid, and supporting the community. We lack a champion with the time to spend on IDE.
We can fix the technical side of things. The thing that we could really do help with is the people-side....
Always curious how moves like this help people who are actually doing stuff in the browser automation/testing scene (I am just a trend follower/leech off the work being done), glad to hear you guys were ready and props on thinking ahead.
[X] created by a company that can't be trusted
[X] made mandatory by lazy devs && corporate bean counters who refuse to let other developers do the professional thing and make stuff work cross platform
[X] worse than the alternatives in many ways except being feature-by-feature and bug-by-bug compatible with the market leaders (yep: memory use, battery use, extensions)