4 ms·
rust would be more appropriate if your intention was to use this in production. Databases ad GC don't mix well. (its done but it makes tuning a nightmare) As m
by cultofmetatron 7y ago
rust would be more appropriate if your intention was to use this in production. Databases ad GC don't mix well. (its done but it makes tuning a nightmare)
As much as I love rust, its learning curve is high and I'm sure Op doesn't want to spend half his article teaching all the intricacies of types and the borrow checker. Go is easy to learn over a weekend so its probably a better medium for illustrating the concepts as everything is laid out simply.
- arendtio 7y agoSometimes I wonder how Go would look like with a borrow checker...
- eatonphil 7y agoTruth is I've written about how to parse in better languages before (JavaScript, Python, Standard ML, etc.) and I wanted to figure out a good approach for doing it in Go. As for databases and GC, you may be right but there are still major databases out there written in Java for example. https://www.quora.com/Which-databases-data-stores-are-written-in-Java https://www.quora.com/Which-databases-data-stores-are-writte...
- matttproud 7y agoA garbage collector is not inherently incompatible with a low-latency database. I was generally very happy with the performance of Go's garbage collector enough to have built Prometheus, the time series database, on it back in 2012, when the collector was considerably more naive. https://blog.golang.org/ismmkeynote https://blog.golang.org/ismmkeynote