creesch

34 ms·

421.
by creesch 4y ago
> I don't see why so many people are against Mozilla using donations how they see fit. They need to diversify because relying on a single project, a free browser, in a single market segment which is saturated with free browsers, is
422.
by creesch 4y ago
I really think it depends on the complexity of the extension and how much it leverages the background page. > Background-workers instead of background-pages makes for a more consistent API. IMO background-pages were always weird. True, b
423.
by creesch 4y ago
Simple, they switched to the webextension API a few years ago as it makes development of extension across browsers much easier. More directly put, developers would develop extensions for Chrome and more often than not would not bother with
424.
by creesch 4y ago
To be frank, I think you are now overselling a product where it really doesn't need to be sold as much as it already has a lot of value in itself. E2E tests deserve better tooling to debug them, not because they are flaky, but because
425.
by creesch 4y ago
While what you have made looks cool it seems like you are leaving out a lot of what is at the basis of many hard to maintain flaky e2e tests: a fundamental wrong approach to testing resulting in too many tests in the development process whe
426.
by creesch 5y ago
Except that it isn't really, the protocol from what I gather is very convoluted which is seen in the amount of mature featured client and server implementations for it. It also doesn't solve some of the problems that got in the w