We had to write two certified letters to all the previous owners, then we either filed that reply or the returned unsigned certified mail after 45 days (for each previous owner) we were able finally file a title transfer application with the Department of Wildlife and the DMV, then we had to wait for two letters to clear the title with those organizations and then finally we applied for a new title from the DMV. It was like 3 years of my life. We finally sold it!
Is there such a thing as mid-ocean fuel transfer? I can imagine some intrepid individuals strike up a bargain to siphon the fuel off of the abandoned ship onto one with the appropriate paperwork.
I must have missed something because my HP keeps ticking down until I pass out and get warped back to the command center. Eating food and resting do not seem to change the situation.
Similarly, are there any modern benchmarks of the performance impact of pinning programs to a core in Linux? Are we talking <1% or something actually notable for a CPU bound program?
I have read there are some potential security benefits if you were to keep your most exploitable programs (eg web browser) on its own dedicated core.
It's very heavily dependent on what your processes are doing. I've seen extreme cases where the gains of pinning were large (well over 2x when cooperative tasks were pinned to the same core), but thats primarily about preventing the CPU from idling long enough to enter deeper idle states.
Yeah, this my guess as well. The other OSes have the ability to pin to specific cores, but first party Apple leaned hard into coding to that hardware vision. Since Apple would love to merge the desktop and mobile software, being very deliberate about what is background vs foreground work is essential. Windows and Linux have not had the hardware guarantees of differentiating between cores, so few programs have taken the effort to be explicit about how the work is executed.
When I ran Gnome, I was regularly annoyed at how often an indexing service would chew through CPU.
There was an article by Raymond Chen where he argued that giving app developers an API option to say "run me under high/low priority" rarely works because every developer views their program as the main character on the stage and couldn't care less about other programs' performance, and they are incentivized to enable the "high priority" option if given a chance because it makes their program run better (at the expense of other programs). So unless there's a strict audit on some kind of app store or some API rules which enforce developers don't abuse the priority API, sometimes it's better to let the OS decide all the scheduling dynamically as the programs run (say, a foreground UI window automatically is given a high priority by the OS), so that the scheduling was fair.
The way it’s conceptualized on Apple platforms is primarily user-initiated vs. program initiated, with the former getting priority. It’s positioned as being about tasks within a program competing for resources rather than programs competing with each other.
So for example, if in an email client the user has initiated the export of a mailbox, that is given utmost priority while things like indexing and periodic fetches get put on the back burner.
This works because even a selfish developer wants their program to run well, which setting all tasks as high priority actively and often visibly impedes, and so they push less essential work to the background.
It just happens that in this case, smart threading on the per-process level makes life for the system scheduler easier.
...violates no patents and can't materially harm a person in any way can be restricted on grounds of paternalistic "safety", then one would be right to remain skeptical of the claim that the FDA is restricting action against unauthorized semaglutide knockoffs to...
Well actually, there are lawsuits in the works because the Philips CPAP machine had toxic foam which would break down and increase the risk of cancer.
But I think that proves my point, the supposedly "rigorous" FDA review didn't flag concerns about foam in the airpath of something you breathe through, so what exactly is the approval process buying you? Philips issued a voluntary recall but resmed uses foam in their units too, and while they claim it's a different type of foam it seems there are better ways to engineer sound reduction than putting foam in the air channel and potentially breathing in microplastics.
Never heard the follow-up, so good to hear that it was potentially less hazardous than the initial reporting.
However, I am still mixed on the interpretation. I do not think the FDA is as good as say the NTSB, but I do think they will take lessons learned from a bad outcome. New medical products are likely to undergo additional scrutiny on any kinds of foams/solvents/whatever that are directly in the airway path. It is only because it is such a heavily regulated product that the entire product chain had to be stamped, certified, and traced so that such an investigation was possible. In a theoretical fly-by-night product offering, SKUs might be changing daily as the vendor can shave pennies off of the development price.
Word has a billion features you did not know that exist. Getting something Word shaped is probably straight-forward enough (how long did it take to make Google Docs), but getting those dangling features and quirks would be a long haul.
Mimicking Excel - woof. This one is used by so many people in different ways, that unless you offer 1:1 bug compatibility, it would be challenging to get 100% of people to meet everyone's current use case.
reply