Great video. We dumped Spring 4 years ago for Micronaut and never looked back. It has first class GraalVM support comping from Oracle Labs ;) Oh, heads up, string templates are being pulled in Java 23. Not even available in preview. Brian Goetz indicated this in an email to the JEP group.
Please, fix the sound quality, every time I click on your videos because of the interesting subject, after five seconds I'm gone, only because of the sound. It's so easily done! Thanks!
hi - I'm sorry to hear that. I don't know what else I could be doing. I've been trying for seven years now to please people's occasional complaints about the audio, and I'm starting to think they hate the sound of my voice! :) I use a Yeti microphone with a muffler and close all windows (though I live in one of the busiest cities in America, so there's going to be noise no matter what). I use Adobe's audio tools to clean things up. Maybe it's "easily done" for you, but I honestly have no idea what else I could do besides renting a dedicated, soundproof studio in San Francisco for an extra few thousand $$ a month. Thanks for baring with me for the few seconds you manage to stick around..
Thanks for answering! It's not your voice! ❤ I think you would come a long way with either speak closer to the microphone, or have some dampening in your room, don't need to be acoustic treatment, just curtains and a carpet and the usual stuff (if you already have that I don't know why the acoustics sound so bad). I promise you, it's much much harder to grasp Spring than to get a decent sound recording! 😊
and I promise you that I grasp Spring with ease but don't know how to get a more decent recording, as I've already got all those things you mentioned and no such luck...
I never know, obviously, @@IfeSunmola , but I have no doubt that this many people, over this many years, can NOT be wrong. I'm doing SOMETHING incorrectly. I just don't know what...
29:90 I love java, but man is it ugly and unintuitive nowadays. I just asked several java developers and they all struggled to explain or understand that code. Gatherer.Integrator.ofGreedy ... is this supposed to be intuitive? Lambda can help to produce nice code, but the language has so much embedded logic behind generic names like "map, scan, gather, filter, collect" now that it becomes pretty hard to read a lot of those function chains. It's a bit like code with bad/generic naming and structure - "filter" or "map" can mean a million things so now i have to read and understand everything. Sure, you can write functions with readable names and use them like "orders.stream().map(extractFirstItemFromOrder).toList();", but that's not what most devs do. Similar, ".stream().collect(Collectors.toList())" is nice in an abstraction sense, but the "stream().toList();" added later makes it much more readable... anyways.
you make a great point. I think that the Gatherer API is at a slightly low level. Most people won't need to use it, and if they do, then the extra complexity is worth using it since they wil have a very particular problem (building an operator that Java's stream API doesn't already have). I suppose it's a cost of doing business. When it comes to the other names, however, like filter, map, etc., I am not sure I agree. those names are very common in basically every other programming language; they're standards of a sort. It's like using the word 'read' to read the next byte in an InputStream. People from other languages would be very confused if it didn't say 'read'. Same for map, filter, etc: Python, JavaScript, PHP, .NET, Rust, Scala, Kotlin, Perl, etc, basically every language beyond straight C has these names (or sometimes other almost as common names like 'select') - map, filter, etc. I do agree that toList() is really quite nice.
Gatherers are heavily inspired by Collectors as an API, so learning the difference between the two should be straight-forward if one is already familiar with Collector. Custom definition of both terminal and intermediate operations is not something to be generally expected to be done frequently, especially since instances of Gatherer and Collector are re-usable. A small collection of predefined Gatherers is available out of the box. For more information about the design, please watch my Devoxx presentation from 2023 titled Teaching old Streams new tricks. Feedback on this Preview feature is most welcome. Cheers, V
Наука
Great video. We dumped Spring 4 years ago for Micronaut and never looked back. It has first class GraalVM support comping from Oracle Labs ;)
Oh, heads up, string templates are being pulled in Java 23. Not even available in preview. Brian Goetz indicated this in an email to the JEP group.
Great video. Thank you Josh!
Please put sections in videos.
Hi Josh, thank you for the presentation. It's really helpful and needed. Can you please let me know what is the IDE you used here ???
Hey Josh, Nice presentation as ever..indeed you are never going to be a born-again C coder😂
good stuf
Using WSL it should work in Windows.
Thanks Josh
Java 2022😅
Please, fix the sound quality, every time I click on your videos because of the interesting subject, after five seconds I'm gone, only because of the sound. It's so easily done! Thanks!
hi - I'm sorry to hear that. I don't know what else I could be doing. I've been trying for seven years now to please people's occasional complaints about the audio, and I'm starting to think they hate the sound of my voice! :) I use a Yeti microphone with a muffler and close all windows (though I live in one of the busiest cities in America, so there's going to be noise no matter what). I use Adobe's audio tools to clean things up. Maybe it's "easily done" for you, but I honestly have no idea what else I could do besides renting a dedicated, soundproof studio in San Francisco for an extra few thousand $$ a month. Thanks for baring with me for the few seconds you manage to stick around..
Thanks for answering! It's not your voice! ❤ I think you would come a long way with either speak closer to the microphone, or have some dampening in your room, don't need to be acoustic treatment, just curtains and a carpet and the usual stuff (if you already have that I don't know why the acoustics sound so bad). I promise you, it's much much harder to grasp Spring than to get a decent sound recording! 😊
and I promise you that I grasp Spring with ease but don't know how to get a more decent recording, as I've already got all those things you mentioned and no such luck...
I'm confused. The sound is okay, which time frame are you experiencing issues?
I never know, obviously, @@IfeSunmola , but I have no doubt that this many people, over this many years, can NOT be wrong. I'm doing SOMETHING incorrectly. I just don't know what...
29:90 I love java, but man is it ugly and unintuitive nowadays. I just asked several java developers and they all struggled to explain or understand that code. Gatherer.Integrator.ofGreedy ... is this supposed to be intuitive? Lambda can help to produce nice code, but the language has so much embedded logic behind generic names like "map, scan, gather, filter, collect" now that it becomes pretty hard to read a lot of those function chains. It's a bit like code with bad/generic naming and structure - "filter" or "map" can mean a million things so now i have to read and understand everything. Sure, you can write functions with readable names and use them like "orders.stream().map(extractFirstItemFromOrder).toList();", but that's not what most devs do.
Similar, ".stream().collect(Collectors.toList())" is nice in an abstraction sense, but the "stream().toList();" added later makes it much more readable... anyways.
you make a great point. I think that the Gatherer API is at a slightly low level. Most people won't need to use it, and if they do, then the extra complexity is worth using it since they wil have a very particular problem (building an operator that Java's stream API doesn't already have). I suppose it's a cost of doing business. When it comes to the other names, however, like filter, map, etc., I am not sure I agree. those names are very common in basically every other programming language; they're standards of a sort. It's like using the word 'read' to read the next byte in an InputStream. People from other languages would be very confused if it didn't say 'read'. Same for map, filter, etc: Python, JavaScript, PHP, .NET, Rust, Scala, Kotlin, Perl, etc, basically every language beyond straight C has these names (or sometimes other almost as common names like 'select') - map, filter, etc. I do agree that toList() is really quite nice.
Gatherers are heavily inspired by Collectors as an API, so learning the difference between the two should be straight-forward if one is already familiar with Collector.
Custom definition of both terminal and intermediate operations is not something to be generally expected to be done frequently, especially since instances of Gatherer and Collector are re-usable.
A small collection of predefined Gatherers is available out of the box.
For more information about the design, please watch my Devoxx presentation from 2023 titled Teaching old Streams new tricks.
Feedback on this Preview feature is most welcome.
Cheers,
V
Java 2022??
do u have mental illness? it's java version 22.....