Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

AgapovOne
Copy link

@AgapovOne AgapovOne commented Apr 25, 2025

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

@chrisbrandow
Copy link

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

details-summary tag might be unusual way of interacting with repos.
@AgapovOne
Copy link
Author

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

@devMEremenko
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants