Nokogiri's problems are compounded in that a lot of major Ruby gems still use it, so sometimes you can't get around the long build time. A new parser is only on

Nokogiri's problems are compounded in that a lot of major Ruby gems still use it, so sometimes you can't get around the long build time. A new parser is only one teeny tiny step towards fixing that problem. These are libraries other businesses now rely upon. Should the maintainers of this library risk the stability of the gem (and thus the reputation of the project) by swapping out such an important dependency? It's incumbent on the designers of the replacement and the community behind it to make such a case.