this merges in a major refactor which scraps the Java prover, and re-writes the entire thing (i.e., client + prover) in native Javascript. There are many additional improvements, e.g. in client.js.
The advantage of this is that no external prover process is needed, and the entire thing can run in a browser (for example). the disadvantage is that proving winds up being slightly slower (by about 1.3-fold).
after this is merged, i might maintain a "legacy" branch that still features the Java prover. this could be desirable if you are extremely performance-conscious. However, by the looks of things the entire Java library will become deprecated. The best route forward might be simply to further optimize the Javascript prover.
benediamond
commented
5 years ago
this merges in a major refactor which scraps the Java prover, and re-writes the entire thing (i.e., client + prover) in native Javascript. There are many additional improvements, e.g. in
client.js.The advantage of this is that no external prover process is needed, and the entire thing can run in a browser (for example). the disadvantage is that proving winds up being slightly slower (by about 1.3-fold).
after this is merged, i might maintain a "legacy" branch that still features the Java prover. this could be desirable if you are extremely performance-conscious. However, by the looks of things the entire Java library will become deprecated. The best route forward might be simply to further optimize the Javascript prover.