update README

README.md

@@ -31,7 +31,7 @@ As of now, it may be useful for checking the validity of simple estimations. The
 
 | Language                    | Time      | Lines of code |
 |-----------------------------|-----------|---------------|
-| C (optimized, 16 threads)   | 6ms       | 183 |
+| C (optimized, 16 threads)   | 6ms       | 222 |
 | Nim                         | 68ms      | 84  |
 | C (naïve implementation)    | 292ms     | 149 |
 | Javascript (NodeJS)         | 732ms     | 69  |
@@ -43,6 +43,8 @@ Time measurements taken with the [time](https://man7.org/linux/man-pages/man1/ti
 
 ## Notes
 
+### Nim
+
 I was really happy trying [Nim](https://nim-lang.org/), and as a result the Nim code is a bit more optimized and engineered:
 
 1. It is using the fastest "danger" compilation mode.
@@ -52,13 +54,32 @@ I was really happy trying [Nim](https://nim-lang.org/), and as a result the Nim
 
 Without 1. and 2., the nim code takes 0m0.183s instead. But I don't think that these are unfair advantages: I liked trying out nim and therefore put in more love into the code, and this seems like it could be a recurring factor.
 
-For the initial C code, I enabled the `-Ofast` compilation flag. Without it, it instead takes ~0.4 seconds. Initially, before I enabled the `-Ofast` flag, I was surprised that the Node and Squiggle code were comparable to the C code. Using [bun](https://bun.sh/) instead of node is actually a bit slower.
+Ultimately, these optimizations were also incorporated into the C code as well.
+
+### C
+
+For the C code, I enabled the `-Ofast` compilation flag. Without it, it instead takes ~0.4 seconds. Initially, before I enabled the `-Ofast` flag, I was surprised that the Node and Squiggle code were comparable to the C code. 
+
+The two optimizations which make more optimized code significantly faster than the naïve implementation are:
+- To pass around pointers to functions, instead of large arrays. This is the same as in the nim implementation, but imho leads to more complex code
+- To use multithreading support
+- To use the Box-Muller transform instead of using libraries, like in nim.
 
 For the optimized C code, see [that folder's README](./C-optimized/README.md).
 
+### NodeJS and Squiggle
+
+Using [bun](https://bun.sh/) instead of node is actually a bit slower. Also, both the NodeJS and the Squiggle code use stdlib in their innards, which has a bunch of interleaved functions that make the code slower. It's possible that not using that external library could make the code faster, but at the same time, the js approach does seem to be to use external libraries whenever possible.
+
+### Python
+
 For the Python code, it's possible that the lack of speed is more a function of me not being as familiar with Python. It's also very possible that the code would run faster with [PyPy](https://doc.pypy.org).
 
-R has a warm place in my heart from back in the day, and it has predefined functions to do everything. It was particularly fast to write for me, though not particularly fast to run :)
+### R
+
+R has a warm place in my heart from back in the day, and it has predefined functions to do everything. It was particularly fast to write for me, though not particularly fast to run :) However, I do recall that R does have some multithreading support; it wasn't used.
+
+### Overall thoughts
 
 Overall I don't think that this is a fair comparison of the languages intrinsically, because I'm just differentially good at them, because I've chosen to put more effort in ones than in others. But it is still useful to me personally, and perhaps mildly informative to others.