5 ms·

Can't understand the downvote for this reply... Also what Carmack said is definitely true within the domain he works in, performance is a major concern and wha

• RyanZAG 14y ago
  Performance isn't just a major concern in his domain - it's a concern in every domain. Why are you even trying to make an auto-threading compiler? Performance. If using immutable blocks that can be run in parallel performs worse than using mutable blocks in a single thread, then your auto-threading compiler is useless for its primary purpose: performance.
  • marshray 14y ago
    It's important to be aware of performance in every domain, but there are few domains where performance is always the overriding consideration. As Carmack said: Most of the time this is of only theoretical interest; we trade performance for productivity all the time
    • RyanZAG 14y ago
      I agree, but the idea of switching to immutable blocks in this case is so you can use auto-threading on the blocks. ie. you're switching to immutable blocks to increase performance through threading. If the immutable blocks don't increase performance through threading in excess of the loss from just using mutable blocks, then the whole exercise is wasted. Bolting on immutable blocks into C# is unlikely to have the same effect for readability as designed-around-immutability of Haskel.