this post was submitted on 23 Mar 2025
266 points (98.2% liked)
LinkedinLunatics
6540 readers
2 users here now
A place to post ridiculous posts from linkedIn.com
(Full transparency.. a mod for this sub happens to work there.. but that doesn't influence his moderation or laughter at a lot of posts.)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I suppose immutability is a solution, I'm not sure if it's a good idea to radically isolate everything though
I get the idea, and how you keep it from copying a lot of data unnecessarily. A radical approach would be using immutable types exclusively
Clever! But I'd worry to run into performance problems when some operations effectively require copying or becoming a sort of linked list.
Although I suppose you could also be explicit if you do need it to behave in a particular way.
I like it!
You are absolutely right. And that would be easier to maintain too. Thank you for the insight!
That is definitely handy, and easy to make lazy if required. I might have a look into scala