Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I cannot continue working on my add-ons

fasezero.com

Post reply on HN
Print view View original

211–218 of 218 posts

Re: I cannot continue working on my add-ons

#211

Post by affected »

Tree Style Tabs is a true differentiator for Firefox and it is a perfect expression of Mozzilla Mission: https://www.mozilla.org/en-US/mission/ "Our mission is to ensure the Internet is a global public resource, open and accessible to all. An Internet that truly puts people first, where individuals can shape their own experience and are empowered, safe and independent."

Seeing Tree Style Tabs continuity halted and more importantly a developper motivation deeply affected is not a good sign for the community and users who engaged with Mozzilla's goals and with its addon community.

Tree Style Tabs empowers the user browsing activity at a level rarely seen. It brings to awareness constant history (tab tree) and allows the user to mature its browsing profile with structure.

An deeply thought addon that really shapes the browser into a navigation tool that empowers its users and allows building more mature browsing focus and improves the individual's independence.

Mozilla should review carefully the resulting loss of differentiating value by letting a valued and committed add-on developper go and how this diffuse into impacting its mission.

Re: I cannot continue working on my add-ons

#212

Post by BrendanEich »

chr1 wrote: post #210
BrendanEich wrote: post #194

Earlier quoted context omitted.

No need to fork Brave, we will collaborate on extensions APIs as we scale. We're supporting tested chromium extensions that we curate and fetch from our own S3 (essentially a cache backed by the Chrome Web Store). For an extension to get support, we need to rank it as in-demand, and then try adding it to Brave to see what missing chrome.* APIs it might need. https://twitter.com/bravesampson is leading this charge, us…

Great to hear you are interested in colaborating on this issues. muon and react based ui is exactly why i was suggesting to use brave as a base for experimentation. I was not talking about the type of extension that allow to do some common things based on small api created specifically for that. I am more interested in extensions that get full access to existing react components, and can modify the browser ui in arbi…

I was chief architect of Mozilla back in the 1998 October roadmap period and onward, when we created XUL. Indeed we wanted powerful extensions, and got them. Problem is they tied Mozilla down for too long, without anyone stepping up to find a way forward that didn't just seem to signal "XUL going away... . Oh never mind; or maybe later".

Brave UX will evolve but slowly and without big changes that break too many users (Australis). Still, we need to be able to change our UX. So if we have powerful extension APIs into that UX, we can't promise never to break extensions that use those APIs in ways that become unsupportable.

All we can do is try to co-evolve nicely and cooperate better. I don't see a silver bullet here, but I do see how Mozilla has burned a lot of add-on developer good will -- and we won't make that mistake at Brave.

Re: I cannot continue working on my add-ons

#213

Post by [deleted] »

chr1 wrote: post #210
BrendanEich wrote: post #194

Earlier quoted context omitted.

No need to fork Brave, we will collaborate on extensions APIs as we scale. We're supporting tested chromium extensions that we curate and fetch from our own S3 (essentially a cache backed by the Chrome Web Store). For an extension to get support, we need to rank it as in-demand, and then try adding it to Brave to see what missing chrome.* APIs it might need. https://twitter.com/bravesampson is leading this charge, us…

Great to hear you are interested in colaborating on this issues. muon and react based ui is exactly why i was suggesting to use brave as a base for experimentation. I was not talking about the type of extension that allow to do some common things based on small api created specifically for that. I am more interested in extensions that get full access to existing react components, and can modify the browser ui in arbi…

[deleted]

Re: I cannot continue working on my add-ons

#214

Post by BrendanEich »

otabdeveloper wrote: post #127
thezilch wrote: post #108

Earlier quoted context omitted.

Most or all stats will show mobile FF browsing usage at about IE6 levels, and I don't think you'll find anyone caring much for the later market any longer. We [web developers] owe a lot to FF, Firebug, etc, but the writings on the wall for mobile and desktop. Chrome is going to have to screw up really bad, and likewise for the base installs of IE/Edge and Safari. These days, I'm more likely to suggest Brave over FF,…

> These days, I'm more likely to suggest Brave over FF, if someone really requires a Chrome alternative. Brave is just a reskinned Chrome. > We [web developers] owe a lot to FF, Firebug, etc, but the writings on the wall for mobile and desktop. Where I work developers have mostly switched to Firefox over the last few years. Firefox is just a better browser (faster, less bloated) under the hood. Yes, Firefox will have…

> Brave is just a reskinned Chrome.

No, see https://news.ycombinator.com/item?id=13534564.

Re: I cannot continue working on my add-ons

#215

Post by ngokevin »

syshum wrote: post #185
ngokevin wrote: post #152

Earlier quoted context omitted.

That's not the point. There's a poison pill in the contract. Mozilla can walk out of the existing contract, get all of the money in lump sum, and sign with another search partner (while still being paid by Verizon). There are other search engines waiting in line, Mozilla's not married to Verizon.

>>There are other search engines waiting in line, Mozilla's not married to Verizon. Who?? I know of none MS will never support Firefox, They want people to use Edge. DuckDuckGo do not have the cash to do it. Google has the market share and does not need FF anymore that is why they dropped them So Who.... >>That's not the point. Actually it is the point, by 2020 Mozilla's IMO mozilla revenue stream will dry up, they n…

Search competition is different from browser competition that mainstream media likes to hype up. A few hundred million for 10-15% of the search market is nothing, Bing and Google would gladly offer a bit of money. There are also partners around with world (Yandex, Baidu).

Re: I cannot continue working on my add-ons

#216

Post by ngokevin »

syshum wrote: post #181
ngokevin wrote: post #151

Earlier quoted context omitted.

https://testpilot.firefox.com/experiments/tab-center/

this link keeps posting this link 1. No that is not a Replacement for TreeStyle Tabs, far from it 2. It uses XUL as well and will be killed in 57 unless new API;s are made this link is not the solution to the Extensions problem we are complaining about

The OP asked for:

> If Firefox included vertical side tabs...

Re: I cannot continue working on my add-ons

#217

Post by PeCaN »

ngokevin wrote: post #216
syshum wrote: post #181

Earlier quoted context omitted.

this link keeps posting this link 1. No that is not a Replacement for TreeStyle Tabs, far from it 2. It uses XUL as well and will be killed in 57 unless new API;s are made this link is not the solution to the Extensions problem we are complaining about

The OP asked for: > If Firefox included vertical side tabs...

> > If Firefox included vertical side tabs...

> […] as it went pseudo-Chrome-mode

The problem is Firefox is killing that and other addons as it goes pseudo-Chrome-mode.

Post reply on HN