• redcalcium@lemmy.institute
    link
    fedilink
    arrow-up
    70
    ·
    6 months ago

    I’m truly torn with this. The first one seems sensible (action -> target) and easier to read and reason about (especially with long names), while the other one looks more organized, naturally sortable and works great with any autocompletion system.

      • Lightfire228
        link
        fedilink
        arrow-up
        13
        ·
        6 months ago

        I am a programmer, and i also like the naming scheme on the right

        Especially for things like filenames

        • bitwolf@lemmy.one
          link
          fedilink
          arrow-up
          9
          ·
          edit-2
          6 months ago

          Also a programmer and think method names would be conducive using little endian.

          TopicGet()
          TopicCreate()
          TopicDelete()
          

          Writing this I realize we do this implicitly in some instances.

          http.Get() -> httpGet()
          http.Post() -> httpPost()
          
    • kunaltyagi@programming.dev
      link
      fedilink
      arrow-up
      15
      ·
      6 months ago

      We need a new framework, one that allows universal lookup, and makes life easier

      x = _.dialog.file.open
      y = _.open.file.dialog
      z = _.file.open.dialog
      a = _.file.dialog.open
      

      Once done, the formatter simply changes everything to _.open.file.dialog

      Let’s get this done JS peeps

      \s