3 ms·
>In other languages, the abstractions and sweet (if helpful) syntactic sugar that attend the code conceal the heartbeat. IMO, that means they're failed abstrac
by Groxx 16y ago
>In other languages, the abstractions and sweet (if helpful) syntactic sugar that attend the code conceal the heartbeat.
IMO, that means they're failed abstractions and syntactic sugar. Proper ones should result in better understanding due to simplification - you can learn it in levels, easily encapsulating the knowledge at each level so you know you can "trust" what it's doing without having to remember all of it.
- rbanffy 16y agoAs such, any abstraction or syntactic sugar that distances you from the flow of the program fail. Bu that's for programs that are procedural. Functional programming has no flow. Truth neither moves nor changes. To use an analogy, a procedural program is like music, where rhythm and motion of the instrument are the essence of what you are representing. Functional programming is more like sculpture, where you create an elaborate piece that has no rhythm or movement of itself, but guides the flow and transformation of the data around it.
- Groxx 16y agoI haven't done functional programming really, I didn't think of that case. Interesting that it still seems to apply, though. If your abstractions in functional programs obscure that flow, they still strike me as a failure. Though I'd be interested in if functional programmers would disagree, I obviously don't know functional design patterns.
- silentbicycle 16y agoIf you reason about functional code with appropriate assumptions: they don't lie. A big part of functional programming is making code easier to reason about in isolation. If you want good procedural C code, read Lua. That shit is polished.
- rtaycher 16y agoI always thought that part of the reason that c sometime fosters a feeling that "syntatic sugar" is because it doesn't haven nearly as much ability to abstract things as other languages. Although this can be useful to some people in that things may be less context sensitive and more straightforward.
- j_baker 16y agoYeah, code without abstraction is good and works on a small scale. But on a bigger scale, it leads to not being able to see the forest for the trees. I want to be able to see the big picture while being able to dig up the smaller pictures if I have to.
- rbanffy 16y ago> it leads to not being able to see the forest for the trees And it's entirely possible the forest will end up being a beautiful one.