I2P-Easy-Install-the-Movie VS onramp

My goal for the past several years has been to make I2P easy to use. Like really easy. Right now, I2P is easier to use than ever. The I2P Easy-Install Bundle for Windows will fully automate the configuration of I2P and an I2P browser on Windows systems. I'm also working on Unzip-and-Go Portables with an example build here to make I2P as straightforward as Tor Browser.

This has been changing: https://eyedeekay.github.io/I2P-Easy-Install-the-Movie/

There are routers in Java and C++ right now. I am better equipped to support Java router users. Many applications can simply be forwarded into I2P from a server, configured to answer requests that come from I2P, just like an .onion service on Tor more or less. For more sophisticated apps, hooking an external I2P router(one that is already installed and running) using the SAMv3 API offers more flexibility. There are dozens of SAMv3 API libraries for dozens of languages, like 5 in python, at least 4 in Go, at least 2 in Rust, at least 1 in Ruby, at least one in Typescript, there are a bunch. I'm a Go developer sometimes and I've put a ton of effort into making the Go libraries exceptionally easy to use, onramp is as easy as I can make I2P application development in Go at this time(and it's pretty easy). I'm way less good at Python and/or C++.