3 ms·
Lots of comments about this already, but the intent was that if you are writing Hibiki code then you are 100% ok. If you are using it for an internal tool, the
by sawka 5y ago
Lots of comments about this already, but the intent was that if you are writing Hibiki code then you are 100% ok. If you are using it for an internal tool, then you are 100% ok. The only part that is restricted is if you write a service that allows your customers to write Hibiki code (and you aren't a generic hosting service or cdn) that's not ok.
- KaoruAoiShiho 5y agoWhat if I'm something like shopify and I want to allow my customers to be able to use this in the website builder, is that okay?
- sawka 5y agoIf you're Shopify, please contact me :) But, for that example, it depends. So if Shopify adds Hibiki to their site, and then writes a custom module that integrates Hibiki into their API. And then they add a new tab to their webpage builder that says "write your form in Hibiki HTML", then no, that would not be okay. If they just have a generic form that accepts HTML, and makes no mention of Hibiki , and you manually add your HTML which happens to include the Hibiki script and runs Hibiki code, then there is no issue.
- electroly 5y agoI'm curious--why all the weird license stuff? I mean, I understand what it allows and doesn't allow, but why did you decide to do it that way? I don't honestly know if a non-open-source framework has a legitimate chance of success in 2022 with so many strong open source competitors. From the response here on HN I think you can see that this is a pretty major issue.
- catlifeonmars 5y agoI’m sure this is already mentioned elsewhere, but are you sure the nonstandard license is pulling its weight? IMO it’s a distraction. In many ways a license is very much part of a frameworks API.
- sawka 5y agoNo it isn't pulling its weight, it is a distraction, in that half the comments are about the license :)