So do you use JSON for your endpoints?
No we use XML
Oh interesting why is that?
Uhhh…no reason
Well SOAP is inherently evil so that just makes sense
What happens is that engineers look at a technology and say, this is too complex, I just need something simple. So they invent and/or adopt something simpler than the popular technology of the day.
But as they build more and more things using the technology, they realize that it needs more features, so those get added on. This happens over and over again to the technology with more and more features being added to it, until a new set of engineers look at it and say this is too complex, I just need something simple…
This is peak licensing
Wait I though the point of these post-opensource clauses (see also: anti-capitalist licence, WTFPL, etc.) was to scare off the big corporations lawyers and make sure your code won’t end up in AWS or something like that? Are Linux distros the only actors who are still giving a shit about licencing?
If you want to scare corporations use AGPL or, if you’re feeling spicy, SSPL. Do not use WTFPL, it’s too permissive.
https://opensource.google/documentation/reference/using/agpl-policy/
AGPL policy: Don’t use.
Exactly. It scares them.
OK but how can json have a license? I understand a particular json parser having a license, but how can a specification, which contains no code, even be considered “software”?
I’ll be downloading this one
The question on stack overflow: PHP Fatal error: Call to undefined function json_decode()
Every Villain Is Lemons
E.V.I.L
can we please pronounce that evil in a British accent: ivil
