Java 17 to 20 Pattern Matching Full tutorial with Records, Instanceof and Switch - JEP Café #14 

Feel like I could watch this gentleman talk about Java all day long. This is my third video. Love the content and delivery!

Really appreciate these videos and the format of them! Thanks!

I like these kind of videos. Seems to me like finding hidden pearls to be used.

It gives me joy listening and learning from you. Thank you sir!

I'm really looking forward to Java 21

Nice and clear explanations. All I need now is a java cup ☕

Hi Jose, A great video! You are a great teacher. I love your courses on Pluralsight. Thank you and enjoy your Java coffee ☕ Lot’s of greetings, Dennis 🇳🇱

Around 11:00, I think switch(Shape shape) should be just switch(shape), with the variable previously declared... I'm enjoying the video enough to be trying examples with the Early Access release and old-school command-line javac and java commands!

Nicely delivered, clear and simple.

Cool, do you know what also is cool? The Java coffee cup you got! Would love to have one on my desk and flex on my colleagues : )

Thanks for the awesome video

It would be great if record patterns could be used on assignments like this: Point(int x, int y) = foo.getPoint();

Nice! Next steps: pattern matching in function and lambda arguments

Super Java evolution

Thank you so much for this video!

9:00 this is great. But the syntax is unnatural. I wonder if there is a syntactic better way to expose s to the rest of the method that is more clear.

Nice do you have a full course on Java core programming from A to Z thanks.

Adding features to java is making me an old man, how slowly it is going on.

In for(Points(double x, double y) : pts) instead of having to mention double data type every time it is better to provide a generic type so as to avoid exception while iterating. *Generic types can be bounded* One more thing is that there could be a third point for z-axis(double z) so there must be an overloaded constructor. So it is much better to have a vararg parameter. I don't how this will affect performance and memory. I haven't read the docs properly so it's just an idea from this video.

Fortunately we have Kotlin. In Kotlin code is more expressive.

Is it too difficult for the language to infer the type of o based on the assertion in the if statement so inside the if o is an string without the need of a new variable?

Would it be a good idea to be able to have more than one variadic parameter, such that one takes the odd elements and the other takes the even elements? Useful for Map.of

Will there be boolean only patterns when you've got a single type? E.g. List is Empty -> ... default -> ...

Why not release switch pattern directly? AFAIK, preview feature should be completed in 12 months

17:55 - `for` loop throwing exception if an `Iterable` is empty when pattern matching is used is just terrible, insane even, and is absolutely counter intuitive.

8:39 is really weird. Everyone that has used curly brace languages knows variables only exist in the { } they're declared in. Sure, it's not hard to wrap your head around it, but maybe it could have been done in another way ...

Pattern matching is required for functional programming. But this is anti-pattern in OOP (example with Shape is not in OOP style) And on practice people will use it for creating ugly procedural code

Java is looking very LISP with those Parentheses...

Happy to see that java is copying useful features from other languages, but worried it will ruin existing ones