4 ms·

Developers evangelized Android and Chrome in their early days - created the monsters. People making Chrome only sites are feeding the monster. Instead of Kozmo

Developers evangelized Android and Chrome in their early days - created the monsters. People making Chrome only sites are feeding the monster. Instead of Kozmos shutting down, the best revenge would making a firefox extension and getting their users to switch.

pedrocx486 6y ago
Or even Edge. Their new Chromium based builds are Chrome compatible and have their own store.
- sb8244 6y ago
  The great thing here is that it is literally 100% compatible with Chrome extensions. I have been working on an extension that uses Chrome's Debugger API, lots of tab / network related APIs, and DevTools. I spun it up on Edge the other day and...it just worked. Everything worked. I can't say the same for firefox. They do a good job bringing over some extension APIs, but I find it severely lacking for my use case.
StavrosK 6y ago
Agreed, why are they shutting down instead of doing that?
- arkh 6y ago
  Not sure there's a lot of Firefox users paying for extensions. especially one which seem to just be a sexier bookmark search.
- livueta 6y ago
  I generally try to avoid bitching about Firefox design decisions in Chrome threads, but possibly because of https://bugzilla.mozilla.org/show_bug.cgi?id=1409675 https://bugzilla.mozilla.org/show_bug.cgi?id=1409675 - the original WebExtensions breaking change removed the ability for newtab-style extensions to do a lot of things their XPI counterparts could, in particular focusing on the address bar after opening a new tab. That bug went WONTFIX with no suggestions for an alternative interface, basically telling extension devs to come up with their own proposal for how to implement it if they want that bit of the API back. I'm not familiar enough with the extension in question to say whether any of those specific issues would have affected it (and from the article it sounds like time was a bigger pressure) but developing newtab-style extensions for Firefox is definitely harder than it should be. While I generally agree with the reasons behind moving away from XPI extensions, it's been really disappointing to see Firefox not be as focused as I'd hoped they'd be on restoring lost extension functionality. That's especially important in the context of Google fuckery like the OP.
superkuh 6y ago
This wouldn't be a problem if browsers weren't walled gardens that are controlled by corporations instead of the users running them. Yes there are security issues with ignorant users doing things. But sometimes the fix causes a problem worse than the original. Firefox and Chrome both don't let users install any add-on without their permission. Switching to Firefox ecosystem just means the leash is longer (and the protection is fake because of their automated signing portal).

pedrocx486 6y ago

Or even Edge. Their new Chromium based builds are Chrome compatible and have their own store.

sb8244 6y ago
The great thing here is that it is literally 100% compatible with Chrome extensions. I have been working on an extension that uses Chrome's Debugger API, lots of tab / network related APIs, and DevTools. I spun it up on Edge the other day and...it just worked. Everything worked. I can't say the same for firefox. They do a good job bringing over some extension APIs, but I find it severely lacking for my use case.

StavrosK 6y ago

Agreed, why are they shutting down instead of doing that?

arkh 6y ago
Not sure there's a lot of Firefox users paying for extensions. especially one which seem to just be a sexier bookmark search.
livueta 6y ago
I generally try to avoid bitching about Firefox design decisions in Chrome threads, but possibly because of https://bugzilla.mozilla.org/show_bug.cgi?id=1409675 https://bugzilla.mozilla.org/show_bug.cgi?id=1409675 - the original WebExtensions breaking change removed the ability for newtab-style extensions to do a lot of things their XPI counterparts could, in particular focusing on the address bar after opening a new tab. That bug went WONTFIX with no suggestions for an alternative interface, basically telling extension devs to come up with their own proposal for how to implement it if they want that bit of the API back. I'm not familiar enough with the extension in question to say whether any of those specific issues would have affected it (and from the article it sounds like time was a bigger pressure) but developing newtab-style extensions for Firefox is definitely harder than it should be. While I generally agree with the reasons behind moving away from XPI extensions, it's been really disappointing to see Firefox not be as focused as I'd hoped they'd be on restoring lost extension functionality. That's especially important in the context of Google fuckery like the OP.

superkuh 6y ago

This wouldn't be a problem if browsers weren't walled gardens that are controlled by corporations instead of the users running them. Yes there are security issues with ignorant users doing things. But sometimes the fix causes a problem worse than the original. Firefox and Chrome both don't let users install any add-on without their permission. Switching to Firefox ecosystem just means the leash is longer (and the protection is fake because of their automated signing portal).