Except when you're not worried about scale because you're building a small side project... I don't want to pay for a db (or the hardware to host it) for my play projects. My in-home play server is a very old home PC that is very underpowered for today's software.
Not sure I get what you're saying. Sqlite exists and works on very underpowered hardware.
Ah, yes... good old sqlite... I guess the main reason I go the route I go is that I like writing map/ reduce functions... much more than reorganizing tables because I structured them poorly to start.
In fact, the project I'm on right now at paid job has a lot of structure transformation... and I'm enjoying it so much that I'm not even pining for one of my million side projects.
While it's not the most performant way to do things, I feel like data structure manipulation is one of the easiest to read ways to get from point a to point b.
Except when you're not worried about scale because you're building a small side project... I don't want to pay for a db (or the hardware to host it) for my play projects. My in-home play server is a very old home PC that is very underpowered for today's software.
Not sure I get what you're saying. Sqlite exists and works on very underpowered hardware.
Ah, yes... good old sqlite... I guess the main reason I go the route I go is that I like writing map/ reduce functions... much more than reorganizing tables because I structured them poorly to start.
In fact, the project I'm on right now at paid job has a lot of structure transformation... and I'm enjoying it so much that I'm not even pining for one of my million side projects.
While it's not the most performant way to do things, I feel like data structure manipulation is one of the easiest to read ways to get from point a to point b.