No spark and k8s are configuration problems. Hard but you are not creating the tool, just configuring it. It's more of a dev ops /sys admin thing and, though I agree it's very hard, it's a very left field comparison IMO.
With engine creation you are creating the tool. It's programming through and through.
Though I can see how a lot of backend people are taking on the role of "configuring" stuff so it's hard to delineate backend programming away from it completely.
Still even when taking this into account, it is of my opinion that a rendering engine is significantly harder then even K8s or spark.
You are right though that with existing game engines graphics programmers are not as needed anymore.
> Hard but you are not creating the tool, just configuring it. It's more of a dev ops /sys admin thing and, though I agree it's very hard, it's a very left field comparison IMO.
They specifically are talking about creating the tool.
They're talking about the developers working on spark and K8? That's different. But I don't think they are talking about that. They are more likely talking about using these tools.
With engine creation you are creating the tool. It's programming through and through.
Though I can see how a lot of backend people are taking on the role of "configuring" stuff so it's hard to delineate backend programming away from it completely.
Still even when taking this into account, it is of my opinion that a rendering engine is significantly harder then even K8s or spark.
You are right though that with existing game engines graphics programmers are not as needed anymore.