4 ms·
This fits really well with a pet peeve - that "data" is used by various frameworks to mean everything from a request body to file contents to a stream of databa
by l0b0 8y ago
This fits really well with a pet peeve - that "data" is used by various frameworks to mean everything from a request body to file contents to a stream of database records. It is always possible to be more specific than "data". Conversely it's really confusing to deal with two different "data" in a single piece of code.
- deleted 8y ago[deleted]
- trustmath 8y agoIt's hard to say which layer you are working with without having to know the whole model. You can always look at data as initial to what is computed, but 1. That's not much different than looking at the code and 2. Everything that is initial probably can be defined in terms of what computed it, unless you want to draw some arbitrary wiggly line between perception and act of taking a record or something like that, in which there are tons of use cases where one defines the other, no matter what sort of nomenclature you start with.
- fierro 8y agoit sounds like what you're describing is encoding. It's all bits, right, and the nature of the data (the thing itself) is determined by the way you assign meaning to those bits. Can't really blame frameworks for operating in a specific data model.