Yes, I heard that too. @Araq, are we still planning destructors and deterministic string/seq for v2 as previously said on the GitHub Wiki?
Oh, also @mratsim, possibly, certain parts of #7041's checklist are for v1, and others are for v2? The compiler infrastructure is underway already, after all.
- Nim's strings and seqs need to change so that nil is not a valid state but completing this implementation produced weird random crashes. Since the implementation should change to be based on destructors I thought it's wiser to not spend too much time on a moribund implementation.
- I figured out how to make these new seqs/strings work with the GC. No big breaking language changes, just a smooth transition process (well, I hope!).
So yeah, the v2 ideas are confirmed to arrive sooner than anticipated.
Roadmap should be easier to find firstly ;)
Would be nice to see some big goal or few smaller ones, just to realise vector of development.
To decide to spend time, I want to know what will going to happen.
Will there be cpp parser, python converter, maybe some backend for Vue/Nuxt, anyway, again, it would be nice to hear about ambitions of language.
Just watched google vid about swift, it looks bearable, but the most fascinating part -(it's going to android for killing java & kotlin)- is that it has some nice features, since Nim being a community driven project, I believe that we can make it better than some big corp's with a lot of restrictions =)
Nimpy can go pretty far though it doesn't support Numpy. It was already done in the past in nim though (https://github.com/jboy/nim-pymod#pyarrayobject-type)
We don't have a stable Jupyter nim kernel for the notebook like showed though we had many proof-of-concepts (https://github.com/stisa/jupyternim) and Jupyter is also one of the specific goals of the hot-code reloading work (https://github.com/nim-lang/Nim/issues/8927).
hot-reloading — is essential for any web frameworks
Colab IS jupyter: https://colab.research.google.com/notebooks/welcome.ipynb