pixelscript

I think I'd keep using the slow cooker in that situation, because 100% of slow cooker time is parallelized with work time. Even if the pressure cooker is fast, it can't compete with zero.

Though, having the pressure cooker available for when I'm a brainless oaf who didn't start the slow cooker in the morning sounds like a great fallback option.

Not on low, no. I make no promises about high.

I think slowcookers in general avoid reaching boiling temps because the whole point is being able to leave them run unattended for hours, which you can't safely do if it's boiling off.

My best guess for a potential solution if you're gung-ho to try and find a way is to pour the juice into a saucepan and bring it to a boil separately, let it cool, then prepare as directed. But I have no idea what that will do to this compound she is allergic to, whether boiling water is sufficiently hot to do that, how long you need to hold it there to make it safe, or what else boiling it will do to the flavor. I also have no idea what the nature of the allergic reaction is and how much risk it puts her in. So for lawyer reasons I can't in good faith reccommend you make this for her at all.

If you have actual medical advice telling you what temp denatures the bad compound and how long it needs to be held there to make it safe, try leaving water sit in your slow cooker with an accurate thermometer and see for yourself if it gets to that temp. If you can confirm that, then it might be safe.

Experiment with it at your own risk with her consent, I guess.

It's a start!

I hope I'm not moving the goalposts too far here, but I do want to stress that if at any point in this process a consumer has to go out of their way to get the Linux experience, it will never compete. Every lowering of the barrier is progress, but there is a critical mass point we clearly haven't reached yet.

I haven't. I suppose that's a large chunk of where the advantage comes from, isn't it? New computers are expected to just come with the OS on them already. The entire process of installing an OS no matter whose you use is a completely alien concept to most people, and anyone who thinks it's "not that hard for the average person" is daft.

Are OEM Linux installs even a thing? For like, ""real"" hardware, from ""real"" (read: mainstream enough to buy on a shelf at Best Buy) manufacturers? Those are what we need to be steering people to, IMO, if we ever want Linux to be competitive with Windows and macOS for an average person.

+1 for Reddit API exodus.

Lemmy was sold to me as a Reddit replacement. And it is, superficially. I knew it wasn't going to be drop-in going in. But the longer I use it the more I think it's not really quite like Reddit, and never will be. And that's fine. Lemmy is its own character and I like it for what it is.

I still use Reddit. Lemmy doesn't scratch all the itches for me. But only old.reddit on the desktop and on mobile with a UI de-shittifying extension. I'm amazed they still offer it at all. Once that's cut off, something I've been bracing myself for for years, I'll consider the UX enshittification to have fully completed and I'll truly bail. I simply refuse to use their gentrified UI. And I'm tired as it is having to slap on compatibility layers just to keep their less terrible alternative on life support; I'm not going to do the same thing to make their mainstream UI somewhat more palatable.

There's "difficult" in the sense of a person's reasonable ability to follow rather straightforward prompts, even if they don't know what they mean. Linux installers are rather low difficulty here.

Then there's "difficult" in the sense of how much a typical person will tolerate being rushed through a bunch of mystifying questions just to get through to the other side, particularly when an alternative option that doesn't ask them at all is available. Linux is atrocious in that regard.

Really hot take: more choice is actively bad for people who don't care. Which is far and away most of them. The kind of personality matrix that is attracted to Linux as-is tends to be the kind that wants everything configurable, and for the system to never assume anything, and let the user roll everything themselves. Most people are not like this and they don't appreciate this "courtesy". Giving them the option at all is the deterrent.

If you want to talk Linux installers that are on-par with the UX feel experience provided by macOS or Windows from a normie's perspective, show me one that doesn't ask anything of the user that doesn't also appear in one of those installers. Not a single thing. If it does, that's a speed bump that has no reason to be there. Because the person who is using it likely doesn't have the answer, and if the correct course of action in that situation is, "It doesn't matter, just use the default", then why did it even ask? It should just do it.

I'm not suggesting we need to completely rob all installers of any choice, either. We can have a two-tier system, so people who actually know the answers to those questions can select the advanced install, and people who don't care can select the streamlined install.

The dirty little secret about the mass market aversion to Linux is that people are genuinely not interested in or remotely curious about the inner workings of their computers. Those of us who like to immerse ourselves in it for fun are outliers. Any one of us who denies it has their head extremely far up their ass.

It's similar to car mechanics. The vast majority of drivers don't know or care how the machine works, they just want it to get them where they want to go. If it breaks, take it to the nerd who gives a shit. The more fiberglass cowls and covers you slap on top to hide the inner workings of the thing and automatic features you implement to abstract it all away from the user, the better, from their perspective. The damn car should just go. How it goes is not of any concern.

Linux needs to offer a similar experience if it wants mass market appeal any time soon. The alternative, trying to actually spark that curiosity in people to enjoy understanding how the machine works, is far too slow of a process to make any measurable movement of the needle of user adoption over time. Low barrier to entry isn't good enough when zero barrier to entry exists and is already the standard.

It's such a stumble of history that teeth were historically associated with barbers and not doctors, causing the dental practice industry to evolve separately from all other medical practices. Bullshit how a vestige of that lives on today in dental insurance coverage being its own special snowflake thing.

Until they make T shaped displays that I can mount sideways, to get the best of both worlds

Were you also a proud owner of an LG Wing? 😉

I'd rather have multiple monitors so I have the more intuituve window snapping. But to each their own.

Zero-effort french dip:

1. Buy an arm roast at the grocery store the night before, sleep.
2. Wake up, dump in arm roast, a can of french onion soup, top off with water or beef stock
3. Cover and set to Low, then go to work for the day
4. Return home in the evening, shred meat with some forks, serve on buns with cheese of your choice

It's not glamorous, and you could do a lot better with more intelligent ingredient choice and more prep (searing the roast first, adding veg, doing the broth from scratch, etc). But the result-to-effort ratio of the bare minimum is unmatched if you're ever in a "fuck it, guyslop night" kinda mood.

For slightly more effort, I sometimes make a very simple hot apple cider recipe. That's non-alcoholic for all the non-Americans, though you can always spike it with your spirit of choice:

For every 8 cups (~1.8L, 2L is probably fine) of apple juice from concentrate, add:

• 1 tsp whole cloves
• 1 tsp whole allspice
• 2 cinnamon sticks
• 1/3 cup packed (~70g) light brown sugar
• 1 large orange, sliced

Cook on low for 2 hours, fish out solids, serve hot.

If you can specifically find "honeycrisp" apple cider at the grocery store to use as your base, it's even better. I can sometimes find it seasonally at Walmart.

Well, I also tend to consider ultrawide monitors a mistake in their own right. Why would you want a 49" wide literally anything if it's not some kind of immersive media experience where menus are irrelevant anyway?

Of course, if that is in fact exactly what you bought it for, I have no complaints. Even if I disagree with having one for other purposes, that's still no reason for the OS to punish you for having one when you try to use it that way when that problem is completely avoidable.

I've personally always loathed the global menu bar paradigm of macOS. Having a menu bar that's wholly detatched from the currently open window that is context-aware based on which window has focus always felt like an irritating speed bump to me. My mind feels like the OS itself is hiding things from me by only allowing me to see a single app's menu bar at a time.

But then again, I have no objective qualms with it. I'm sure I could adapt to it. When have I realistically needed to see more than one menu bar at once? I can't name a time. I'm probbably just pearl-clutching at the perceived arresting of my agency to do things when in fact I'm losing effectively nothing.

At any rate, we agree it's a sure sight better than the shitshow that is GTK. "Hm? Window decorators and shit? Nahhh, those are your problem. Go roll your own." For the flagship windowing toolkit of the GNOME Project, the DE I'd consider the closest in philosophy to what macOS has going on, that was a rather strange position to take.