XcodeBenchmark icon indicating copy to clipboard operation
XcodeBenchmark copied to clipboard

Move older xcodes to summary-details tag to improve readability of repo

Open AgapovOne opened this issue 9 months ago • 4 comments

This pull request is not a build details, but an improvement to readability.

I consider older Xcodes irrelevant to common viewer of this repo so we could keep history but move it in cut.

You can preview the README here: https://github.com/AgapovOne/XcodeBenchmark/tree/patch-1

AgapovOne avatar Apr 25 '25 06:04 AgapovOne

I think this PR would make the usability slightly poorer for a couple reasons

  1. I don't think it actually improves readability to begin with since the newest result comes first, so it is unchanged how quickly a user finds the most recent results.
  2. On my first pass reading your proposed README, I didn't see any link or indication of how to find the older versions.
  3. I often compare the most recent results with at least the last prior version, particularly when the newer version is lacking examples. Putting the older versions on a separate page would make this more difficult.

Fundamentally this proposal reduces usable information without improving the time to acquire the newest information..

chrisbrandow avatar Apr 26 '25 19:04 chrisbrandow

@chrisbrandow you might be right, but is it about familiarity with old style or actual time to find information?

Older versions could be found with search on page or right below latest Xcode table:

Screenshot 2025-04-28 at 10 20 51

It's not a separate page but information is not revealed right away. It won't be searchable either, so use-case where you would

  1. Enter a repo
  2. Search for some result or machine
  3. Find all results for all possible xcode versions

Would be broken.

But I don't see this as a main way of using this repo. Who would need to use old xcode? Only people who have an old project and can't move to it, so this information is irrelevant to majority of newcomers.

AgapovOne avatar Apr 28 '25 05:04 AgapovOne

Hey folks,

@AgapovOne, thank you for your suggestion. I generally support the idea. At the same time, GitHub allows a quick jump to the necessary section (see screenshot).

@chrisbrandow, I see your point, too. Would viewing a plain or raw file as well as expanding the other section work for your use case?

Let me know your thoughts.

Screenshot 2025-05-09 at 22 00 18

devMEremenko avatar May 09 '25 20:05 devMEremenko