Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • He is just legendary when it comes to game programming
    by cuechan
  • I took notice when he breaks down the ethics of gen ai as it pertains to online theft, that AI broke the natural order of putting content online where you'd trade exposure for use https://youtu.be/bjO-s4rNPlY?si=uAtBTb6V_Sw1puBU&t=2244
    by fantasizr
  • Will have to give this a watch after the kids go to bed. I like a lot of Casey’s views even if I don’t agree with them.
    by mberning
  • THE LEGENDARY GAME PROGRAMMER
    by kshallvari
  • Personally I'm quite sure this is super interesting, but I don't really have 3 hours to listen to this, even 1.5h at 2x speed is too much.

    I would very much prefer something written down, so I could absorb this at my own pace. I know, gift horse, but still.

    by torginus
  • What I don't understand with both Muratori/Blow is that they seem to be incredulous that someone wouldn't just make software high quality and fast for the sake of it

    Like they can't comprehend the fact that these things only happen if there is an incentive for it

    I think its because they work in games where there is a business incentive for performance, users care a lot if framerate suffers in a game

    They are so used to working in games that they take it for granted that the business incentive for performance exists

    As someone who has worked in both AAA games and big tech it just comes across as a bit naive to me

    by ex-aws-dude
  • Terrific presentation. But I have a comment:

    His dismissal of the argument Knuth makes regarding the hot loops could have been explored a bit better. I found it weird he didn’t mention the difference of types of programs of then vs now. Even today, in scientific code it is still absolutely the case a lot of the time that a huge chunk of the runtime comes from a single very very hot loop. It might be hidden in a library, but it’s there. Instead he focuses only on “program size”. Knuth samples where very small FORTRAN programs (compared to today’s standards). Today’s program are bigger but the fundamental number crunching primitive of “let’s compute stuff in a loop” remains. It’s just buried under a pile of extra cruft (data loading, parallelism, dispatching etc).

    Now we just deal with a lot more programs that are of a whole different class compared to what they where doing with computers in the 70s. We have much more I/O involved. And hot loops don’t like being I/O bound.

    by FacelessJim
  • I think Casey is currently the most informed person to make a series of books or articles summarizing the history of SW Engineering, all the lessons learned and forgotten, and all the good stuff that was published and still hasn't gained traction in the practice
    by Almondsetat

Explore Birbla archives