Name: Anonymous 2013-06-19 2:04
After see several fragile designs adoted by several libraries written in C, I realize that parallel/multithreaded programming can teach a lot about API design to newbie programmers, such as:
* Avoid global variables
* The best way to make two, initially unrelated, programming parts comunicate with each other
* The implications that a decision has on flexibility, safety and performance (usually all they care is ease-of-use)
* Migrate easily to other programming models/idioms/paradigms (such as functional, event-driven, ...)
Should computer science students learn parallel/multithreaded programming from the beginning? What do you guys think about this idea?
* Avoid global variables
* The best way to make two, initially unrelated, programming parts comunicate with each other
* The implications that a decision has on flexibility, safety and performance (usually all they care is ease-of-use)
* Migrate easily to other programming models/idioms/paradigms (such as functional, event-driven, ...)
Should computer science students learn parallel/multithreaded programming from the beginning? What do you guys think about this idea?