Oddbean new post about | logout
▲ ▼
deeznuts | 3 months ago (raw) | root | parent | reply | flag 
 JSON to struct syntax looks like trash and is so verbose

Everything in the current project I am on is incredibly verbose. Duplication is the way. Maybe this is the project designer’s fault?

I could build this system in python in 1/10th the amount of code
▲ ▼
mleku | 3 months ago (raw) | root | parent | reply | flag 
 yeah encoding/json is my most unfavourite, and the struct tags and the whole problem around json is a big hassle, that's partly why so much of my efforts this last 6 months have been involving json

you can't actually use my library with standard JSON interfaces either, because that syntax assumes you don't care about generating memory garbage and the use of stupid strings
▲ ▼
mleku | 3 months ago (raw) | root | parent | reply | flag 
 i prefer go's approach to structs but json is literally diametrically opposed design philosophy
▲ ▼
deeznuts | 3 months ago (raw) | root | parent | reply | flag 
 Sadly, 99% of the internet is “stupid strings” 😂
▲ ▼
mleku | 3 months ago (raw) | root | parent | reply | flag 
 indeed, and i'm not a web dev i'm a server dev, my early background with Go was actually forking btcd (which is why you will sometimes see me raging against that dumpster fire)

anyway, that wasn't even the problem with my recent work on a nostr relay, and fiatjaf has made a big note on his go-nostr repo alerting to the fact that his code does not handle goroutine lifecycles properly