3 ms·
I think you're referring to confirmation bias which is related but not quite the same. Never the less I understand what you're getting at. I took it to mean tha
by agentultra 12y ago
I think you're referring to confirmation bias which is related but not quite the same. Never the less I understand what you're getting at. I took it to mean that the kinds of problems a programmer encounters is not sufficiently random to properly determine the usefulness of a given language or "paradigm." Which may keep people from switching to new, better tools (or from trying them out at all).
The data-oriented design thing is interesting and something I've heard come and go over the years. Check out:
http://www.dataorienteddesign.com/dodmain/ http://www.dataorienteddesign.com/dodmain/
and
https://www.youtube.com/watch?v=ZHqFrNyLlpA https://www.youtube.com/watch?v=ZHqFrNyLlpA
A video demonstration of Jai; a new compiler from Jonathan Blow designed around this paradigm.
Cheers!
- SomeCallMeTim 12y agoAhh, I see. Yeah, I guess I meant that each paradigm is inherently a different value for different domains, and so therefore has a different value for programmers who specialize in their domain(s). And when someone checks out a paradigm that doesn't match their domain, they may end up complaining about how the tool isn't good. Love the links. Listening to Blow talk now. Will look at the longer book later.