Why creating primitive wrapper objects is a bad idea??

Question

Autoboxing over instantiating primitive wrapper objects

Answer 1

Autoboxing is intuitive and requires less code.
Character ch = 'a';
Vs
Character ch = new Character('a');
Simple unboxing.
char c = ch;
But, you may not need to wrap your primitives if used in a way that doesn't make sense. Wrapping requires and consumes extra space in memory and likewise will slightly slow down you code during lookups and possibly conversions.
However, when it is need to use a primitive like type with a data structure or method etc that uses Generics, a type that inherits from the Object class is required.
So, it's not a bad idea to use primitive wrapper classes, bit you also should only use them when needed and when needed and possible use autoboxing/unboxing in lieu of more verbose and possibly less intuitive code.

https://stackoverflow.com/questions/27647407/why-do-we-use-autoboxing-and-unboxing-in-java

https://crunchify.com/java-tip-wherever-possible-try-to-use-primitive-types-instead-of-wrapper-classes/

Answer 2

ChaoticDawg thank you so much I now see the point ...

Answer 3

I'd just use autoboxing
Character ch = 'a';

Answer 4

ChaoticDawg about the example you used earlier.. on
Character ch = new Character("a");
And
Character ch = a;
Which one is the best to go around ?

Answer 5

Ohhk... So that you avoid creating objects in memory that already exist.