3 ms·
I don't think I meant it completely in those terms. Rather, I am pushing "easier" in a term that is more in line with "cheaper." Consider, it is cheaper to re
by taeric 8y ago
I don't think I meant it completely in those terms. Rather, I am pushing "easier" in a term that is more in line with "cheaper." Consider, it is cheaper to reimplement a framework into javascript than it is to port the language demonstrating the framework into the web platform. (I'm thinking of the general "reactive" methodologies here.)
That said, I agree your point still stands. I was not trying to disprove it, but give it some complimentary points. That is, to help myself understand the point in the fine print, not just at the broad level. That make sense?
- mmt 8y ago> Consider, it is cheaper to reimplement a framework into javascript than it is to port the language demonstrating the framework into the web platform. I'm not sure I follow what you mean here, though I admit I'm quite inexpert in this area. My primary exposure/interest (especially in reference to the original topic) is that of a sysadmin who's done building and porting of mostly open source software on diverse Unix platforms and some of the integration of build tools (including compilers) into existing processes... long long ago. > That make sense? It does. I don't think we're really disagreeing, either, just exploring the ideas around this.