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.)
No mutable types? So like.. no lists? no for ... i++?
I get that there are alternative approaches, but I don't quite see why you'd want to go to that extreme with this idea? It's useful for some applications but even for a simple video game it's likely not helpful.
There are non-mutable lists and every other data type.
https://docs.scala-lang.org/overviews/collections-2.13/overview.html
https://docs.scala-lang.org/overviews/collections-2.13/concrete-immutable-collection-classes.html
“for… i++” is easily replaced with a foreach, range, iterable, etc… in any language of reasonable capability.
I get that there are alternative approaches, but I don't quite see why you'd want to go to that extreme with this idea? It's useful for some applications but even for a simple video game it's likely not helpful.
I should've said that right away, really. That's on me being online while tired. At that time I did not really think outside the box I was working in that day
It's just a very common foot gun, especially in legacy code where it is not explicit in the design. Even when you have proper getters and setters, it's way to easy for someone to overload the scope of some object, either intentionally or accidentally and modify it inappropriately.
I suppose immutability is a solution, I'm not sure if it's a good idea to radically isolate everything though
Pure functional programming is often like this.
Or pragmatic functional programming, or rediscovered by “OO” programmers who realize they are messing up the Redux store bad.
Erlang/Elixir doesn't have muteable variables/types. Appending to a list would just create a "new" lists.
Good riddance.
Which is why he doesn’t have a company of his own. He’s a terrible leader.
I’m pretty in-line with all these.
“guru”-driven, fad, and ineffective management processes, misunderstanding and corporatization of low-overhead planning tools, rather crappy (and faddish) languages, and not putting team first - all bad things.
