Gregory's Server@strangeculprits @kevinrns @Pineywoozle How is a fork that doesn't do any engine work going to continue when the upstream goes away?
|
7 comments
@strangeculprits @kevinrns @Pineywoozle I don't understand how you think this is an alternative if you think that Mozilla may not continue to exist. It's not like this browser has any real marketshare, any way of monetizing itself (in order to hire people), or even a significant contributor base. Are you comfortable saying "use it for as long as it lasts, and don't think about whether using this actually hurts the upstream"? Because I don't really see how Floorp can replace what Mozilla does. @strangeculprits @kevinrns @Pineywoozle I'm pretty doubtful of your third point -- the support given to Gecko *today* is minuscule - why would organizations attempt to replace Google's revenue entirely, rather than contributing to Chromium or WebKit on the margins? What is more likely -- that developers will gravitate towards forking or contributing to a fully funded codebase with paid developers, or one that has no upstream and will quickly experience user flight? @strangeculprits @kevinrns @Pineywoozle I have no idea what your Twitter comment meant - Firefox *is* the alternative that has paid labor. Floorp is cool, but a developer working on the margins isn't going to keep Gecko going if the upstream dies. Where does your belief come from? Do you have any evidence to support it? For example, Igalia and Microsoft have contributed to Chromium. Google has contributed to WebKit and developed Blink. Where is the extensive outside work coming to for Gecko?  @yoasif @strangeculprits @kevinrns Hello, this thread has officially exceeded by my competency level and my interest.😜 Could you drop me? |
@yoasif @kevinrns @Pineywoozle
Probably a better question for the devs, we were just offering an alternative for those who didn't know about Floorp or the financial realities of Mozilla.
We presume you understand the risk to Mozilla, given your statement "when the upstream goes away."
We don't know who or whether the FF code base would be maintained if Mozilla goes away, though we are cautiously optimistic that FOSS true believers with the requisite technical skills will step into the breach -- either by maintaining the code, or by making the next thing.
We'd be cool with just using Qutebrowser, but then we're weird that way... Not everybody wants to use a keyboard-based web browser :vim:
@yoasif @kevinrns @Pineywoozle
Probably a better question for the devs, we were just offering an alternative for those who didn't know about Floorp or the financial realities of Mozilla.
We presume you understand the risk to Mozilla, given your statement "when the upstream goes away."
We don't know who or whether the FF code base would be maintained if Mozilla goes away, though we are cautiously optimistic that FOSS true believers with the requisite technical skills will step into the breach -- either...