[nim-dev] Re: Nim vs Scala (not holywar). Compare functions for strings
- From: wulfklaue <wulfklaue@xxxxxxxxxxx>
- To: nim-dev@xxxxxxxxxxxxx
- Date: Sun, 17 Jul 2016 12:12:48 +0000
Some things, owing to their prevalence, in my opinion have to be part of
standard library of language. For example, the string methods\functions
toCharArray, getBytes, reverse are in many languages.
The problem is, when is enough... I can think of a dozen things i like to see
in Nim. But they are all not essential. At some point there needs to be a lock
down on functions, so a 1.0 version can be reached. Because as long as 1.0 is
never reached, there will be no broad pickup of the language. The helper
functions you mentioned above can easily be added to the language on later
versions.
Unification of methodes across external modules is a different topic then the
helper functions. And i do agree, the more unified calls are the more easy for
people to learn. But external modules like nimfp, tuples are maintained by
other users. So that kind of invalidates your point. Araq has no say over how
other developers create there own modules. If those modules get merged into the
Nim standard library, then sure... they must be updated to reflect the default
behavior.
Remember Garry, a lot of the constructive criticism that you point out can be
addressed after 1.0 release.
- Helper function: Can be added after 1.0
- Tuple improvements. Can be done after 1.0
- Including other modules as standard libraries ( with standard constructs ). I
am starting to sound old ... 1.0
The main focus now needs to be:
- Stable! There are like 750 bug reports still open. While not all are
critical, the focus needs to be reduction of those.
- Documentation ( one of my problems with Nim, especially for the more "exotic"
functions where the docs are very basic ).
All that ties back into a 1.0 release. The basic idea was ( from what i read )
to have 1.0 is 2015! We are already half past 2016 and from the open bugs etc
it will be surprising if there is a 1.0 release in 2016.
The issue goes beyond 1.0. As Nim keeps stalling with no official 1.0 release,
GoLang, rust etc keep build up there communities. Trust me, its no fun being a
"obscure" language when a few big one's run with all the glory. Because this
directly influences the developer base. Do not think that Araq will be able to
keep doing Nim core development for the next 10, 20 years. At some point more
people will be needed for core development. And that goes back to having a
large community.
Qua features Nim is very much 1.0. So the focus is bug fixing and 1.0 release.
Simple as that.
Other related posts:
