They are niche and not that useful for General Programming tasks tbh. I get unsigned bytes but for ints just take a Long ngl

Bruh, I literally said C is faster and that there are different tools for different jobs, I am convinced you're either trolling or cannot read, either way, you are right, this is pointless

Funny, I thought your goalpoasting moving post was what se were talking about!

You just sound like a java fanboi lol, cheers and goodbye 👋🏼

Funny, I thought the same about your comment. Your original complaint was that java lacks unsigned ints, given that's what you said, that's what I thought we were talking about

What a load of goal post shifting lol.

We're not comparing to C, we're comparing to a theoretical java that has primitive unsigned ints since that was your original complaint. Ofc C is faster, java is faster to write than C though. I write both, there are different tools for different jobs

I understand that reasoning but the dude literally forgot to add uints. Which is funny I think. Then they never fixed it (this math library stuff is just a weird band aid).

Today it is less important I guess, but back then it sure wasn't. I also don't really care what C# specs say, that has nothing to do with the story IMO.

If you do C bitwise operations on big chunks of data (like encryption) Java is probably more than 1000 times slower 😁

Eh, if you use the API, I just go up a size and use bitwise operators, the JIT is fast enough that it's usually not a problem. Definitely not 100x slower

Iirc, the decision was made for performance reasons and reducing programmer confusion. Even in the .net world, unsigned ints are against the CLS spec and using them in c# has compiler warnings. Really the only reason to care about unsigned ints is reducing memory footprint...which case Java shouldnt be your choice lang to begin with.

So you don't need it means it's okay a major feature is just forgotten for 20 years? I'm not even criticising you, I'm criticising the language lol.

Just 100 times slower lol

Eh. I rarely use unsigned integers, and using 4 extra bytes for large numbers is nothing when the jvm is already chugging RAM... So lacking uint isnt that big deal. Though, why is a byte signed...? That is beyond me.

I have written a lot of code that would benefit from primitive unsigned ints...and while it is a little more work to do it java's way, it's definitely not a horrid mess

Yeah so it doesn't. That's just a horrid mess.

If you'd know your history, uints were forgotten in the first version, and never added.

Java has support for unsigned integers since java 8... its just in java's fashion, they are methods bolted onto the standard Integer class instead of proper unsigned primitives.

Yeah as an OCPJP7, Oracle loves to squeeze hard on this shit. Costs an insane amount of money, and you have to re-do it for each version.

they changed the release schedule to be once every six months as opposed to every two years back in 2017; typically, this means each release is smaller in scope too

don't even know what it means to be certified just for a specific Java version, sounds kinda silly

Kind of glad I didn't get certified for Java 8 a few years ago. I've been away from Java for a bit and had no idea we were already at 27.

Man, how is netbeans doing these days? I moved to JetBrains ages ago but always hoped netbeans could become something great. Maybe I'll need to check out the new release.

Just a casual 200k lines PR, 3k commits

But still, getting a HelloWorld app down to 6.5MB; is it just me or is that still rather bloated for all but the most elaborate "hello world" programs?

But you're including a runtime and standard libraries in the executable. go produces largish binaries for small applications as well since it's statically compiled and includes the go runtime.

We're not using floppies anymore.

This is huge! I'll admit I'm one of those who effectively gave up hoping this would ever merge. Glad to see it finally getting into the mainline!

Substack. AI illustration. 🙄