papercrane

It is bundled with Swing and AWT, but neither really looks like native, which has been a consistent complaint about them.

There is also JavaFX, but that is no longer bundled with the JDK.

Google already has quite a large office in Toronto.

The JDK team made a decision awhile ago to hold the Vector API until value types are final. That's why the API has been incubating so long.

> acquired a warrant IMO to compel the valid, non-destructive PIN be given over.

Compelling a PIN, even with a warrant, is legally questionable. Courts have held that it is a form of 'testimony' because it's compelling you to disclose something you know, while some state courts have ruled the opposite way.

In all likelihood the government wouldn't push it in this instance, to avoid creating any sort of precedent.

The problem will be aftermarket car alarms. There used to be a car that parked on the street near my apartment that would go off ever time a bus went by it.

> Settlement would mean it doesn't become legal precedence, right?

The summary judgment ruling from 2025 in this case will still be legal precedence, the settlement will mean that there is no trial for damages.

However, since this is a district court ruling it is non-binding on other courts.

Yes, the trick is having a "ground-truth" KB it can link to, and trying to avoid citogensis from happening. I'm not sure if it's a technique that's every going to scale because of that.

In this context, it would mean building a knowledge base the model can link to that is considered authoritative. So maybe the LLM is has some slop in it's training, and that causes it to try and output some junk, but if it can't match it to it's verified ground-truth KB it doesn't end up outputting it.

The problem is figuring out what is the authoritative sources.

It's when the models outputs are connected to sources.

So for example, you might have a company chatbot that responds with a summary of a Confluence page it was trained on and a link to the source.

Doesn't eliminate hallucinations, but it does reduce them and gives you a chance to verify.

It's possible they could AOT compile for iOS, but I think the idea they are unifying to be unlikely.

I have an Ergodox EZ for work, and I love it for that, but for my gaming I just use a typical keyboard, I couldn't get used to it for gaming.

Yes, because auto-boxing is just compiling to Integer.getValue under the hood, the bytecode for Integer.getValue(1) and ((Integer) 1) is the same. They'll both compile to something like:

   iconst_1
   invokestatic java/lang/Integer.valueOf:(I)Ljava/lang/Integer

> I'd love to see pledge/unveil on (upstream) Linux - but I'm not holding my breath

There is Landlock now, I believe it would be possible to implement unveil and pledge on top of that.

There are a number of licenses that are named MIT that are all similar, but not identical.

The "Expat" here is the MIT license variant. It is referring to the Expat XML parsing library that first used this license.

Usually when projects these days use an MIT license this is the version they use.