3 ms·
The man is amazingly unbothered by things, and he writes really interesting notes, too. I started to get a sinking feeling. I searched around in the level for
by jodrellblank 18y ago
The man is amazingly unbothered by things, and he writes really interesting notes, too.
I started to get a sinking feeling. I searched around in the level for a view that would confirm my suspicion, and when I found a clear enough view of some angled geometry I saw the tell-tale mid-polygon affine swim in the texture as I rotated. They were using the software rasterizer on the iPhone. [..] The developers came back and said it [rewriting it for OpenGL] would take two months and exceed their budget.
[..] I told them to just send the project to me and I would do it myself. [..] my off the cuff estimate of "Two days!" was optimistic, but I did get it done in four
:D
- palish 18y agoTo be fair, it's probably 10x harder to repurpose someone else's code than to repurpose your own. So it probably would've taken anywhere from 40-60 days for someone else to do it. Plus, Carmack's code isn't exactly clear. :)
- pistoriusp 18y agoHave you ever gone back and looked at your own code that is ~2 years old? It usually takes some time for me to get familiar with what I was trying to achieve, I should comment more, but what I'm trying to get at is that code that ~18 years old is probably very different from the code you're making today.
- Hexstream 18y agoYes, however if you wrote the code you can remember "where things come from", why things are the way they are (you have a vague recollection of refactorings) and that helps for perspective. A third-party can't do that.