4 ms·
Before I'm willing to concede a particular, very restrictive definition about what "FRP" is, it would be nice to first see a model of it that does not contain f
by jerf 13y ago
Before I'm willing to concede a particular, very restrictive definition about what "FRP" is, it would be nice to first see a model of it that does not contain fundamental logical contradictions acknowledged by the author. Last I knew nobody had a continuous, perfectly sensible model of FRP in theory.
Further, given the lack of extant model, it's very silly to get pedantic over the term, and end up insisting on a meaning which has not been demonstrated to be practical and therefore one must consider the possibility will never turn out to be practical. It is not out of the question there exists some fundamental mathematical problem with the strict definition of FRP and therefore it must inevitably turn into a family of techniques.
This strikes me as sort of like insisting that you don't have OO unless you fully support access control via "private", six months before the first release of anything that actually supports "private", and all along it turns out that access control is fairly orthogonal to OO anyhow.
If I am out of date and somehow FRP has settled on a consistent model (without this fact being trumpeted on /r/haskell, where I would have heard about it), then it is, at the very least, still awfully young to be getting this pedantic about what is The One True Definition; it could only have been proved to be not immediately impractical, not yet proved practical.
- edwintorok 13y agoCan you expand on the contradictions? Is there a link where I could learn more about them?
- jerf 13y agoNo, I've never dug in enough to understand. I'm much more in the "wait and see" camp about FRP... if it works, great, I'm glad someone's thinking about it, but the philosophical spirit in which it is being approached rubs me the wrong way (and after a few tries, I can't seem to write my characterization of that philosophy in way that doesn't sound insulting or sarcastic, so I'm going to have to leave it there, sorry). YMMV.
- seanmcdirmid 13y agoEncapsulation (and it's twin sibling identity) is completely essential to OO, otherwise you are just using objects as poor man modules.
- jerf 13y agoThere are a ton of perfectly OO languages with little to no language-enforced encapsulation. You're sort of proving my point... if you're going to insist that if you don't have that you don't have OO, you've got an awful lot of language communities to go explain to them that their language isn't OO... hopefully you've got some explanation of what it actually is, too, that makes some sort of sense.
- seanmcdirmid 13y agoEncapsulation isn't just information hiding, though I guess that is how people usually grok it. The essence of an object is its identity, with identity you can own things like state, but then that state needs to be protected. In a pure system, this identity is problematic: all values are are identified simply by their structure, and state would be unheard of. We might try to fake it by providing identities manually (see immediate-mode UIs), but then you are just trying to build objects again anyways. Do you have values that you can name and talk about independent of their structure or how you get a handle to them? Yep, those are objects. I think most languages that claim to have objects actually have objects, the bar is not high! What is more problematic are communities who claim not to have objects, like the entity component people, or the functional programming people who start passing around numeric/string based identifiers to "solve expressiveness problems." But they are just in denial in that they have recreated objects. Note that information hiding, what we more generally understand as encapsulation, is not even meaningful without objects. So if your values don't have identity, it is only their structure that is important, and then it doesn't make sense to hide that structure without chopping it off of the value itself!