The fact that 99% of my RPC and event serialization has to be done in json is blowing my mind.
Where did we go wrong??
“It’s so simple” they say, wtf?
The fact that 99% of my RPC and event serialization has to be done in json is blowing my mind.
Where did we go wrong??
“It’s so simple” they say, wtf?
@mnl 🌶️ take: in a lot of ways, XML was and is better than JSON: it has far better tooling around it (schemas, XSLT, etc), and is still at least somewhat human readable… but everyone decided they hated all the angle brackets, so instead we got JSON.
@graydon @edmistond which is why we have json and json schema and json ld and bjson and oO
@edmistond @mnl Everybody decided they hated the parse time, if one is being charitable. Everybody decided they hated having to think in trees, if one is being practical. Everybody decided they hated having to follow complex rules when their intent was simple, if one is being unkind.
@graydon @edmistond @mnl "Instead of regarding the obligation to use formal symbols as a burden, we should regard the convenience of using them as a privilege: thanks to them, school children can learn to do what in earlier days only genius could achieve." - Dijkstra
He was criticizing the idea of programming in natural languages. Now that that has arrived, it is clear he was right.
@mnl Do you have a favorite JSON-datamodel-like binary serialization out of JSONB, BSON, BJSON, UBJSON, CBOR, MessagePack, etc?
Asking partly because it's hilarious that we as a community haven't decided, in fact we're so undecided that at least two of these have IETF RFCs, and partly because you might actually have a preference and offer some insight. 😃
Depending on the use case:
- XML
- protobuf/flatbuf/any decent binary serialization (much easier to handle)
For readability and human consumption: YAML
@mnl Do you have an alternative format in mind?
@joesabin I’m kind of fine with code bloat, in the sense that we can build software that does a lot more. But json parsing is just… complex, feature-poor and json is an infuriating format and not even that readable to boot.
@mnl Yes, and code bloat has been caused by thinking memory will expand exponentially forever.
This is the direct consequence of “I program with vim and 80s unix tooling is the best we’ll ever need” thinking, imo
@mnl @graydon @edmistond look at machine learning systems, which the very rich, who resent talent they don't have and can't buy, hope to replace actually knowledgeable people with. They're fine, until they start hallucinating, and then they're not fine at all.
If we want correct software, we have to use precise formal systems.
@ravenonthill @graydon @edmistond how is it clear that he was right?
Even as programmers, we program in natural language all the time, in documentation, comments, variable names, rfcs, GitHub issues, planning meetings, etc…
Dijkstra himself was a great natural language communicator, if it weren’t for his cheap quips.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.