3 ms·
Effectively one is comparing library performance here and not language performance. Granted, that line can get very blurry indeed, but in this case this says ve
by SeanDav 10y ago
Effectively one is comparing library performance here and not language performance. Granted, that line can get very blurry indeed, but in this case this says very little about golang the language and far more about a current implementation of one of the golang libraries.
- jonlawlor 10y agoIt is kind of both; go doesn't allow some approaches in native go code that can make it slower than other languages. (I love go, but that is my experience.) In this case the choice to use utf-8 everywhere, including in the csv delimiters, is making it slower.
- weberc2 10y agoThis isn't what makes CSV parsing slow, there's nothing about Go that requires you to deal in UTF8.