Changes

* the compiler is getting faster and producing faster code; . Comparable to OpenMP/MPI.* there are lots of examples, tutorials and documentation available; .* friendly community.

* Chapel's biggest problem in gaining users is the lack of a native Windows version.* Adoption* It’s , hard to escape the fact that Chapel’s gain user compare to another parallel programming platform.* User base is very small. * The good news It certainly will not be used in the IT industry for the near future(or ever) unless you are opening your own company and decided to try Chapel.* a small number of contributors to this open-source project. Much less support and update compare to other IT giants.* Projects based on Chapel is that Chapel’s niche, unlike Julia’s, has no serious immediate competitor — I’d consider other productive parallel scientific programming languages to be very little.* It's more for 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 languagenot as easy as other tools like OpenMP/MPI.* 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。package. ===Conclusion===* users have no much reason to start trying the language.