5 ms·
I like it. Is there a term for the opposite situation? Where you're operating in a declarative environment, what you want to do should be possible, everything
by jjoonathan 11y ago
I like it. Is there a term for the opposite situation? Where you're operating in a declarative environment, what you want to do should be possible, everything similar to the thing you want to do is possible, but your particular use case is excluded due to lack of foresight/manpower/understanding by the authors?
(Obviously not entirely specific to non-Turing-complete environments but they tend to be the worst offenders and the hardest to work around for obvious reasons.)
- binarymax 11y agoNot an opposite situation, but avoidance of this issue (mostly related to management of state) is outlined in the fantastic paper 'Out of the Tarpit' - which in my opinion every developer should read at least once. http://shaffner.us/cs/papers/tarpit.pdf http://shaffner.us/cs/papers/tarpit.pdf
- plonh 11y agoIronically, that 66 page document is a massively overcomplicated discussion of the simple idea that inessential mutable state causes problems.
- PaulHoule 11y agoFunny enough I have been doing a deep dive on production rules and logic programming lately, facing up to why the technology has not caught on more than it has. One thing I find is that novices are creating rule bases that form infinite loops and that the CS community has been paralyzed by the fear of infinite loops and poor scaling for particular reasoning chains. Working with mainstream languages, however, I don't find infinite loops (or Turing's Halting Problem) to be all that relevant and the big reason is that the mainstream languages that people like to complain about already have structures built in that make infinite loops less likely to happen.
- deleted 11y ago[deleted]