Is heavy office work possible on a smartphone? No. Why? Because they shifted to Android or wrote: At least at work this simply is not possible. Many haven’t bothered replacing their old XP boxes. But look around, most people are using phones for their information consumption. We intermix ourselves with like minded tech consumers, so you and I see Windows as important or still important. How many people do you know who use their smartphone as their main device?] I think it’s crucial to these stakeholders that it at least appear that Mozilla is not just letting its userbase sail over to wrote: When it comes to the desktop ever being fully replaced, I don’t think so. Now I understand that Mozilla doesn’t have public shareholders, but they must have financial stakeholders who deem the future of Firefox as important. They may have failed, but they needed to be seen as trying. Shareholders needed reassurance that Microsoft was able to play in that mobile space, and not be lost in desktop antiquity. Oh I also believe that Mozilla will sink, but it’s like Microsoft having tried taking on Apple and Google, albeit late to the game with Windows 8 and 10. But other comments buried your responses, so I’ll respond here (if that’s wrote: Competing with Google is not within …… scope unfortunately, save David vs Goliath scenarios.] Hi wanted to respond to some of your comments from a post below (and you did take some time to write them, so I wanted to give you an equally thought-out response to a few key points you made).
Second, because it would have been better if Mozilla would make exemptions for forks of existing add-ons at the very least that fix things.
While I can understand Mozilla's reasoning for blocking new legacy add-on uploads to Mozilla AMO, as it could lead to user irritation if a legacy add-on they just installed got disabled when Firefox 57 is launched, it is not the best option to in my opinion.įirst, because the same thing can happen with older legacy add-ons that are still offered on Mozilla AMO. Nightly users, who may continue to run legacy add-ons will face the issue of broken add-ons however even if a fix would mean to change a single line of code only to make the add-on compatible. The situation will improve once Firefox 57 gets released so that the bulk of users will have all legacy add-ons disabled automatically. This applies solely to legacy add-ons, as WebExtensions are not limited in any way. The blocking of new legacy add-ons removes one core fundamental open source principle from Mozilla AMO: the option to take the source, fork the add-on, and make it available again in a different version.
0 kommentar(er)
