You're in luck, this seems to _only_ support WASM in the browser for the time being.
> Graphite's code architecture is structured to deliver native performance for your graphically intensive workloads on desktop platforms and very low overhead on the web thanks to WebAssembly and WebGPU
Agreed, my company tried buck2 first when evaluating a cargo replacement, but bazel is just so much more mature at this point that it ended up being the natural choice. Thanks for your examples, they helped us get started :)
This is not.. really the right takeaway from his work. That not every true statement within a system is provable from its axioms, or that the consistency of a system is not provable within that system, does not mean that axioms are not useful. Indeed, what math is not grounded in the end by axioms?
This is not some "glossing over some details for a lay audience" situation. It is not a lack of depth. It makes ridiculous claims, fundamentally misrepresenting what this research is, to make it sound cooler and more interesting. This is one of the worst pieces of science journalism I've ever seen.
You typically wouldn't use an array with a million objects in Java if you cared about performance though (for exactly that reason), you'd architect it some other way. Using SoA style when appropriate, for example.
There has been big debates about this in Norway for as long as I can remember. One of the arguments for the "father's quota" is that when fathers were not "forced" to take at least some parental leave, there was an implied policy many places that as a father you left all the parental leave for the mother, with all the inequality that follows. Personally I am very pro the father's quota, as no employer can now (implicitly) force me to not take it.
That is basically the case in Norway. Both the mother and the father gets 15 weeks mandatory each, and the rest (of a full year) is divided between them as they themselves see fit, iirc.
There's nothing in PostgREST that stops you from limiting control so that even anonymous users can use it safely. I've used PostgREST for user-facing APIs with success, but it requires some knowledge about the postgres access control model.
EDIT: And "Just point Postgrest at your PostreSQL database" is rarely a good idea in my experience, I usually have (versioned) API-schemas containing views, so that I can change my underlying data schema at will without borking the API.