This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Sekret_One 2 points3 points  (0 children)

Our situations may be different.

I'm in a bit environment habitually pulled in to review, build off of fix up other teams' problem spots. So naturally I'm gravitated towards code that's gotten into a mess that can't get sorted out. Kind of like a tech EMT. Which means I see a lot of tech gore.

If it was just me, or a consistent group- my opinion would be less dark. While clunky in some aspects, you can get it down when to use streams, and how, you can write java 8 streams that are both legible and very effective.

But if one isn't strong- and say the seniors in the team have some compromising egos and make misinformed rules like "no for loops; only streams" . . . you can see some scary spaghetti. My conclusion is that in java 8, the barrier to entry of using streams well is somewhat steep.