4 ms·
people will bike to work to "save the environment" but won't use C direct on metal to reduce the carbon footprint of their code. For a guy like Carmack, it may
by buboard 7y ago
people will bike to work to "save the environment" but won't use C direct on metal to reduce the carbon footprint of their code.
For a guy like Carmack, it may be quite frustrating working with the constraints of pytorch etc. He ll probably end up making his own pytorh frontend in C, which as a bonus people will use to deploy models.
- Aperocky 7y agoI don’t think it’s that big of an language issue. Java isn’t that much slower (logarithmically speaking). But design choices have arbitrarily incorporated huge amount of bloat and inefficiency.
- buboard 7y agoyep, logarithmic. Well, the question is what's the motive about those design choices? Today's e.g. web app choices seem to be basically aesthetic with an eye for extreme novelty, and total disregard for how many times a buffer is being copied back and forth before reaching the user.
- Aperocky 7y agoThat is compared to python/ruby which would be multiple logs slower or scaling choices that makes the service resemble the microkernels. Usually dedicated, simple engineering can be very fast using either C or java
- FpUser 7y agoHypocrisy is not such a rare animal. There is however extra factor here: biking to work if possible is your personal choice. Using your favorite tools at work: often not as much
- buboard 7y agoprobably not so much hypocrisy as lack of consideration. Even though the energy benefit from making apps e.g. twice as fast isn't so big, it's worth giving a try for the time savings.