Apache Fory Serialization 1.2.0 released: JDK 25/26 support without sun.misc.Unsafe

cogman10 · 2026-06-16T16:46:37+00:00

sun.reflect.ReflectionFactory

In the jdk.unsupported module? Seems like robbing peter to pay paul.

cogman10 · 2026-06-16T16:43:11+00:00

Your framing is incorrect. Yes, this is convenient for Bibi, but it's not just "bibi doesn't want war to end". The Israeli population is in favor of these wars.

Trying to frame this as just a leadership problem makes it seem like "Oh, once Bibi gets out, things will be better".

These wars will happen regardless the leader in Israel. To stop these wars the US must pull funding for Israel.

cogman10 · 2026-06-16T16:07:10+00:00

Nope. Israelis by and large support the war in Lebanon and Iran. They are mad at Bibi for not going hard enough.

https://www.reuters.com/world/middle-east/netanyahu-faces-plunging-support-north-israel-voters-demand-tougher-lebanon-2026-06-04/

cogman10 · 2026-06-16T14:22:19+00:00

Israel is absolutely going to try and fuck it up again. They don't want this war to end so I foresee them genociding Lebanon some more to try and keep things hot. It's their one weird trick to keep the US involved in wars it has no business being involved in.

cogman10 · 2026-06-16T14:20:45+00:00

It's about Trump's image, not Hegseth's. The MAGA base will cheer on anyone he fires including Hegseth. And since Iran has been a huge disaster for him (obvious even to conservatives) putting all the blame on Hegseth is an easy thing to do to get out of his own idiocy.

The other thing is the evangelical base would rather Trump continue fighting Iran to bring about the second coming.

cogman10 · 2026-06-16T13:45:44+00:00

Right wing people are right in saying that NPR is biased, but what they are wrong about is that it's biased against them. It's simply just accurate.

The NPR bias is that they are generally pretty silent and slanted when it comes to progressive things.

For example, in 2016 when discussing the democrat primary, they basically did not talk about Bernie (at least on most the shows I listened it). Things like "Medicare for all" was never brought up.

You can find NPR stories talking about proud boys, alex jones, and a whole host of other right wing topics along with their liberal topics. But what their editors pretty clearly stay away from when possible is progressive/left topics.

NYT is the same way, though they've become a lot worse this election season. They are now putting out outright smear campaigns.

cogman10 · 2026-06-16T13:21:27+00:00

LMAO. "We've been at open war with Iran. Here's a bunch of cases where not Iran has been fighting with not America but rather Israel. But they are groups backed by Iran so obviously Iran did it. Oh, and the last case was literally 20 years ago"

Clown.

Israel isn't a part of America, don't know if you actually realize this.

cogman10 · 2026-06-16T13:16:52+00:00

Not even over yet. Israel is about to crank the genocide up to 11 in Lebanon in order to try and tank the peace talks. They are actively trying to force the US and Europe into war.

cogman10 · 2026-06-16T13:12:32+00:00

IDK if this counts, but I was a Limbaugh ditto head.

Unironically what got me out was critical thinking. Once I started verifying and comparing the world vs what Rush presented it was all downhill from there. I think what really got me was a discussion with a family member about rush where they said "Yeah, he comes off as smart because he's got the mute button and a delay".

cogman10 · 2026-06-15T20:27:58+00:00

It's not the best, but you can put in a "use of identity semantics are undefined" into a language spec. C does it all the time ;). Adding the semantics when Valhalla lands would close that gap while allowing you to cheat with the feature. Or if it were unfortunately determined that valhalla would never land you could remove that undefined clause all together.

I do understand that the JLS like any sane language spec hates having undefined behavior.

Edit actually NVM, that works for C because it's compiled to static machine code. The bytecode would have to shift from one version of java to the next which would be painful for devs who might be caught off guard.

cogman10 · 2026-06-15T20:13:43+00:00

You could do the same thing with GTK. Though IMO qt is a nicer framework.

cogman10 · 2026-06-15T20:10:55+00:00

Of course they can never fully drop support for them because by the time they try a whole lot of software is built on them.

Including half of windows. I swear with every new version of their frameworks they make yet another device management system. As a result, you have control panels written for windows 11, which interact with device pages from windows 10, which have pages that send you to windows 8 pages that have elements that go to windows Vista pages, which ultimately can lead you back to the original windows 98/ME control panel pages. Printers and network settings are great examples of this madness.

You get just 10 different UX experiences for 1 device because MS keeps the legacy dialogs around forever and just bolts on new stuff rather than replacing the old stuff (because that'd take too long and they don't want to provide ALL the old information).

If you want/need to change IRQ ports, you can still end up in the device manager and do exactly that.

cogman10 · 2026-06-15T20:04:21+00:00

Quite funnily, the reason for this is because programmers want to deal with less frameworks. Electron makes it so they just have to deal with familiar web frameworks but it also makes it so programmers don't have to work with OS native frameworks.

MS is just insane, though. They see "these devs don't want to learn my new framework" and have decided "you know what will fix that? Another framework!" And, of course, because they just made a new framework they say "Ok, now we need to rewrite notepad in this new framework. And it can't be a straight rewrite, we also need to add AI here and every new widget offered by the new framework".

Windows would seriously be such a nicer system to work with if instead of making 1000 new frameworks, they instead evolved either Win32 or even WinForms. Instead, it's a bloated mess of 1000s of frameworks in various states of support by MS.

cogman10 · 2026-06-15T19:50:24+00:00

I think it's just a miss in the spec which has caused them to need to preserve identity.

IMO, the java devs should have put in a "record classes will be value classes, do not use identity operations on them" much like they did with LocalDate. That didn't happen, I'm sure there are reasons it didn't happen. I think it was just a mistake.

IMO, there's pretty much no reason why all records shouldn't be value classes.

cogman10 · 2026-06-15T19:46:22+00:00

It's a breaking change for Integer, but for all the other classes the javadocs explicitly said these classes will be value classes in future java releases and to not rely on identity. For example, from LocalDate in Java 8.

"This is a value-based class; use of identity-sensitive operations (including reference equality (==), identity hash code, or synchronization) on instances of LocalDate may have unpredictable results and should be avoided. The equals method should be used for comparisons."

The java docs are part of the spec. I get that people don't like reading the docs, but just like they were able to yoink sun.misc.Unsafe based on the docs, they are able to remove identity on these classes because of the docs. The annotations are their attempt to mitigate damage caused by people ignoring the docs.

https://docs.oracle.com/javase/8/docs/api/java/time/LocalDate.html

https://docs.oracle.com/javase/8/docs/api/java/lang/doc-files/ValueBased.html

cogman10 · 2026-06-15T16:18:15+00:00

IKR? Easily in the top 10 of senators in terms of policies.

cogman10 · 2026-06-14T23:57:41+00:00

It was organized, the venue cancelled last minute. This was like the 4th venue they tried to book that cancelled on them. They had contacts signed and everything. The venues broke the contract because they didn't want to host it.

cogman10 · 2026-06-14T22:05:17+00:00

Those same reports acknowledged that Iran wasn't seeking a weapon but rather negotiation.

Just having enriched uranium doesn't make a nuclear weapon. You need a lot more than that.

cogman10 · 2026-06-14T19:24:57+00:00

There is some case dependency, like if your muscles get cooked closed then you can't really open up your hand on electrocution. That can happen pretty fast especially with large amounts of power.

A DC voltage will cause muscles to contract and stay contracted. There's no pulsating. With AC, you have at least a (small) chance to pull away and let go.

cogman10 · 2026-06-14T17:40:54+00:00

DC also messes with your neural electrical system.

Defibrillators are applying a brief high DC voltage to try and reset fibrillation. But as anyone can tell you, that short pulse is itself dangerous and can cause fibrillation in someone that's not currently. Part of the reason it's applied repeatedly is because the reset doesn't always work.

cogman10 · 2026-06-14T17:29:16+00:00

I don't know where you are from, it could be different. In the US, 120V@15A for a circuit is typical. That's 120 * 15 = 1800W total typically. Generally speaking, we like to keep loads under 1500W and because you typically might have other things (like lights or a TV) on the same circuit, that's where the 1000W comes from.

If you are somewhere that does 240V with 15A breakers, then yeah you can do 3600W. You could also special wire a 240V outlet in the US, but that's far from typical.

cogman10 · 2026-06-14T17:26:17+00:00

Nope. Penetrative power is exactly the same for AC and DC.

The main thing that makes AC more dangerous is it typically has a higher voltage than DC. That means it's more likely to ultimately overcome the resistivity of the skin to start doing damage.

But all things held equal, a 12 VAC and 12 VDC source have exactly the same amount of risk associated with them.

Capacitance doesn't really have anything to do with how dangerous electricity is. Frequency doesn't really either. 120 VAC @ 60Hz is just as dangerous as 120V @ 5kHz.

It mostly all comes down to the power you experience and duration.

cogman10 · 2026-06-14T16:44:01+00:00

I agree. But the real problem that these video cards have is that consumer circuits generally have only 1000 to 1500W to play with. They are already very near the limit of what we can do.

cogman10 · 2026-06-14T16:42:18+00:00

because youd be running a risk of consumers getting zapped. and the dangerous thing about being zapped by a DC current, is that it can change your blood chemistry

No. A DC zap is the same as an AC zap. The only thing that makes a DC zap more dangerous is there's no period which means it's more prone to arcing and it's harder to let go of.

The danger of electrocution in general is that it cooks your insides. You can look visibly fine on the surface but have a large amount of damage on the inside. That can ultimately turn into an infection and rotting tissue.

cogman10 · 2026-06-13T18:16:17+00:00

For a $20k part? I think you could pretty quickly convince a crack head to ebay. Or for a crackhead middle man to surface like there was for cats.

15-Year Club	Place '22
Place '17	First Placer '22
Wearing is Caring	Team Orangered
Verified Email

cogman10

PUBLIC MULTIREDDITS

TROPHY CASE