@leo I think productivity has to do with how fast a developer can write an effective program. To make a language that has really high performance and really high generality, you could simplify define an interpreter that lets you choose from any programming language currently in existence and call this a 'language.' This can be really performant (because you have your pick of language) and really general (because you have your pick of language). But it is really low productivity, because to learn this language you have to learn the syntax of so many others, and no developer actually has the time to do this.
I think this might just be the ability of a parallel programming language to implement new parallel applications or features quickly and efficiently
Would the effectiveness of abstractions go into productivity?
@joshcho productivity could also be time spent in developing the application. Writing Python / Javascript code is definitely faster than writing good C/C++ code.
I'm confused why Python falls under a productive language but Java doesn't? Aside from some syntactic sugar aren't they both general purpose programming languages? And where would Verilog fit in this chart for example?
Please log in to leave a comment.
I'm a little confused with what productivity refers to for a parallel programming language