← Feed

Posts

• Post #3802335

  an admission and lukewarm take, apropos of nothing: I find the usual tech spec substructure of “options considered” and “pros and cons” really itchy I think it’s good-in-theory but in practice it becomes makework, & I’d generally rather see more focus on the problem statement!

• Post #1136739

  OK! Without further ado, here it is. Part 2 of "Understanding WASM", "Whence WASM", written to answer the questions "what makes WASM different from the JVM?" and "what exactly *is* a 'virtual ISA'". Please enjoy the attached footnotes and bibliography/list of relevant links! https://www.neversaw.us/2023/06/30/understanding-wasm/part2/whence-wasm/

• Post #903476

  I'm realizing all at once that what I really want from sqlx isn't `query_as(RowType)`, it's to query into a struct of arrays.

• Post #903475

  so I’m revisiting “data oriented design” (because —who knew?— structs of arrays actually work really well with sqlx) and this quote jumped out at me: “if you link your operations by related data, such as when you put methods on a class, you make it hard to unlink your operations when the data changes or splits, and you make it hard to split data when an operation requires it to be together for its own purposes”

• Post #903473

  This has been a fascinating experience, working on a rust service for $dayjob that ingests data whose shape and meaning in the domain was unknown to me at the beginning of the month. It’s been a lassoing experience: hold the data as loosely as possible (as json), then gradually define it as necessary. Opposite to most of my rust experience, where “thinking about the exact structure of the data” had been front-loaded.

• Post #903469

  redesigned my website. bonus main page content: git HEAD shots over the years. ever wondered what I looked like as an awkward teen? wonder no more: https://www.neversaw.us