2 ms·
I recommend reading: https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/ https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va...
by manx 2y ago
I recommend reading: https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/ https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va...
- specialist 2y agoIDK... I've done a lot of data processing. What the kids today call ETL. Plus some parsing (writing grammars). Here's my working taxonomy: Parsing for source code and protocols. Serialization when you control both ends. (Implicitly defined parsing of protocols.) Scrapping is data processing, more or less. Find and read a value, maybe transmogrify it, write new value. -- As for the OC, once the contract made a breaking change, the problem transmuted from serialization to scrapping. Maybe some future runtime system will successfully enable multiple live updatable schema revisions. (I've been pondering that gordian knot for decades. Anyone else remember "objected oriented databases" hype?) Until then, we're stuck in data processing hell.