They could try. I just keep hearing people who would pay for no extra features as long as it paid for actual Firefox development and not the random unrelated Mozilla projects. I would pay a subscription. But they don't let me.
The problem I (and others that I see here) have is the lack of trust in mozilla's model, esp long term. Their economic reliance in google, their repeatedly stated goals of trying to engineer ad-delivery systems that "respect privacy", their very high CEO salaries, and their random ventures do not inspire much trust, confidence and alignment in their goals. And also the unclear relationships with their for and non-profit parts.
If they can convince me that some subscription for firefox will strictly go for firefox development, that firefox will not pivot to ads (privacy respecting or not), and all the other stuff they have, including executives' salaries and whatnot, are completely separated, I would be more than happy to subscribe.
You can't effectively paywall it because not only is it open source, but there are many nearly equivalent competitors all of which are free. Any subscribers would essentially be donors.
There are people like yourself who would be happy to donate, but not nearly enough. Replacing MoCo's current revenue with donors would require donations at the level of Doctors without Borders, American Cancer Society, or the Make-a-Wish Foundation.
Turning into one of the largest charities in America overnight simply isn't realistic. A drastic downsizing to subsist on donor revenue also isn't wise when Mozilla already has to compete with a smaller team. And "Ladybird does it" isn't a real argument until and unless it graduates from cool project to usable and competitive browser.
Oh no, it would be a donation and it's not going to completely replace all the funding of the parent entity of the project mentioned, therefore it's not realistic or worth trying. Right... That's a lot of arguments unrelated to what I wrote.
> That's a lot of arguments unrelated to what I wrote.
What I understand they are saying is that donations wouldn't be nearly enough. Which is related to what you wrote, which is that you would gladly donate to Firefox (not Mozilla, but Firefox).
They compared it to the largest non-profits in America, presumably because if we look at the money spent by Mozilla every year, that's similar. Right now Google pays for Mozilla, and if you wanted to replace that with donations, it would have to become one of the biggest charities in America. Which does not sound plausible.
I think the point is that if it was open source but free, it would require donations. And given the money that Mozilla spends every year, it would mean that the amount of donations they would need to receive would make them one of the biggest charities in America. Which sounds implausible.
Only on a short distance. To effectively radiate a significant amount of heat, you need to actually deliver the heat to the distant parts of the radiator first. That normally requires active pumping which needs extra energy. So now you need to unfold sonar panels + aluminium + pipes (+ maybe extra pumps)
Orbital assembly of a fluid piping system in space is a pretty colossal problem too (as well as miles of pipes and connections being a massive single point failure for your system). Dispersing the GPUs might be more practical, but it's not exactly optimal for high performance computation...
It’s a fun problem to think about but even if all the problems were solved we would have very quickly deprecating hardware in orbit that’s impossible to service or upgrade
Also likely you don't have as much time. I'd be more keen to discover things on my own a few decades ago. Now I'm limited by work/family life to an hour of play here and there. That means if something looks annoying or long without a good reason, I'm going to look it up and not feel bad at all.
> This means that when "/usr/bin/firefox" sets a "passwords:superwebsite.com = animebooba", an app called "~/Downloads/totally_legit.sh" can not see ...
It will be interesting to see how it treats symlinks in this case. Or specifically, will this idea break completely for nixos or not.
Not everyone wants to recompile the whole app and dependencies with filc to get a slowdown, extra memory use and safety. It's cool that it exists, but omitting the tradeoffs when pushing this is weird.
reply