The microwave radio frequency has been selected so the energy will be strongly absorbed by the water molecules contained within the food or drink in the target area.
This frequency does not happen to be absorbed by cooking oils very much.
An approximate rule of thumb is that a nominally powered microwave oven will penetrate an inch to maybe two inches into ordinary food before all the energy has been absorbed so that's about as far as it will heat "toward the inside" rather than from the inside. Unless it's little things like small potatoes where the needed heat forms through-and-through. For much bigger stuff where the deep part can not be energized directly, it can be good to take it easy so the outer target layer can be kept from overheating long enough for the outer layer itself to cook the inside thoroughly.
Or take a break a couple times to stir a large bowl of soup between heating sessions.
They're such idiots, they haven't published Mistral Code on OpenVSX. LMAO.
I wanted to recommend to a group of friends to try it, but I can't because they use VSCodium.
It certainly makes them idiots, from the perspective of artificially restricting their audience; AFAIK it's very simple to publish on OpenVSX, there are no extension changes needed. Most devs I know use VSCodium, not VSCode.
And how many devs do you know? What percentage of all the devs in the world does that represent?
If you know a million devs who mostly use VSCodium instead of VSCode, that might be significant. But I'm guessing you just jump to conclusions about almost everything based on your own bubble and lack of critical thinking skills. Then you can just call other people idiots while patting yourself on the back for being so smart.
It's not an issue for me, I have enough coding assistants. It's a issue for them, since they are restricting their audience artificially, since it requires minimal effort to publish on OpenVSX.
That's because of the Javascript running on them. If I have a dozen youtube tabs that are not suspended my FF becomes very janky and if I look in FF task manager, sure enough, they're consuming lots of CPU. I suspend them and FF becomes snappier again.
Right, but the article says nothing about suspending and seems to strongly suggest that tabs take "no ram at all" by default, which is just plain false, unless I'm misunderstanding something. I don't even see a way to suspend tabs without a separate extension.
There is also an unfair comparison made in the article.
> A quick PCMag test shows that 10 Chrome tabs on a Windows 11 PC with 32GB of RAM and 2TB of NVMe SSD storage take up over 2,000MB, or 12.5% of PC memory, so there's still room for improvement (Hazel's massive Firefox session file is just 70MB).
Taking up nearly 2GB of RAM for 10 tabs sucks, but they seem to be comparing the size of the session on disk to the resident size of the loaded browser in memory, of course the memory footprint is going to blow it away.
well i have 4600 tabs, 13 windows, 18 tab groups and 130 firefox processes. htop shows me that while each browser process has about 3GB of virtual memory, all of them barely register any real memory use. so as far as i can tell, tabs do not use any memory.
right, most tabs are suspended. i also use an extension that automatically suspends inactive tabs, so i don't have more than 20 or 30 tabs that are not suspended.
Close Firefox then restore your session. Until you switch to a tab, it stays unloaded and consumes nearly no resources. The tab does stay resident in memory until you restart again, or otherwise suspend it.
I don't want to keep any tabs open, but I haven't found a better way for my workflow and I've tried quite a few.
My tabs fall into the following categories:
- unfinished/long running projects/topics/research: for these I use a version of the Tabs Aside! extension that I've modified, which converts them to bookmarks.
- tabs I will want to look at someday and further categorize and/or take action: for these I implemented a babashka script that when I click on an URL it fetches the page, extracts the title and displays it and asks me if I want to open it now, or save it for later in an org-file. This doesn't work, unfortunately, for URLs that I open from another FF page. For these, my long term plan involves archiving the text and doing RAG on them, as they relate to my long term interests/projects/curiosities.
- tabs I need for the actively running projects/tasks
> Also it heats food inside out equally as compared to stove which transmit heat from the out layer to inside
This is also false, photons don't teleport themselves to the inside of food.