trying to be synthetic, but I have enjoyed the exchange, there is material to 
untangle in multiple threads here. :)

  * on concepts: looking forward to your write up!
  * on compiler errors: yep, they can get bad, with some experience they become 
better to navigate, still could definitely be an area of improvement. an howto 
guide on compiler errors should be much welcome.
  * on nimcrypto: ok, now if I can see where you come from and the gist of the 
criticism. maybe some of your remarks could end up in issue in the repo. how to 
use crypto is definitely more difficult and require special expertise than how 
to implement crypto.
  * on making random a secure call: I guess one of the advantages of current 
call to random is that is fast and a secure version would necessarily be 
slower. current one is based on some variations of xoroshiro that aims for 
speed and statistical quality and still would be the one to use for example in 
monte carlo simulation in a scientific context. whether the default is the fast 
or the secure one I guess it could be up to debate (and not sure I am sold on 
this) and an alterantive could be provided: secure_random or fast_random. 
pretty sure that for nim 2.0 the ship is already sailed though (it is frozen 
and only bugfix mode).
  * developer onboarding/slimming stdlib: I also would tend to prefer a fat 
stdlib instead of a slim one but I think the hard argument there is that there 
is not enough manpower currently and I think this is a lesson hard learned by 
core devs, so it seems a fair choice for this 2.0 iteration. the theme on 
trying to ship some nim distribution of libraries is something that has come up 
and fusion is indeed recognized as a failed experiment (unfortunately). 
centralizing stdlib like iface and others (e.g. pattern matching) I think is 
not feasible until those libraries get a decent amount of usage as nimble 
package (and yes, with such a young ecosystem it is hard to avoid the risk of 
having to rewrite because of obsolete dependencies).
  * on foundation: no progress that I know of. this is a topic that I think 
would advance better with a group of people in the same room (and some prep 
work). of course a new thread on that topic would not hurt. nice to hear about 
the expert connections, they might turn useful! thanks for the availability!


Reply via email to