@hba6018
Magnificent giant mustache and amazing Java 🙌👏
@shannonkohl68
His point about the difficulty of API design is even more than the presenter may realize. As one of those guys who has programmed in Java almost 30 years, I recalled that the Collections framework was added before autoboxing. So as originally designed, you could not call myCollection.remove( 1 ); without forcing it into an Integer. So in a sense that was a design issue introduced after the original design was done. According to Grok, Collections came out in Dec 98 (Java 1.2), with autoboxing following in Sep 04 (Java 1.5).
@RafayAli117
One of the best technical speakers
@larjasoul
Legendary teacher.
@prunge
It's intersting that Vector, the predecessor to ArrayList and the collections API, had better naming for its removal methods - removeElement() and removeElementAt()
@edwardharman1153
For the List remove(int) and remove(Object) collision - I think it is worth mentioning the history of the language, and how these existed before generics and auto-boxing were added.
@kokosensei5231
Thank you for share!
@MichaelSchuerig
I don't agree that lambdas always have to be pure. The point of using forEach is to cause side-effects, otherwise you could remove it. However, if you're in a parallel context, you should probably restructure the code to use map with a pure lambda instead. If you insist on forEach, better make sure that the code executed by it is thread-safe.
@MidnighterClub
I love this talk. He's using vi as his editor.
@KogularajK.
Probably, dont need java for my life (I'm a math major).. But, here I am just for Mr. Venkat's way of presentating..
@Narfanator
He's back in my algorithm!! 🎉🎉
@shavarshshahoyan
awesome talk and energy, thanks a lot
@ramakanaveen
Venkat’s talks are always interesting. Thanks for this.
@andmal8
Very interesting. Thank you!
@__nitinkumar__
@32:00 what was the issue here and why? I can this it is because of passing onUppercase and not using collector. But I want to more info, what exactly did parallelStream did that caused it.
@fabianmerki4222
parallelStream paid me a super nice lunch once - where a dev "guaranteed me" that parallelStream is not the culprit ... it was :-) thank you peter!
@ahuramazda9202
I just realized how great Go and C are as languages without an overloading mechanism.
@angelokezimana
Interesting talk
@justsignmeup911
Great lecture. Very enjoyable.
@sunilpilani9260