News for hackers. Stuff that matters.
Re:Let’s Write a Firefox Web Extension by javajosh on Tuesday September 22, 2015 @12:16AM (#10256600)
Oh come now, that's not fair. Sure XUL can't be the key to a good extension mechanism. If devs stop writing (or choose not to port) it's because of the economics of Firefox extensions, which is to say, there are no economics to writing Firefox extensions. Except some minor reputation points and feel-good points. (The exception, of course, being those add-ons that make a SaaS more usable.)

Out of curiosity, if there was a Firefox App Store, how much would you pay for Tree Style Tabs?

Re:Let’s Write a Firefox Web Extension by Illniyar on Tuesday September 22, 2015 @01:09AM (#10256728)
From what I understand its not for lack of commitment that these extensions arent porting, its because XUL had basically the ability to run native code and modify everything. That is the new web extension api does not replicate all the features of XUL (by design).

Look at the sorry state that is Tree Style Tabs clone in chrome - which is because Chrome's extension api is just not powerful enough.

Re:Let’s Write a Firefox Web Extension by Springtime on Tuesday September 22, 2015 @01:12AM (#10256739)
For those interested the relevant previous HN discussion on this: https://news.ycombinator.com/item?id=10097630
Re:Let’s Write a Firefox Web Extension by mafuyu on Tuesday September 22, 2015 @12:55AM (#10256679)
I would pay a significant amount of money for pentadactyl + Tree Style Tabs that just worked, without bugs. It's a significant part of my workflow, and I'm not sure if either will survive XUL deprecation. :(
Re:Let’s Write a Firefox Web Extension by silon7 on Tuesday September 22, 2015 @03:51AM (#10257221)
FF will be forked if that happens (also for classic theme restore, and others).
Re:Let’s Write a Firefox Web Extension by eloisant on Tuesday September 22, 2015 @06:10AM (#10257650)
It's not about XUL, it's about having no limit on what you can do to the browser.

Old-school extensions can change entire parts of the browser, remove features, there really is no limit because the extension code is dumped inside the browser code without any kind of interface or security limitation. So it's powerful, but potentially destructive as a bug in an extension can impact the whole browser, and same goes for performances.

On the other hand, the new API is more like Chrome where you have defined entry points to plug your extension.

The new API approach has limitations, but it's a much better way to do extensions. Not only it limits the damage a poorly written extension can do, but it will make extensions more robust to version upgrades of Firefox.

Re:Let’s Write a Firefox Web Extension by yellowapple on Tuesday September 22, 2015 @12:19AM (#10256603)
> Out of curiosity, if there was a Firefox App Store, how much would you pay for Tree Style Tabs?

Probably a few bucks. TST is pretty fundamental to my Firefox workflow.

Re:Let’s Write a Firefox Web Extension by Qantourisc on Tuesday September 22, 2015 @03:27AM (#10257125)
Well according to Mozilla TST has 100 000 users. At a few bucks that's 300 000$ I suppose that could be enough :) With that money you can even maintain a separate Firefox patch-set to allow the plugin to work.
Re:Let’s Write a Firefox Web Extension by Mindless2112 on Tuesday September 22, 2015 @02:03AM (#10256880)
> there are no economics to writing Firefox extensions.

The same could be said of most free software. But see [1].

> Out of curiosity, if there was a Firefox App Store, how much would you pay for Tree Style Tabs?

I don't know. I keep dozens of tabs of reference materials open at work, which becomes unmanageable without it. I'd either pay for it, find a new way to work, or build my own.

[1] http://www.gnu.org/philosophy/motivation.html

Re:Let’s Write a Firefox Web Extension by javajosh on Tuesday September 22, 2015 @03:17AM (#10257093)
Apropos of nothing it occurs to me that one way to make it lucrative to build totally open and freely distributed software is to invent a caustic software environment. E.g. keep changing the hardware and software dependencies so that anything you did build and give away has to be built again. And again and again.

That's one way to make a living from software in the long term, but it sure does seem wasteful. And if the technology truly hits an asymptote, then it's not clear what will drive the decay apart from programmer self-interest.