Time |
S |
Nick |
Message |
05:03 |
|
|
df0 joined ##friendlyjava |
09:05 |
|
aditsu |
pdurbin, philbot: ah, wb, let me repeat what I wrote earlier |
09:05 |
|
aditsu |
hmm, lambdas are great, but they seem to clutter the call stack a lot.. |
09:05 |
|
aditsu |
also see http://blog.takipi.com/the-dark-side-of-lambda-expressions-in-java-8/ |
12:13 |
|
pdurbin |
aditsu: I see what you mean. So you've using lambdas a lot? |
12:16 |
|
pdurbin |
yeah, philbot and I were offline for a few hourse yesterday: http://i.imgur.com/V8msfL9.png |
12:17 |
|
aditsu |
pdurbin: not a lot, but I started using them here and there.. I'm coding some algorithms recently, and getting a bit worried about the size of the stack |
12:17 |
|
pdurbin |
I'm not sure what happened. To fix it I power-cycled the Digital Ocean droplet. |
12:18 |
|
pdurbin |
I let Netbeans go ahead and change simple for loops into lambdas. That's about it, so far. |
12:19 |
|
aditsu |
oh, I didn't know that was a thing, I'm only writing lambdas intentionally |
12:20 |
|
aditsu |
although I suppose an automatic refactoring of single-method anonymous inner classes would be useful |
12:23 |
|
aditsu |
streams still feel very foreign to me though.. |
12:24 |
|
aditsu |
I wish they did more functional stuff on collections directly, rather than adding that stream "layer" |
12:26 |
|
pdurbin |
Hmm, what I hear is that the main way that one uses lambdas is via streams, that streams are the real user-facing feature. Yeah, it's an extra layer. |
12:49 |
|
aditsu |
I'm using them more like general tasks or callbacks |
12:52 |
|
aditsu |
and implementing all those little interfaces, like Comparator |
13:00 |
|
pdurbin |
cool |
17:37 |
|
|
mr_lou joined ##friendlyjava |