3 ms·

> What should those interested in increasing productivity learn? Productivity for whom? And over what timescales? As I have been trying to say, it is not that

by willtim 10y ago

> What should those interested in increasing productivity learn? Productivity for whom? And over what timescales? As I have been trying to say, it is not that simple, you are oversimplifying. > So what is the claim, and is there actual evidence (even anecdotal) to support it? It sounds like you are completely satisfied with existing approaches, in which case there is little point in me trying to convince you. > The industry is extremely interested in anything that can significantly reduce the cost of developing software. Industry as a whole, does not have a good track record of adopting even good ideas in a timely manner. c.f. Garbage collection. So again, I think you are oversimplifying.

pron 10y ago
> Productivity for whom? And over what timescales? As I have been trying to say, it is not that simple, you are over simplifying. I'm only simplifying as much as the claims in the article. It's just pretty hard to understand what the claims about Haskell are given all of the vague hype. The article we're discussing says, "Haskell decreases development time by narrowing the scope of development to your domain." Obviously, I understand there are caveats, and it's unclear how big the savings are. I just want reports with some meat. > It sounds like you are completely satisfied with existing approaches, in which case there is little point in me trying to convince you. The question of being "completely satisfied" is irrelevant. I'm not a researcher and my goal isn't to dream up better approaches, nor do I have the resources to invest in experimenting with every new tool. I am, however, very interested if someone says they have a tool that can provide significant savings. If there were only some more actionable information, convincing me would be quite easy. I want to be convinced, but throwing general promises around serves to confuse more than enlighten.

by willtim 10y ago

pron 10y ago

> Productivity for whom? And over what timescales? As I have been trying to say, it is not that simple, you are over simplifying. I'm only simplifying as much as the claims in the article. It's just pretty hard to understand what the claims about Haskell are given all of the vague hype. The article we're discussing says, "Haskell decreases development time by narrowing the scope of development to your domain." Obviously, I understand there are caveats, and it's unclear how big the savings are. I just want reports with some meat. > It sounds like you are completely satisfied with existing approaches, in which case there is little point in me trying to convince you. The question of being "completely satisfied" is irrelevant. I'm not a researcher and my goal isn't to dream up better approaches, nor do I have the resources to invest in experimenting with every new tool. I am, however, very interested if someone says they have a tool that can provide significant savings. If there were only some more actionable information, convincing me would be quite easy. I want to be convinced, but throwing general promises around serves to confuse more than enlighten.