11–20 of 103 posts
Submitting files with this form encoding is of course going to have the base64 overhead, but otherwise this looks great!
It amazes me that we're now at the point of standardizing sticking array references inside strings and yet we're still not having a serious discussion about what comes after HTML.
Can we just get rid of HTML and replace it with JSON while we're at it?
> wow[such][deep][3][much][power][!] And there goes my interest for this submission. Don't use overused memes in a submission. Liking the idea though.
It reminded me of that show that makes me laugh on Netflix.
It also illustrated the point that he was trying to make. I prefer warm examples, rather than ones using book titles.
They're still working on XForms after 10 years http://www.w3.org/MarkUp/Forms/
Isn't that kind of like saying "They're still working on HTML after 23 years"? Technically you're right, but version 1.1 of XForms was completed and published over 5 years ago. That said, XForms is dead AFAIK, and that's not a bad thing.
It amazes me that we're now at the point of standardizing sticking array references inside strings and yet we're still not having a serious discussion about what comes after HTML.
Earlier quoted context omitted.
What's wrong with a human-readable serialization format?
Nothing - I was talking about this:
Since these same servers failed to establish a consensus (Django using "a=1&a=2" as array, whilst php uses "a[]=1&a[]=1", for example), someone has to start ...