Re:Show HN: I benchmarked six Go SQLite drivers (found you d...
by cvilsmeier on Wednesday December 13, 2023 @09:14AM
(#38627640)
Maybe because Go devs are more allergic to 'non-Go' solutions that Java devs are to 'non-Java' solutions? (Explain: Java's xerial driver is a DLL/SO wrapped in a Java library)
[ Parent
| on HN ]
Re:Show HN: I benchmarked six Go SQLite drivers (found you d...
by lmz on Wednesday December 13, 2023 @09:28AM
(#38627819)
Also because there's a mismatch between goroutines and C threads as described here https://www.cockroachlabs.com/blog/the-cost-and-complexity-o... while Java threads can map 1:1 to C threads.
Re:Show HN: I benchmarked six Go SQLite drivers (found you d...
by butlerm on Wednesday December 13, 2023 @11:54AM
(#38630151)
Perhaps someone should define a new C compatible threading API to allow C libraries (including glibc or a wrapper around glibc) to work with something other than native pthreads. Such as goroutines or Java threads and so on.
Re:Show HN: I benchmarked six Go SQLite drivers (found you d...
by morelisp on Wednesday December 13, 2023 @02:04PM
(#38632513)
Many general M:N threading solutions have been tried over the years. As far as I know current thinking is still that you need substantial cooperation from a language runtime to make it worthwhile. (And even then it's hard - Java's first attempt failed and they went 1:1 essentially between 1998-2022.)