|
|
|
|
|
by vanderZwan
2 days ago
|
|
This is why I switched to jsgist[0] years ago and haven't looked back since. It's very sparse, but it has also avoided feature creep as a result, and since the output is stored as a gist on my GH account I don't have to worry about losing it if the site ever goes down either. (also, the sister site jsbenchit[1] has been one of the more reliable microbenchmarking tools among the various sites I've tried - most end up triggering deopts or introducing "noise" in a way that makes the output less reliable) [0] https://jsgist.org/ [1] https://jsbenchit.org/ |
|