No, it is not. bcachefs needs to have all the code for error recover in the kernel as it needs to be available when a storage device fails in any of a myriad of ways.
Maintaining a piece of code that needs to run in both user space and the kernel is messy and time consuming. You end up running into issues where dependencies require the porting of gobs of infrastructure from the kernel into userspace. That's easy for some thing, very hard for others. There's a better place to spend those resource: by stabilizing bcachefs in the kernel where it belongs.
Other people have tried and failed at this before, and I'm sure that someone will try the same thing again in the future and relearn the same lesson. I know as business requirements for a former employer resulted in such a beast. Other people thought they could just run their userspace code in the kernel, but they didn't know about limits on kernel stack size, they didn't know about contexts where blocking vs non-blocking behaviour is required or how that interacted with softirqs. Please, just don't do this or advocate for it.
I don’t really see how it’s different than how you’d setup someone really junior to have a playground of sorts.
It’s not exactly a groundbreaking line of reasoning that leads one to the conclusion of “I shouldn’t let this non-deterministic system access production servers.”
Now, setting up an LLM so that they can iterate without a human in the loop is a learned skill, but not a huge one.
Is there a reason all workspace accounts need a project ID? We pay for gemini pro for our workspace accounts but we don't use GCP or have a project ID otherwise.
The reason is that billing is separate, via the paid tier of the API. Just a few minutes ago, I was able to test Gemini CLI using a Workspace account after setting up a project in the free tier of the API. However, that seems to have been a bug on their end, because I now get 403 errors (Forbidden) with that configuration. The remaining options are either to set up billing for the API or use a non-Workspace Google account.
Whether or not you are religious, channeling the human impulse to worship into something singular, immaterial, eternal, without form, and with very precise rules to not murder, lie, covet, etc… is quite useful for human organization.
If God or The Gods are defined as not being man-made, then each person will be able to find their own interpretation and understanding. As contrary to man-made objects and concepts. Most modern people worship "the government" or "the state", even though there is no dispute whether it was created by man or not and whether it acts under the influence of man or not.
The vast majority of them volunteered. And that's just conscription -- every country would do the same in such a situation. The US pursued and prosecuted thousands of cases of draft dodging in WW2, forcing most of them to go and fight.
>the President may grant a 1-time extension of not more than 90 days with respect to the date on which this subsection would otherwise apply to such application pursuant to paragraph (2), if the President certifies to Congress that--
(A) a path to executing a qualified divestiture has been identified with respect to such application;
>(B) evidence of significant progress toward executing such qualified divestiture has been produced with respect to such application; and
>(C) there are in place the relevant binding legal agreements to enable execution of such qualified divestiture during the period of such extension.
It seems highly unlikely any of those criteria are being. Trump is not even suggesting it, never mind providing receipts.
Seems like a pretty vacuous article if “megaregions” are so poorly defined. Anyone who has ever driven between Spokane and Portland or Seattle knows it could hardly be considered “mega”.
I think the consensus is that the Portland-Seattle-Vancouver corridor is the "real" megaregion of the PNW. That corridor has ~10 million people and a high per capita GDP, especially the middle part which kind of ties it together.
If you were going to include Spokane, it isn't that much of a stretch to include Boise as well.
Yea, that makes sense. I think you can conceivably define a megaregion to include places like the PNW corridor, the bay area, research triangle, etc. I'm just a bit baffled how Spokane and the region between makes the cut. Seems like the author just wanted to draw a bigger circle.
Some of these megaregions really are "kind of one thing" like Southern California, others are pretty separated. Spokane is close to Seattle and Portland so there's traffic there, but I don't know they really operate as one "region".