![]() ![]() >The items/services we all want/need, that are scarce, and can't be imported from our foreign "slaves", are where you will find it concentrated. (Though around here, the suburbs of greater Cincinnati, home prices haven't generally doubled in ten years my home's valuation is maybe 15% higher than it was when I bought it five years ago.) I can hardly think of anything besides houses and GPUs that (a) impact me and (b) have gone up fairly drastically in price. Got anything besides home prices? Car prices haven't gone up that much, at least. Regardless, rent is accounted for in the CPI (though not assets like home purchases). Inflation is more than just home prices, and just because something is more expensive than it used to be doesn't mean that inflation is the culprit. > Remember when house prices went up 20-30% in a 6 month period of 2021? Not inflation? I can check those prices and they haven't gone up nearly as much as you're saying. Everyone has to buy groceries at some point, whether wealthy or impoverished, and for those on lower incomes groceries are a fairly major share of total consumption. ![]() How is that a problem? Let's say I work in the grocery industry. Said compiler warnings are frequently valid, and analyzing them at least to know if its true is a worthwhile code quality exercise. (not that gcc is better than clang, only that ideally a project like firefox would compile cleanly with a wide range of compilers). When the work was done to actually get it to build with gcc, it turned out to be even faster. Then they claimed that the result was "faster" than gcc, despite the fact they were comparing an old version of GCC with a newer version clang. Then frequently instead of actually fixing them they did things like switch from building with an old GCC to a newer clang because it threw fewer errors. And overwhelmingly these breaks were caused by crappy C++ programming where people were doing things that were known not to be syntactically correct but no one bothered to fix them. I've mentioned elsewhere the difficultly building it, but even more than that, is that pretty much every single version of gcc that came out for a while would break firefox in some fundamental ways. Seat of the pants, I would say getting something like rust on par with g++/clang code generation, and 3rd party tools is probably in the same ballpark engineering wise as actually maintaining the browser.Īnd if you spend a little time looking at firefox, there is/was a lot of low hanging fruit. Yes, but consider the engineering effort to create a general purpose memory safe language vs just a domain specific one in comparison to the work required to write a browser, which also includes another domain specific language (javascript). The diversity of truly independent browser engines is far too important to give up without a fight. We as a community, cannot afford to let Firefox languish until the only browsers in the world are Chromium derivatives. Firefox is also Mozilla's raison d'être, and they should embrace that. Make whatever partnerships are needed to have a steady stream of income, be that donation or selling out to Google or Bing.įirefox is in trouble. ![]() Make sure that all donations from now on are redirected to things that support Firefox development and nothing else, period. Get a CEO/upper management that are in it for the passion, not the money, and cut their salaries (bonuses tied directly to increase in Firefox market share). Fire all inessential staff that don't want to work on Firefox. Donate the major money drains that aren't Firefox to the Apache Foundation or another worthy custodian Cut out all (or at the very least, most) initiatives that don't serve the goal of promoting Firefox's market share or sustainability going forward ![]()
0 Comments
Leave a Reply. |