46
edits
Changes
m
the compiler is getting faster and producing faster code;
there’s lots of examples, tutorials and documentation available;
→Pros and Cons of Using The Chapel
== Pros and Cons of Using The Chapel ==
===Pros===
the compiler is getting faster and producing faster code;
there are lots of examples, tutorials and documentation available;
===Cons===
The good news is that Chapel’s niche, unlike Julia’s, has no serious immediate competitor — I’d consider other productive parallel scientific programming languages to be more research projects than products — which gives it a bit more runway.
The Chapel team is doing many of the right things — the package is easy to install (no small feat for a performant parallel programming language);
and the community is extremely friendly and welcoming — but it seems clear that users need to be given more reason to start trying the language.
Small Number of Contributors
Admittedly, this is related to the fact that the number of users is small, but it’s also the case that contributing code is nontrivial if you want to contribute it to the main project, and there’s no central place where other people could look for your work if you wanted to have it as an external package. A package manager would be a real help, and it doesn’t have to be elaborate (especially in the initial version).package。
= References =
