[issafram]

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

[maxbond]

You've gotta click "tree".

https://git.sr.ht/~evanhahn/setBigTimeout/tree/main/item/mod...

[adregan]

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...

[Minor49er]

I clicked on "browse" under the refs: main section and found the code right away

[zgk7iqea]

yes, sourcehuts interface is just godawful

[egwynn]

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]

One has still to know that "tree" stands for "source code".

[kelnos]

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]

Well it doesn't stand for "source code". It's the tree of directories and files.

[internetter]

This is not a sourcehut problem, it is a github problem. "Tree" is semantically correct.

[ajkjk]

What? Of course it's a Sourcehut problem. They chose to use that word and could choose to use a better one.

[Klonoar]

Tree has been used for this kind of thing for decades now.