The words of every C programmer who created a CVE.
But others might be amazed that I'm around 40 years old and have never owned a car.
I do not live that far from an Amtrak station but there is only one train a day, it takes forever, and does not go anywhere that I am typically traveling.
The train moved at a frustratingly slow speed (< 10 mph) for probably 30% of the trip, but aside from that I liked the more relaxed atmosphere of the travel and it was overall more comfortable.
The train itself was a bit bumpier than I expected and the wifi was not very good. Those things and the slow speed would mean I could not imagine taking a much longer trip than this one. With the extra time and hassle of dealing with an airport, this one balanced out as probably only being slightly slower travel but it was less expensive and more relaxed. If it were Seattle to San Francisco, as an example, the slowness would be too much for me. The comfort and amenities like wifi and food would have to be a lot better than they are.
It provides client and server API. The latter is used by Gerrit for its server. https://www.gerritcodereview.com
Not sure what the Java to WASM story is if that is a requirement for what they need.
Reading this article and the comments here ... I do not want to think, other than being glad it was too expensive to consider.
My point, since you replied to my post, was simply that prior to GitHub, none of the other sites for OSS were trying to achieve the same goal. The goal was to establish a specific OSS community for a set of projects. SourceForge was a bit of an outlier in that a lot of projects used their distribution network, if they were not part of a foundation like Apache or Eclipse that had extensive mirrors setup.
SourceForge was never the main development and collaboration site for any of the major efforts happening around OSS.