> Please can you quote some text to show who and what you're responding
to? I *think* you're responding to my post, but it's hard to be sure.
Sorry, I'm using the web UI which nests replies - I forgot this is a mailing
list! I was responding to your message.
_
I don't think we're saying anything different, I agree. The point I was making
was that _after_ loading the data onto a dataclass (or equivalent), you
wouldn't be able to unpack it. In JS, you can use destructuring assignment
when working with "classes" (and therefore well-defined APIs), which
This feature is far more useful in JS because JS objects double up as mappings
- Python dataclasses/attrs models/Pydantic models/named tuples/who knows what
are all represented by (typed) objects in JS/TS. As soon as you want to
describe your data e.g. by encoding it in a dataclass you'll no lo
