This is a use case that hasn't yet been proven out, though. "Good enough" for an executive may not be "good enough" to keep the company solvent, and there's no shortage of private equity morons who have no understanding of their own assets.
Every decade, global capitalism decides that 100 million people don't need to eat and they get to starve to death. In the same time period, slightly less than that die from lack of medical care the market decides they don't need.
And that's just contemporary capitalism. Hundreds of millions starved in famines, and starving people got to watch as the food they themselves harvested was shipped to markets that would pay more for it. Millions were enslaved, and cultures, races and communities were wiped off the faces of continents in the name of profit.
And created such a boom of medicine that one can assert that the poorest among us should be entitled to it, and not have that assertion dismissed for being literally impossible.
Firefox is set to allocate memory until a certain absolute limit or memory pressure is reached. It will eat memory whether you have 4GB of RAM of 40GB.
Set this to something you find reasonable: `browser.low_commit_space_threshold_percent`
And make sure tab unloading is enabled.
Also, you can achieve the same thing with cgroups by giving Firefox a slice of memory it can grow into.
No one, if you aren't in the administration's good graces and something shitty happens unrelated to you, you've put a target on your back to be suspect #1.
Companies that submit bids for contracts get contracts. You would be surprised at the diversity of size and scale of companies which service defense contracts in particular - very small companies can end up in big supply chains because they're the ones who turn up to make the part.
Ignorant of this NPU, but in my experience, you're expected to use some cursed stack of proprietary tools/runtimes/SDKs/etc and no, it will not play nicely with anything you want it to unless you write the support yourself.
> BTW what's up with people pushing N150 and N300 in every single ARM SBC thread?
For 90% of use cases, ARM SBCs are not appropriate and will not meet expectations over time.
People expect them to be little PCs, and intend to use them that way, but they are not. Mini PCs, on the other hand, are literally little PCs and will meet the expectations users have when dealing with PCs.
It's not a problem with ARM servers or vendors that care about building well designed ARM workstations.
It's a problem that's inherit to mobile computing and will likely never change unless with regulation or an open standards device line somehow hitting it out of the park and setting new expectations a la PCs.
The problem is zero expectation of ever running anything other than the vendor supplied support package/image and how fast/cheap it is to just wire shit together instead of worrying about standards and interoperability with 3rd party integrators.
How so? The Steam Deck is an x86 mobile PC with all the implications of everything (well, all the generic hardware e.g. WiFi, GPU IIRC) work out of the box.
The problem is increasing profits by replacing paid labor with something "good enough".
reply