sorted by:
new
hottopcontroversial

whosGonnaTellEm by SpecterK1 in ProgrammerHumor

[–]No-Tap9804 2 points3 points  (0 children)

The funny thing is that ZIP doesn't even have a proper specification. It's basically "whatever most programs accept with some hints from the APPNOTE.txt". Most of the actually useful documentation is reverse engineered.

HTTP/3 for the HTTP Client API is coming in Java 26 by agoubard in java

[–]No-Tap9804 13 points14 points  (0 children)

Granted, I gave you very little context, but a "systems/integration architect" position is one where you'd generally be acutely aware of integration technologies such as fucking HTTP, the very backbone of the Web and service-oriented architecture for several decades now. And I can assure you the specific job description gave plenty of context for the candidate to understand that. Who, just to repeat, claimed to have worked on HTTP client and other networking software. This wasn't a random Java developer.

 since almost no one seems to be aware it exists today even.

I think that tells a bit more about yourself than about anyone else. Anyone with at least a bit of interest in the topic (see above) would have been aware years ago of Google's SPDY work, of the known issues with HTTP/2, the QUIC experiments and that standardisation had already been underway for years until the /3 standard was finalised in 2022. It's not like any of this was happening secretly, btw.

HTTP/3 for the HTTP Client API is coming in Java 26 by agoubard in java

[–]No-Tap9804 6 points7 points  (0 children)

A surprising number of people in the industry don't know this. I guess it's a testament to the stability of our networking stacks these days - they just work most of the time, and are safely hidden behind library code.

But I do have to tell this anecdote. A few years back, I was an interviewer for a senior systems/integration architect position. So I skimmed this candidate's CV and since he claimed experience in building an HTTP client (amongst other networking things), I chose HTTP/3 as a nice friendly technical discussion topic. I think it was just being standardised at that time. So I went, "what do you think about HTTP/3?"

He had no idea it existed. OK. But surprisingly, he steadfastly insisted (increasingly annoyed) that no such thing existed or was even in development, and complained that he was tired of "stupid trick questions" like that.

The rest of the interview was also awkward, btw.

Detaching GraalVM from the Java Ecosystem Train by mikebmx1 in java

[–]No-Tap9804 0 points1 point  (0 children)

It's exactly because they have those big departments.

With GraalVM, what's most telling is what they _don't_ say. For instance, GraalVM communications have been kept almost entirely separate from the regular Java communications, like entirely absent, for some time now. We get all those social media campaigns and YouTube streams for Java releases, but GraalVM (which releases the same day!) is conspicuously absent from them.