Comment by lock1
4 days ago
That's needlessly aggressive. Ignoring webapps, you could do gamedev without even knowing what a matrix is.
You don't even need such construction in most native applications, embedded systems, and OS kernel development.
4 days ago
That's needlessly aggressive. Ignoring webapps, you could do gamedev without even knowing what a matrix is.
You don't even need such construction in most native applications, embedded systems, and OS kernel development.
I am working in embedded. Had to optimize weights for an embedded algorithm, decided to use linear regression and thus needed matrices.
And if you do robotics, the chances of encountering a matrix are very high.
To be fair, I do use matrices a reasonable amount in gamedev. And if you're writing your engine from scratch, rather than using something like unity, you will almost certainly need matrices
Even when using some game engine you need some prior knowledge. Otherwise you are just throwing stuff at the wall and see if it sticks.
I really doubt this.
Even through UE blueprints (assuming the most high level abstraction here) you will come across the need to perform calculations with matrices. While a lot is abstracted away, you still need to know about coordinate spaces, quirks around order of operations, etc.
This is my exactly point. Even in a highly specialised library for pricing securities, the amount of code that uses matrices is surprisingly small.