do not use yaml. do not support the propagation of yaml. say no to 300 page specs for fucking plain text storage god damnRE: https://w3c.social/@w3c/116216070362563670
Timeline
Post
Remote status
Context
6 do not use yaml. do not support the propagation of yaml. say no to 300 page specs for fucking plain text storage god damnRE: https://w3c.social/@w3c/116216070362563670
We need to shut down all working groups until we can figure out what's going on.
@vic i had an anneurism seeing this. the spec for json is like 1 page.
if you must go whitespace then consider nestedtext. it doesn't have embarassing issues like the norway problem.
if you must go whitespace then consider nestedtext. it doesn't have embarassing issues like the norway problem.
@icedquinn @vic AND json5 already exists to fill this exact niche while also having other neat upsides (backwards compatibility with regular json data and using perfectly valid ecmascript syntax)
@icedquinn @vic i mean fuck its the json-ld working group i shouldve expected this they're the reason activitypub is impossible to implement right
@icedquinn @coolbean @vic activitypub is impossible to implement because it's incomplete and everything you need to complete it is out of scope (authentication/authorization, trust model, etc etc)
fedi is a nightmare to interop with because everyone filled in the gaps differently and even worse they use the little that *was* specced in ambiguous and nonspecific ways instead of defining their own terms or using the terms as officially defined (and then the behaviors are basically totally undefined)
json-ld group is doing yaml-ld because believe it or not, some people actually asked for it and intend to implement it (as well as cbor-ld) so they have an actual mandate for doing this and didn't just decide to do it on their own
fedi is a nightmare to interop with because everyone filled in the gaps differently and even worse they use the little that *was* specced in ambiguous and nonspecific ways instead of defining their own terms or using the terms as officially defined (and then the behaviors are basically totally undefined)
json-ld group is doing yaml-ld because believe it or not, some people actually asked for it and intend to implement it (as well as cbor-ld) so they have an actual mandate for doing this and didn't just decide to do it on their own
Replies
1