3 ms·
I worked on similar applications in my past. My understanding this requires "arcane knowledge" is because most frameworks and developers simply don't care. All
by lmilcin 7y ago
I worked on similar applications in my past.
My understanding this requires "arcane knowledge" is because most frameworks and developers simply don't care. All new languages and frameworks are built to supposedly make things easy and fun and counting your objects or calculating your buffers isn't exactly fun.
Making things dynamic and hiding underlying memory layout is seen as a tool to write software faster but it disconnects developers from understanding what actually happens and makes it even more difficult to write reliable software.
If writing software the correct way was prevalent this would not be arcane knowledge but common sense.
- diroussel 7y agoThere is possibility that you could write software at a high level and the compiler and tool chain could compute all the static allocation at build time. It could even save the plan as an output to be reused. You could run an optimiser yo optiate cache and memory usage. If a human can do it, then an advance tool chain could do it. Probably too expensive for most use cases.
- lmilcin 7y agoThis is done routinely for embedded software.