What's new in Java 15?

[@omprakashhivre4519]

Very good explained 👍

[@laurspilca]

Code on GitHub: github.com/lspil/youtubechannel/tree/master/welcome-java15

[@raghuvardhansaripalli9636]

nice video and its a touch up for java 15 new features. Thank you ..god bless you..

[@javacoder1986]

Thank you for posting this informative video.

[@s1mpl3_]

7:47 even darker joke for the current situation would have been if you called the class Bat instead of Cat

[@laurspilca]

:))

[@ahadporkar7355]

Thank you

[@xs2farooq]

What are the practical examples / design patterns of local interfaces and local enums?

[@laurspilca]

Good question, Muh. I honestly don't know where and if we'd ever use this. But it's possible this implementation is done as a prerequisite for some new features which will be implemented in next Java versions.

[@BinSlayer1]

Hi Laurentiu. I was wondering what your opinion was about sealed classes. I guess to me they look like they have more security, but they seem to completely break DIP and low coupling principles, don't they? Unless I'm missing something I don't see how they can be used in professional coding. I would say they are on the same level as the instanceof operator.

[@laurspilca]

Now they also look like a little bit overengineering to me. But I don't want to make the mistake to say they're not useful yet, or that they might not become a successful feature. Let's see how they'll be embraced in the future by the community. It's hard to say something about a feature you have no experience with. We have to wait for a little and see if it finds a place in the ecosystem.

[@vadympylypchenko5801]

In my opinion, the Sealed classes and interfaces can make a big mess in the real project.

[@sharifyy]

Thanks for the video. Doesn't non-sealed keyword violate the whole purpose of sealing a class?

[@jakobkmar]

Only classes with permission can use non-sealed when inheriting from sealed classes. This way sealed classes can allow implementation for just the classes with permission - now these classes are normal (non-sealed) after having implemented the original sealed class.

[@laurspilca]

@@jakobkmar I think Mohamad means (correct me if I'm wrong) if B extends A and A is sealed, if I make B non-sealed it could be extended by C, but this way C is also an A. So you can write A a = new C() even if A is sealed for B. That's actually an interesting question. I'd like you leave me more time to see how will these new sealed classes evolve before coming with a good answer. Or, in more decent words: I don't know how to answer yet :))

[@jakobkmar]

@@laurspilca Well B still needs the permission from A. So the developer who writes class A has to think about which classes to give the permission to.

[@sharifyy]

@@laurspilca yes! exactly I mean that.

[@jakobkmar]

@@laurspilca Wanted to add: You said "you can write A a = new C() even if A is sealed for B" which is wrong, because (sry for writing this the third time) B needs to be listed at the "permits" list in A (and then A is NOT sealed for B). If this is not the case, then "A a = new C()" (actually it fails earlier at B extends A) would not work - so this "problem" does not exist :)

[@cinzacaful]

Wow...nice video! I am learning C# and C# had "sealed" classes and I am happy to see this in Java. Can we use the generic data structures with the primitive datatypes instead of the generic classes? ex: ArrayList list = new ArrayLis();

[@laurspilca]

In java you cannot use primitives for generic types. At least not yet. But I know some projects already work for this so we might have this possible in future releases.

[@cinzacaful]

@@laurspilca Thanks for the answer! 🥳

[@_dallas_]

the intro just made it sound like the video has ended, i got so confused...

[@saikrishnakaushik2869]

lmao

[@rey6253]

Oh fck, the sealed classes are horrible on the way how they are implemented. Why would u have to explicitly permit every class to extend it ?! In c# it is much better implemented.

[@lowercaseguy3578]

pls fix ur audio , the beginning raped my ear!

[@laurspilca]

Hey. Sorry for this. I'll check out what's happening.