4 ms·

I wish that I could actually see the code. I understand that it's chaining timeouts, but the git site is just garbage

• maxbond 2y ago
  You've gotta click "tree". https://git.sr.ht/~evanhahn/setBigTimeout/tree/main/item/mod.ts https://git.sr.ht/~evanhahn/setBigTimeout/tree/main/item/mod...
• zgk7iqea 2y ago
  yes, sourcehuts interface is just godawful
  • egwynn 2y ago
    I agree it’s not the prettiest, but I had no trouble clicking on “tree” to get to the folder and then “mod.ts” to see the code.
    • Joker_vD 2y ago
      One has still to know that "tree" stands for "source code".
      • internetter 2y ago
        This is not a sourcehut problem, it is a github problem. "Tree" is semantically correct.
        • ajkjk 2y ago
          What? Of course it's a Sourcehut problem. They chose to use that word and could choose to use a better one.
          • Klonoar 2y ago
            Tree has been used for this kind of thing for decades now.
            • ajkjk 2y ago
              So what? There are still better words for it.
      • kelnos 2y ago
        That seems like... a normal thing to know? Pre-GitHub, one of the most popular web git viewers (cgit) used "tree" in this way. Never found that to be confusing. (In git, the listing of the files and directories at a particular commit is called a "tree". So it's correct. Just not as intuitive as you, personally, would like.)
      • mort96 2y ago
        Well it doesn't stand for "source code". It's the tree of directories and files.
• adregan 2y ago
  This reminds me of when I am trying to find something in a cabinet, but don’t really look very hard, and my wife will say “did you even try?” and find it in ~1second. https://git.sr.ht/~evanhahn/setBigTimeout/tree/main/item/mod.ts https://git.sr.ht/~evanhahn/setBigTimeout/tree/main/item/mod...
• deleted 2y ago
  [deleted]
• Minor49er 2y ago
  I clicked on "browse" under the refs: main section and found the code right away