- Prefers to be called
- Uses pronoun
- Perth Australia
- 6 years 2 months ago
- Last seen
- 2 weeks 4 days ago
@adeveloper Can you provide some examples of why that's needed and how that would work using a preference based system please? I'm not sure I understand the need or solution well enough to agree or disagree.
Without getting into a bike shed type argument about it, having strict datatypes as Vuo does makes it more functional than object oriented I think. I'm not sure if it has lazy evaluational the way QC does for example, another characteristic of a functional language. One of the problems though is the types aren't expansive enough as they stand (no lists of lists for e.g.) and users can only extend types by writing C code.
Any functional language thrives or dies on compositional expressiveness and the ability to create higher level functions from lower level functions. To me sub compositions are not really doing that yet in Vuo, it's too hard to manufacture higher level functions from lower level ones. With QC type Macros as an intermediary step for development I feel like it will engender more of that kind of coding. I agree having too many nodes on the canvas is a deterrent to major work in Vuo.
I'm not smart enough or skilled enough to know if Lambda's in Vuo could be implemented successfully or not. I'm just teaching myself Haskell after a 3 day training course for professional coders run by Lab61 in Australia — I was quickly out of my depth but am totally hooked on the concept of pure functional programming as the coding method of the future.
macOS zoom is a good workaround I hadn't thought of, Jaymie