←back to thread

setBigTimeout

(evanhahn.com)
210 points cfj | 7 comments | 17 Oct 24 18:01 UTC | HN request time: 0.203s | source | bottom
Show context
issafram ◴[18 Oct 24 16:50 UTC] No.41881187[source]▶
I wish that I could actually see the code. I understand that it's chaining timeouts, but the git site is just garbage
replies(5): >>41881255 #>>41881282 #>>41881321 #>>41881348 #>>41883829 #
zgk7iqea ◴[18 Oct 24 16:59 UTC] No.41881282[source]▶
yes, sourcehuts interface is just godawful
replies(1): >>41881332 #
egwynn ◴[18 Oct 24 17:04 UTC] No.41881332[source]▶
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.
replies(1): >>41882365 #
1. Joker_vD ◴[18 Oct 24 18:55 UTC] No.41882365[source]▶
One has still to know that "tree" stands for "source code".
replies(3): >>41884585 #>>41885519 #>>41886820 #
2. internetter ◴[19 Oct 24 00:11 UTC] No.41884585[source]▶
This is not a sourcehut problem, it is a github problem. "Tree" is semantically correct.
replies(1): >>41885281 #
3. ajkjk ◴[19 Oct 24 02:52 UTC] No.41885281[source]▶
What? Of course it's a Sourcehut problem. They chose to use that word and could choose to use a better one.
replies(1): >>41887938 #
4. kelnos ◴[19 Oct 24 03:51 UTC] No.41885519[source]▶
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.)

5. mort96 ◴[19 Oct 24 09:51 UTC] No.41886820[source]▶
Well it doesn't stand for "source code". It's the tree of directories and files.
6. Klonoar ◴[19 Oct 24 14:26 UTC] No.41887938{3}[source]▶
Tree has been used for this kind of thing for decades now.
replies(1): >>41889510 #
7. ajkjk ◴[19 Oct 24 18:15 UTC] No.41889510{4}[source]▶
So what? There are still better words for it.