Nim is a statically typed programming language which compiles primarily to C and has an excellent performance/productivity ratio. Nim's design focuses on efficiency, expressiveness, elegance.
Nim's performs well in performance benchmarks, offers powerful metaprogramming capabilities and is easy to write, leaning on Python syntactically.
Tags
programming language, language, statically typed, high performance, compiler, metaprogramming
If you did not choose "veteran" in the checkbox, have you applied in the past? If so, for what year(s)?
Yes, for 2014.
If you chose "veteran" in the checkbox, please summarize your involvement in Google Summer of Code and the successes and challenges of your participation. Please also list your pass/fail rate for each year.
-
Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating?
Nim has been gaining popularity significantly in the last year, but we're still a comparatively small programming language. Participating in GSoC would have an enormous effect for us.
We hope to give students a chance to get a deeper look into Nim and learn a lot. The interesting projects will also benefit the Nim community. GSoC students should afterwards be ready to keep contributing to the Nim ecosystem.
How many potential mentors do you have for this year's program? What criteria did you use to select them?
We picked motivated mentors with experience and a deep insight into Nim and their respective GSoC ideas. As the main mentor I have many years of experience teaching and tutoring university students in many programming and computer science subjects.
What is your plan for dealing with disappearing students?
This should be avoided from the start by explaining to the student thoroughly and making sure that the student understands what to do.
By regularly interacting with the student and getting feedback from both sides, problems can be avoided early. I believe this will significantly reduce the risk of a student disappearing.
What is your plan for dealing with disappearing mentors?
Our mentors are core members of the community, including Andreas Rumpf, the author of the Nim programming language himself. I highly doubt that any mentor would disappear since we don't take this responsibility lightly, but another mentor could jump in.
On our ideas page we're asking them to join our IRC channel and discuss potential ideas with us. It's very important for us to get in touch with students before, to make sure to find a fitting project for each student, and make them understand and help with their independent research. During the program we also expect the students to continuously interact with us via IRC.
Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here.
-
Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application?
