3 ms·
It is hugely significant when doing 3D coding if you want to use the convenience of vector and matrix types (and you really do because doing operations on raw f
by bhouston 13y ago
It is hugely significant when doing 3D coding if you want to use the convenience of vector and matrix types (and you really do because doing operations on raw floats it not scalable and it is bug prone.)
Background: I did a lot of 3D app dev in Java in the 1998-2001 time frame and then switched over to C#. C# was a huge improvement because it had value types. When you have 5M vectors, you really do not want each to be its own allocation.
- taeric 13y agoOh, I did not mean to imply it is not a huge factor where it matters. Probably makes a bigger difference in standard CRUD fair apps than people realize. My assertion is simply that compared to the cost of serializing to/from database/user, it is probably not the pain point of many programmers. Hence, most programmers probably don't think about it. Just ask a few developers about the ridiculous overhead of HashSet<Integer>. And then see how many places people still use it.