• Hexorg@beehaw.orgM
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    I do dislike Rust’s namespace(module) mapping to files but I’m not certain requiring a single directory package structure is the solution as I don’t think it’s all that discouraging for having a ton of files in there… have you seen Java? If at some point you’re so concerned about compilation times you should be able to rip out modules into new crates without a problem since they are already in separate folders.

    • rath@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      1 year ago

      In Java it’s really rare to see hundreds of files in a single package (dir)… do you have examples showing anything different??

  • nii236@lemmy.jtmn.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Aw shit here we go again lol.

    Though as a guilty pleasure, and as a career Gopher, I can’t get enough of these comparisons.

    After reading the article, seems that “as usual”, Go being restrictive and more rigid actually helps improve the code.

  • Kalkaline @lemmy.one
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I know nothing (relatively speaking) about programming or Rust or Go, but all of this made a lot of sense.

  • KerPop47@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Ooh, an interesting read. I’m looking to get into a new language, and I’ve been looking at Rust. Would the best use then be to have many small crates? Maybe have a tool that creates the toml? Wouldn’t that keep compile times low?