dashborg-go-sdk VS hibiki

Ya, I understand your concern, and I may change the license going forward if it causes too much confusion. The intent is that those use cases would be totally fine (unless 3rd party users are literally writing Hibiki HTML code). My intent is more of a temporary anti-cloud-poaching license because I intend to integrate Hibiki into my hosted internal tools platform - https://github.com/sawka/dashborg-go-sdk .

Golang SDK - https://github.com/sawka/dashborg-go-sdk

Yes! This is exactly how I feel too... all the Javascript frameworks just make everything more complicated! You should check out https://github.com/sawka/dashborg-go-sdk ... built because I wanted there to be an easier way to build modern looking tools without setting up a frontend stack.

Hey Mike. This looks great. Just want to say, unrelated but, I'm a big fan of your Hibiki HTML(https://www.hibikihtml.com/) and wish you would resume work on it at some point. Any plans on that front or is it feature complete? Will you fix bugs if they are discovered? Any way, will try Wave out this weekend, keep up the good work.

While building out (https://github.com/dashborg/hibiki), I have code like this to parse raw HTML:

Well, I'm obviously not a lawyer, but that definitely was not my intent when I said offer "hosted version of Hibiki HTML" :/ . I meant hosted, like offering a service like Netlify, Next.js, or Heroku or as an integrated development experience (not like a CDN). Also it is 100% fine for anyone to use Hibiki on Netlify or Heroku or any generic hosting service.

Since it was already confusing, I'll work on clarifying that point specifically in the future. https://github.com/dashborg/hibiki/blob/main/LICENSE , tried to make it clear that any generic hosting was fine, and also 100% free if it is used for internal tools.