3 ms·

> A UI framework is not an algorithm I think it is. A framework is a pattern of behaviors. You have inputs, transforms, and outputs. Some are connected, some y

by jack9 9y ago

> A UI framework is not an algorithm I think it is. A framework is a pattern of behaviors. You have inputs, transforms, and outputs. Some are connected, some you leverage by use case - standard library of a utility or core namespace (e.g. from flask import jsonify)

seanmcdirmid 9y ago
You have those, but you don't have core algorithmic property of an effective method that can be computed within a finite amount of time and space. It isn't even very meaningful. In the meta sense, you might be able to come up with an algorithm that makes connections automatically, but then...it is meta. Unifying algorithm and architecture has been somewhat of a holy grail of PL, being able to express your whole program (including your frameworks) as just procedures would be very convenient, but no one has figured out how to do that.
- jack9 9y ago
  > you don't have core algorithmic property of an effective method If a software framework doesn't have idioms, I'm not sure it's a framework. Examples of frameworks that have no case for using it dont do well.
  - seanmcdirmid 9y ago
    It’s more like it doesn’t make sense. Of course they have idioms, but idioms are not deterministic decision methods.
    - ArchTypical 9y ago
      Don't be dense. How a controller in an MVC framework maps to a url and provides an execution path through the framework is an algorithm. The fact you plug in multiple values to make that happen (including the executing function) is the idiom that results in a consistent algorithm. You can alter this, which isn't a compelling argument.
speedplane 9y ago
A UI framework is better understood as an algorithm plus a psychological model of your user. You must understand what they are thinking at every step of the way, guide them to the answers they want, and help them avoid pitfalls. This is by its very nature a less deterministic solution than a pure algorithm.

by jack9 9y ago

seanmcdirmid 9y ago

You have those, but you don't have core algorithmic property of an effective method that can be computed within a finite amount of time and space. It isn't even very meaningful. In the meta sense, you might be able to come up with an algorithm that makes connections automatically, but then...it is meta. Unifying algorithm and architecture has been somewhat of a holy grail of PL, being able to express your whole program (including your frameworks) as just procedures would be very convenient, but no one has figured out how to do that.

jack9 9y ago
> you don't have core algorithmic property of an effective method If a software framework doesn't have idioms, I'm not sure it's a framework. Examples of frameworks that have no case for using it dont do well.
- seanmcdirmid 9y ago
  It’s more like it doesn’t make sense. Of course they have idioms, but idioms are not deterministic decision methods.
  - ArchTypical 9y ago
    Don't be dense. How a controller in an MVC framework maps to a url and provides an execution path through the framework is an algorithm. The fact you plug in multiple values to make that happen (including the executing function) is the idiom that results in a consistent algorithm. You can alter this, which isn't a compelling argument.

speedplane 9y ago

A UI framework is better understood as an algorithm plus a psychological model of your user. You must understand what they are thinking at every step of the way, guide them to the answers they want, and help them avoid pitfalls. This is by its very nature a less deterministic solution than a pure algorithm.