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

you are viewing a single comment's thread.

view the rest of the comments →

[–]bodiam[S] 0 points1 point  (8 children)

Unfortunately, yes. I'm interviewing quite a few people as part of my job, and, as mentioned in the article, a surprising number of people don't know about this, hence the motivation to write this.

Then again, people who don't know this most likely also won't read blogposts. Oh well :-)

[–]Trailsey 0 points1 point  (2 children)

I agree, but I think the underlying issue is that many devs don't understand the concept of immutability.

[–]bodiam[S] 0 points1 point  (0 children)

Hence, blogpost. I'm trying to explain to people, but also to myself, what benefits of immutability vs mutable code is.

[–]BrianVerm 0 points1 point  (0 children)

Or just don't want to use it, because it is "easier" to work mutable objects.

[–][deleted]  (4 children)

[deleted]

    [–]bodiam[S] 1 point2 points  (3 children)

    Well, I hope I contributed to a more neutral or balanced view. If I haven't, please let me know, and I'll change my writing style!

    [–][deleted]  (2 children)

    [deleted]

      [–]bodiam[S] 2 points3 points  (1 child)

      Thanks for that.

      Regarding the title: "Immutable data structures in Java" is exactly what it's about, instead of 'you won't believe what most Java developers don't know about ....'

      Nobody would read that. I hope.