4 ms·
one step at a time people will realize mainstream imperative programming and its derivative has been a long waste of time
by agumonkey 5y ago
one step at a time people will realize mainstream imperative programming and its derivative has been a long waste of time
- nerdponx 5y agoI don't think that's a valid conclusion here at all.
- agumonkey 5y agothe amount of code that was - point to a structure / object - declare a variable - access the object / structure field and assign it to var - repeat for every information you want to extract from the struct / object is large and now replaced by something transparent
- Espressosaurus 5y agoIn what way is multiple assignment and tuple unpacking not imperative code?
- sitkack 5y agoAssignment is not necessarily mutation. Every language, including functional ones can assign values to names. You have unlocked +1 reductionist pedantry.
- agumonkey 5y agoYou might never create any actual variable, you point to access/ reference reads passed to other functions. Of course in python it's only syntactic sugar but bit by bit culture will evolve.
- nerdponx 5y agoMemory-managed and dynamically typed programming languages already solve this boilerplate problem mostly. If anything, the primary advantages of functional programming languages are not functional purity, referential transparency, or elegant abstractions; but HM-style type systems, typeclasses, and tidy succinct syntax.
- agumonkey 5y agoI believe HM was derived from structural and purely functional experience.