A Sane Directory Structure for Software Projects — Andrew Tropin
trop.in
  • TehPers@beehaw.orgEnglish
    9·
    2 days ago

    The high-level directory structure looks reasonable, but every language and build tool has its own recommended structure that people should use instead. For example, by default, cargo looks for a src/main.rs or src/lib.rs as an entrypoint. uv expects one of a couple different project structures before you need to touch the pyproject.toml. C# will create namespaces for each of these nested subdirectories if you don’t carefully configure it in your .csproj file. And so on.

    It’s best to just use whatever’s recommended for your environment by your tools. Maybe this directory structure works well for Guile Scheme, but I wouldn’t touch it at all if I were writing Rust.

  • Paragone@piefed.socialEnglish
    2·
    1 day ago

    < sigh >

    There WAS a video on yt by a Norwegian man on why OO languages push people into spreading side-effects throughout the code, whereas in Haskell, side-effects are optimally conserved to Main.hs

    I can’t find that video, now.

    He was on stage, a talk of some kind, not as formal as a university-lecture, so it was some conference, of some kind… ( in case anybody else finds it )

    I think that that principle is contradicting what the article is saying… ( skimmed the rest, I think he’s generally right, but burying side-effects seems to be wrong, from Haskell’s perspective, & I think Haskell’s right, generally. )

    _ /\ _