At 11:00 in the evening, there are two options for what they’re dealing with. Either:

1. They have made precisely no headway whatsoever in actually solving the bug, or
2. They have fixed the bug, but the debugging made them go “—wait, how did that ever work in the first place?!”

If it’s #1, odds are pretty good that there’s a random debug step they put in at 9:08 in the morning that’s screwing everything up now. If it’s #2, odds are pretty good that it actually didn’t work before, and now they’ve got to go back through the last six months of data and rectify it to fix that bug.

That just means it’s in active development and will come to the beta browser soon, and then to the stable version.

Honestly this is the big thing I’ve found handy about using Mint. If there’s something wrong and I can’t find it a Mint answer, nine times out of ten I can fix it by searching for the Ubuntu solution. There’s so much Ubuntu troubleshooting going on.

I’m currently mid-migration from Windows to Linux, so I have to wait until the Windows release or until I finish migrating (I’m not really up for building a beta at this point), but I’m very excited.

I’m keeping an eye on Zed: https://zed.dev/

Yeah, AI, whatever. It’s written in Rust and looks pretty great.

I mean, the real reason is that Chrome added them four years ago. Like it or not, when Chrome adds something, it becomes a de facto standard for browsers.

People work for corporations.

They are mostly the same as keeping them in separate browser windows, but with the advantage of being in one browser window. They also have the advantage of being label-able.

I don’t keep tabs open forever, but back when I used Chrome I regularly used tab groups when I was working on multiple projects simultaneously; the Jira ticket, the PRD, the API documentation, the necessary AWS consoles, and the GitHub PR for one project go in a tab group. Name that group and collapse it, and now you can easily reopen it again when you’re ready to switch contexts.

“Why not just put them in a separate window?” Sometimes that’s preferable. Sometimes both solutions together are better. On a single monitor, having everything in one window is usually preferable for my workflow. In any case, you can’t name a separate window. And if you use a sidebar extension, they aren’t persistent across multiple windows.

“Why not just use bookmarks?” Bookmarks are a long term solution. Tab groups solve the short term problem. They’re ephemeral.

“Why not just close the tabs until you need them again?” I do that as much as I can. But it’s not practical in all cases. One project is in active development, one is in PR Review, one is in QA, and I have a support escalation I need to work on in the meantime. Each of those tabs might be needed at any time during the week.

Yeah, I get twitchy when I have more than about ten tabs open. My senior regularly has thousands, across multiple browser windows. There are two types of people.

I don’t know about that. I regularly forget what year it is.

Then again, I’m pushing 40.

Well, this month in particular…

This happened ages ago, didn’t it? Am I missing something new?

Indeed; it definitely would show some promise. At that point, you’d run into the problem of needing to continually update its weighting and models to account for evolving language, but that’s probably not a completely unsolvable problem.

So maybe “never” is an exaggeration. As currently expressed, though, I think I can probably stand by my assertion.

Proven? I don’t think so. I don’t think there’s a way to devise a formal proof around it. But there’s a lot of evidence that, even if it’s technically solvable, we’re nowhere close.

We will never solve the Scunthorpe Problem.

You can actually fairly easily unload tabs with about:unloads right now, but you have to do it in the order Facebook Firefox thinks they should be done for some reason.

Honestly, I don’t know why, but sidebar tabs have just never worked for me. It makes no sense, but for some reason my brain just doesn’t process them correctly.

But I agree, in general more fine-grained control of tabs would be the thing I would need in order to feel like Firefox was feature-complete.

Edit: Facebook? Wtf?

Uh, no, they definitely need tab grouping before they get into making CSS theming easier.

Actually, since the hurricane season keeps starting earlier and earlier, that would benefit the top of the list (since early-season hurricanes tend to be weaker) because the ones that everyone hears about will almost certainly be several names down the list. For instance, the only ones that anybody’s heard about this year are Beryl (second named storm), Helene (eighth named storm), and Milton (thirteenth named storm). Even Kirk (eleventh named storm and a category 4) went by without a fuss, because it never made landfall.

So my suggestion is, we keep going with the naming system we have, but go with your list–maybe use the Carbon Majors report–and apply the company’s name when they make landfall as a Category 3 or higher, when they cause more than ten fatalities, or when they prompt the evacuation of more than 5,000 people. At that point, the storm gets a tag: “Hurricane Chinese-Coal Beryl.” “Hurricane Saudi-Oil Helene.” “Hurricane Russian-Oil Milton.”

Money has a definition, but “income” is the word used, and that’s a euphemism that could be remapped.

It, uh…makes…food…uh…come in…?