News for hackers. Stuff that matters.

A comment on Software Engineering principles to make teams better. Parent comment

Re:Software Engineering principles to make teams better by ketozhang on Wednesday June 30, 2021 @10:08PM (#27695631)
Immutability isn't so difficult to do with Python language itself for any object. The push back is culture and practice of "we are all adults here" and that influences the language to make it forcing immutability awkward.

For example, let's assign a constant variable to a sequence; should you do use list or tuple (FOO = [1,2,3] or FOO = (1,2,3) )? It doesn't matter, the constant capitalization discourages you to mutate it.

[ Parent | on HN ]
Re:Software Engineering principles to make teams better by travisjungroth on Thursday July 01, 2021 @01:03AM (#27696398)
I don’t want constants. I want immutability. The problem isn’t someone reassigning FOO. It’s them changing the data that FOO represents. So I’d love to just use Python and pass around tuples, strings, frozensets and a homemade frozendict, but the performance is terrible. Any change means a full copy of the whole data structure.
[ Parent | on HN ]
Re:Software Engineering principles to make teams better by dexterous on Friday July 02, 2021 @12:15PM (#27713437)
> The push back is culture and practice of "we are all adults here" and that influences the language

It's strange that a general idea expressing (assuming?) overarching maturity has led to quite so many petulant arguments, wouldn't you say @ketozhang?

[ Parent | on HN ]