Відео

Don’t treat Integer objects like the primitive type. Use the primitive type in preference. Check for null if needed and get the primitive value for comparison.

Small Fun Fact: you can access the Integer Cache via Reflection. Just add a static Code block and rewrite the Cache with random numbers and enjoy the Autoboxing chaos unfold

Object types store memory addresses, not values.

Nice content, keep up the good work 🛐🛐

keep them coming.. nice content

Spent most hours in my college days. They never said this😂😂

TECHNOLOGY IS AWESOME🗣🗣🗣🗣💯💯💯💯🔥🔥🔥🔥

Great video

Integer myGirlFriends = -1; xD ...;(

another reason why Java is one of the most retarded languages

Okay, but... _why_ do you need an object version of a primitive data type, anyway?

Avoiding Java at all cost

[edit: dang, youtube interpreted the underscores as indicating italics. Does youtube support escaping characters? Apparently not quite.] Seems to me like Python has the right idea here: use “is” for checking if the lhs and the rhs are the same object, and use “==“ to do lhs.\_\_eq\_\_(rhs) (or rhs.__req__(lhs) if lhs has no __eq__ attribute, maybe. Idk if Python actually has a __req__ thing, as I believe Object has a default implementation of __eq__ , so it would only fail to exist if you removed it?). Or I guess your language could use “===“ in place of “is” if you prefer sigils to keywords. Having == check for identity for type Integer seems inconvenient without a good reason.. (other than possibly legacy code, I guessss…)

Always, always, always... use programming language that doesn't introduce such illogical behavior.

Why doesn't Integer implement __eq__() to override ==? ... oh.

i know why. (without watching.) Autoboxing and Integer.valueOf(n) will return a cached Integer instance for values -1 to 100 (IIRC), so those Integer objects are the same instance. For 900, it's a fresh Integer instance each time. You're using reference equality rather than Integer::equals so it's returning whether it's the same instance, regardless of value.

tldr: Java is broken

Hey this is a great video, make more!

That's why C++ is still one of the most reliable languages out there. C++ offers full control over a lot of things including cache. I chose C++ because it's the only language I know. 😅 There are surely more than one language offering this much freedom.

This shouldn’t be an interview question, it should be a question for the C-Suite of any company that thinks it’s a good idea to build critical systems using Java.

Ok so, int does not stand for interger... What is int then?

Integer in Java is a Class. Next Vídeo.

Only reason I use java is android studio and majority of help on internet are in java.

My brain is overloading

😀 at 0:36 this is German TV actor Walther Hoffmann performing in popular wedding soap

so it almost acts like a 7 bit integer 💀

== checks for the same address, equals checks the actual object state or value. It’s not that hard idiots. You can even override equals to do whatever your lame javascript franework using ass desires

Java seems cursed. I already didn't like it and refuse to use it because it has no concept of unsigned integers (ICK!) but this is even worse. James Gosling should have been slapped with a trout when he was designing this cancer of a language.

Me when I use C# and don't need to use a wrapper class for primitives because generics support the usage of primitives.

Having implementation details affect the result is horrible design.

Wow, super cool video.

nice explanation

The same as LUA, you need to know how the VM works to program it. That's stupid.

And people go crazy about JS ;)

Does this occur in C# as well? Cause' they are very similar languages.

Wonderful

Javascript: Perhaps we are related (==,===)

For those wondering why you would need to use wrapper classes for primitive types: 1. Only `Object` types can be modified when passed as an argument to a method. 2. `Object` types can have null value. 3. Generic types only allow `Object` types. 4. Can call multiple methods, like `compareTo()`, `equals()`, `toString()`, etc. 5. Cloning and serialization are only supported for `Object` types. 6. Objects are needed to support synchronization in multithreading.

The fffff okay i saw such in python but there is with "is" statement, Java absolutely weird on this, tf i should care, am i not comparing values?? Who tf even made Integer class and why?? Use freaking int, wtf is Integer ahha??

What a retarded design

Because Java isn´t a serious programming language

We often miss details when learning a language; these videos fill that gap. please do upload more videos like these :)

That's interesting but if i got that as an interview question i would leave the interview. A good reason why to use .equals through. But then just have that as a rule in your code pipeline so your team all have the same level of best practises.

Thx

This is the stupid of Java side 😂 and it's inherited on Kotlin too 😂

that's mad silly.

Never touched java before, I've learned from this vid that I'm not gonna touch it ever

why would you use Integer instead of int in the first place

I knew there was a reason I never bothered to learn Java. YUCK. I hope Scala isn't repeating this same type of nonsense.