Gradual steps or paradigm shift towards easier concurrent apps?
Herb Sutter's distinguishing argument is for a gradual evolution of programming languages and techniques (IDEs, APIs) towards easier concurrent program development.
My take on this is that we can only do gradual evolution right now because we don't really know how to do easy concurrent programs, i.e., we don't have an adequate programming language yet, but gradual is not sufficient (because still too difficult) and we will need a completely different language, asap.
Gradual steps may take us there eventually but what we will have once we get there will be a paradigm shift, a completely different type of programming language.
I propose that the new language that we try does concurrency by default and that in general a programmer will have to write specific instructions in order to bypass the built-in concurrency features and get a non-concurrent process or structure.
My take on this is that we can only do gradual evolution right now because we don't really know how to do easy concurrent programs, i.e., we don't have an adequate programming language yet, but gradual is not sufficient (because still too difficult) and we will need a completely different language, asap.
Gradual steps may take us there eventually but what we will have once we get there will be a paradigm shift, a completely different type of programming language.
I propose that the new language that we try does concurrency by default and that in general a programmer will have to write specific instructions in order to bypass the built-in concurrency features and get a non-concurrent process or structure.
0 Comments:
Post a Comment
<< Home