L6 is staff, senior staff is L7.

I would instead argue that Firefox's Gecko engine is beyond saving and that any money invested in it now would be better donated to other community projects because there isn't enough resource to catch up. Sticking with Gecko will eventually lead to the dismise of Firefox the organization.

Microsoft, with their resource and their ability to bundle Microsoft Edge in with Windows, couldn't get any appreciable amount of marketshare. Firefox, with less resource than Microsoft, won't fare any better.

Rebuilding Firefox with Chronium would salvage whatever the mindshare/marketshare left. Then Firefox could still wield some influence with their marketshare and the threat of forking Chronium.

I never had Firefox crashes until Ubuntu 21.10 which I think made Firefox a snap, now I get crashes when it tries to load fonts. And I get that colour scheme thing now too.

Good to know! Would you be interested in performing the same tests and using `wrk` and report the difference?

I grew up in Minneapolis and then the suburbs and left as soon as I could... but returned to a small town about 2 hours drive southeast in a small town called Winona. It's the home of Fastenal, Peerless Chain, and a ton of other "startups" from the last 50 years. I work "remote" for my own consultancy turned Electron-based software company making apps for label printers. The cost of a home here in Winona, circa 10 years ago was about $100k and even though prices have nearly doubled the houses are still affordable. You don't need to make much to live here, and we love the beauty of Minnesota... especially southeastern Minnesota. It's MN "NICE!"

As I work more with someone from the midwest, and being from the mid-atlantic region myself, I'm growing more and more suspicious of the "hard worker" mindset.

What I'm seeing, over and over, is that this drive to "work hard" ends up creating all kinds of "bad" work; difficult/tedious labor intensive decisions rather than efficient and innovative ways that are objectively better.

He gets stuck on a problem, and won't put it down and go pick up the other problems that are easier to complete and provide similar (if slightly reduced) value to the customer. That's his "hard work" ethic at play, and I've found it pretty difficult to break him of that habit.

And this isn't some idle efficiency meddling on my behalf; instead of providing some incremental value on a daily or near-daily basis, he goes completely dark for days or even weeks at a time before surfacing with a "glorious solution" to the problem he's ratholed on. If he had dropped the work at the first sign of trouble (seemingly anathema to a "hard worker"), he would have found other ways to have an impact on our customers. He's substantially less effective because he wants to "work hard".

I do believe that people who value "hard work" generally don't understand this downside, and it's kind of fascinating to me, because of how ingrained this flawed trait is into an entire subset of American culture (being an American myself).

I don't think the `ab` tool does anything special, so it's likely these are closed and reopened after each request. For the purposes of comparison of one architecture to another, this was sufficient, and mimics user behavior well enough. But feel free to try out the test with different headers!

Here's why I moved away from Linux to macOS:

- I'm sorry, but no Linux DE I've ever used beats macOS in terms of stability. The file explorers are also a joke and frequently changing.

- I've never booted to a black screen when upgrading macOS.

- 99% of the work I do never needs anything that has to be virtualized under macOS.

- Macbooks are solid laptops. Every other laptop I've owned hasn't stood the test of time as well as my Mac.

- More [actually good] software supports macOS. It's just a fact.

- macOS is fundamentally the same as it was 10 years ago, just with some relatively minor changes to the design. I'm pretty confident they're not going to move the dock to the top and force a new window toolkit on me that most existing software can't use.

- macOS has hardware that I know it will work with. Finding compatible hardware for Linux can be frustrating and not as complete as is claimed.

- Windows and macOS solved vsync issues long ago. Somehow, even with Wayland, you can still experience horizontal tearing if you have the wrong monitor or graphics card.

---

All the customization doesn't offset the trouble that desktop Linux can bring.

Front end for git in go. Surely you stumbled across GOGS? https://gogs.io/

There are certainly restaurants nearby, but not sure I'd call them cheap. I imagine a lot of MIT students don't have the money to eat out every day. And since most dorms don't have any kind of kitchens or cooking implements, buying food from the grocery and cooking isn't really an option. Pre-made meals or other things from grocery stores that don't require cooking could work, but, again, I'd expect some/many students rely on their university meal plan for their food, and don't have much spare money to buy their own.