Conversation

Notices

1. Embed this notice
   Puniko ? (puniko@mk.absturztau.be)'s status on Thursday, 11-Apr-2024 16:50:43 JST Puniko ?

   best method to optimize: don't optimize :blobcatgooglyfingerguns:

   • kaia likes this.
   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Thursday, 11-Apr-2024 16:51:06 JST Puniko ?

     in reply to

     at least not during development :neocat_googly_woozy:
     you can still optimize afterwards :blobcatgooglyfingerguns:

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Thursday, 11-Apr-2024 17:00:04 JST Puniko ?

     in reply to

     • lumi :blobcatnom: :blobcatflower:

     @lumi@snug.moe i mean, its easier and better to optimize an already running piece of code

   • Embed this notice
     lumi :blobcatnom: :blobcatflower: (lumi@snug.moe)'s status on Thursday, 11-Apr-2024 17:00:06 JST lumi :blobcatnom: :blobcatflower:

     in reply to

     @puniko postmature optimization

   • Embed this notice
     prisixia (prisixia@mk.absturztau.be)'s status on Thursday, 11-Apr-2024 17:00:15 JST prisixia

     in reply to

     @puniko
     have you seen gcc compiler attributes

     Puniko ? likes this.
   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Thursday, 11-Apr-2024 17:01:58 JST Puniko ?

     in reply to

     • Stanford

     @tfunken@social.lyratris.com no, optimizing code should be done after developing a piece of code, not during development imo. its then easier to spot, what needs optimizing and to what extend the optimiziasion improves the performance

   • Embed this notice
     Stanford (tfunken@social.lyratris.com)'s status on Thursday, 11-Apr-2024 17:02:05 JST Stanford

     in reply to

     @puniko It doesn't run smooth?

     Well, that definitely the users fault for not having enough RAM :nko_giggle:

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Thursday, 11-Apr-2024 17:02:55 JST Puniko ?

     in reply to

     • JennyFluff :heart_trans:

     @JennyFluff@chitter.xyz my point being optimiziations should be done after developing a first running version

   • Embed this notice
     JennyFluff :heart_trans: (jennyfluff@chitter.xyz)'s status on Thursday, 11-Apr-2024 17:02:59 JST JennyFluff :heart_trans:

     in reply to

     @puniko yeah this is true for most applications.

     Especially if you don't have a thing that uses a lot of resources in the first place.

     Though if you do, you might be optimizing it, but that is quite rare in modern tech

   • Embed this notice
     JennyFluff :heart_trans: (jennyfluff@chitter.xyz)'s status on Thursday, 11-Apr-2024 17:13:15 JST JennyFluff :heart_trans:

     in reply to

     @puniko given how long modern software is in development after the first running version, I'd move this a few years in the future

     Puniko ? likes this.
   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Thursday, 11-Apr-2024 18:43:06 JST Puniko ?

     in reply to

     • lumi :blobcatnom: :blobcatflower:

     @lumi@snug.moe thats basically what i mean, yes

   • Embed this notice
     lumi :blobcatnom: :blobcatflower: (lumi@snug.moe)'s status on Thursday, 11-Apr-2024 18:43:07 JST lumi :blobcatnom: :blobcatflower:

     in reply to

     @puniko i think there is a tradeoff here, because some performance optimizations are hard to do after the fact, especially if your software wasn't architected with performance in mind
     
     but going all in on perf from day 1 and overoptimizing tends to be bad in the other direction