Conversation

Notices

1. Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 01-Mar-2023 06:09:16 JST Adrian Cochrane

   • Csepp 🌢
   • cancel

   @wim_v12e @csepp @cancel The biggest one that helps JITers is small function sizes, which are heavily reused.

   Then again, polymorphism is especially tricky for JS to optimize away. Not that that stops JS engines from trying!

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 01-Mar-2023 07:34:07 JST Adrian Cochrane

     in reply to

     • Csepp 🌢
     • cancel

     @cancel @wim_v12e @csepp I do think the video addressed function-size as something that doesn't necessarily yield more optimal code in C++, but ultimately I agree.

     I think OO got over-hyped leading to some bad software-engineering decisions which we're still living with.

     P.S. @cancel I would appreciate your source to adjust my understanding. Unfortunately I've lot track of mine.

   • cancel (cancel@merveilles.town)'s status on Wednesday, 01-Mar-2023 07:34:08 JST cancel

     in reply to

     • Csepp 🌢

     @alcinnz @wim_v12e @csepp

     what you're describing with function size for JIT 1) isn't true 2) isn't relevant for the video, anyway, because the function calls aren't repeated in multiple sites.

     ("clean code" people will often tell you to break up stuff into the smallest functions possible. the video covers this)