Live data from Hacker News

Google and Mozilla are failing to support browser extension developers

armin.dev

171–180 of 195 posts

Re: Google and Mozilla are failing to support browser extension developers

#171

Earlier quoted context omitted.

Firefox has a task manager now. They should improve on this to compete with Googles. Nobody wants to type a URL when they can hit an easy shortcut.

I have a hope of remembering about:performance. I can bookmark it, and it's there in autocomplete. You can make a link to it in your webpage or in a nice plugin (which, once it gets a couple thousand users, you can sell to an honest businessman for tens of thousands). Shift-Escape? what? I'm supposed to just randomly press every key combination till something happens?

Why not both (if the shortcut is available)?

Re: Google and Mozilla are failing to support browser extension developers

#172
post #80
post #13

On the one hand, this seems like a real missed opportunity by Mozilla. As Chrome reigns in extensions that conflict with Google's business model, this is a reason to use Firefox. BUT - extensions are also often the cause of a slow and frustrating Firefox experience, which then leads folks to talk about how Chrome is better-performing/faster (I've been guilty of this myself in the past). Mozilla needs to make sure Fir…

> extensions are also often the cause of a slow and frustrating Firefox experience You have any recent data on this? I am not convinced this is true anymore.

This used to be a problem with legacy extensions because their APIs pre-dated the multi-process effort and forced Firefox into single-process mode.

In over a year of using Firefox every day I haven't noticed any slowdowns after Firefox made the move to drop compatibility for those extensions.

Re: Google and Mozilla are failing to support browser extension developers

#173
post #20

>The Chrome Web Store and the Microsoft Store do not offer features for supporting extension developers. That doesn't seem right - doesn't Google let developers monetize extensions in the chrome web store? You can publish Hosted Apps, Chrome Apps, Chrome Extensions, and Themes in the Chrome Web Store. Collectively these are called simply "Items". You have many choices when it comes to making money from items that you…

The web store ecosystem is atrocious. You cannot rely on Google's browser services to make money. They will randomly take down your extension for a ~month in response to malformed (i.e. invalid and illegal) DMCA notices, and they barely maintain the developer tools - I've watched key parts of the developer dashboard break and go unfixed for months even after reporting them. If you want to do this stuff you have to do…

I've developed apps for Chromeos which share a lot of the same docs as extensions and these are some of the worst docs I've ever used. Incomplete, outdated, confusing, etc.

It feels as if Google doesn't want you to actually make Chromeos apps.

Re: Google and Mozilla are failing to support browser extension developers

#174
post #44

> It is a regular occurrence to hear about open source developers selling their browser extensions, only for their users to be exploited later on by the new owners. ... We are witnessing the failure of browser vendors to recognize the value of our labor and the important role it plays in a healthy browser ecosystem. So this is an interesting philosophical question - the market value of the extension is the value of "…

> Those point to wildly undervalued and wildly overvalued estimates of the fair market value of the developers' work. Hrm. I would say that it indicates that there are two different types of market. There is the market for free, ethical extensions. This market is full of products that have no value, either being freely given away by their author, or having insufficient reach or utility to garner commercial success. T…

What about donation models? They aren't lucrative or dependable but they technically can make money - still hard of course.

Re: Google and Mozilla are failing to support browser extension developers

#175

Earlier quoted context omitted.

Your extensions are listed along with their resource usage in about:performance !

There’s a real discoverability issue with those kind of pages. They should be listed somewhere in some submenu. You can’t expect people to go through all the documentation like they used to go through manuals in decades past.

Chrome has about:about at least

Re: Google and Mozilla are failing to support browser extension developers

#176
post #44

> It is a regular occurrence to hear about open source developers selling their browser extensions, only for their users to be exploited later on by the new owners. ... We are witnessing the failure of browser vendors to recognize the value of our labor and the important role it plays in a healthy browser ecosystem. So this is an interesting philosophical question - the market value of the extension is the value of "…

$10K’s doesn’t “wildly overvalue” the developer time that goes into a successful browser extension.

At almost $200k/year, a starting google developer makes ~$4K a week (pre tax, but also ignoring health care, facilities, etc).

The browser extension offers are comparable to months of developer time, but since they are made after an extension succeeds, they’re not accounting for the probability that a new extension won’t become wildly popular.

Put another way, if the scammers could develop (or steal) extensions for less than they’re buying them for, I’m sure they would.

Re: Google and Mozilla are failing to support browser extension developers

#177

Earlier quoted context omitted.

I’m the author of JSON Formatter [1] with 989,000 users. I probably get a couple of offers a year for it. Of those that have offered specific sums, they ranged from from $10-20k. I always reject them, because it’s pretty obvious they want to turn it into malware. I’ve had a couple of cases where I felt they went to some effort to schmooze me first, presenting themselves as having benign intentions, almost like a care…

$20k seems like a pretty lowball offer? Close to 1M users (plus potential for further growth) and you have me expecting at least $400k... Or, am I expecting too much?

how do you suggest to make those 400k back in any reasonable amount of time?

Re: Google and Mozilla are failing to support browser extension developers

#178
post #164

Earlier quoted context omitted.

$20k seems like a pretty lowball offer? Close to 1M users (plus potential for further growth) and you have me expecting at least $400k... Or, am I expecting too much?

There isn't potential for further growth if it gets bought. They just want to serve malware to the existing userbase.

That is still $0.02 per user. Not a bad deal.

Re: Google and Mozilla are failing to support browser extension developers

#179
post #74

Earlier quoted context omitted.

I work for Google, opinions are my own. > Sorry to all Googlers here for being so blunt, and feel free to point out one or more examples from the last few years where Google has prioritized their users above quarterly / yearly profits. No need to apologize =] An example that comes to mind is the current focus on accessibility. I think from an objective financial/engineering perspective, it's much preferable to just i…

I'm curious. What specifically would you like to see removed from Chrome?

To be honest I don't know too much about what's been added but I can only assume new functionality must account for the increased bloat.

I imagine it's support for things like "Chrome Apps" or more generally the desire to get websites to be able to do the same things as native apps. I suspect there's also the fact that Chrome has to support Chrome OS as well.

But I am new to Chrome OS so admittedly I am not too familiar on the history or background =]

Re: Google and Mozilla are failing to support browser extension developers

#180
post #144
post #117

Earlier quoted context omitted.

The root cause of all this is autoupdating. I hope we will eventually move away from that paradigm. But currently its needed, since lack of updates is even less secure.

We will get away from auto updating and security issues once we have a feature complete browser and a stable HTML specification. Given past trends I would expect this no earlier than the heat death of the universe.

The crash of Western Civilisation may suffice.

Unless we've created self-replicating, web-enabled, grey goo first.

Post reply on HN