> P.S. The stack overflow question for splitting commits discusses the old and cumbersome approach. The 20th answer discusses the right approach but has a meagre 2 upvotes as of today, compared to 2656 for the older top answer with the cumbersome approach.

It now has 5 upvotes. A long way to go to 2656 but at least it's going in the right direction.

▲

hotelsacher 4 hours ago | parent | next [-]

Still, it shows how incredibly broken the StackOverflow system is. It's completely normal for older answers to become outdated, but they still act like the old answers are laws of nature.

▲

BeetleB 4 hours ago | parent | next [-]

I think this is harsh criticism. It's because not many people use SO any more.

One of SO's selling points was that outdated answers get replaced with the more modern, better ones - and it worked for many, many years.

▲

locknitpicker an hour ago | parent | next [-]

> One of SO's selling points was that outdated answers get replaced with the more modern (...)

I don't think this is description is right. What you describe as "outdated answers" are actually answers to apply up to specific releases. Just because a project launches a release that rolls out a new feature that doesn't render the old answers wrong or stale.

	▲	schacon 16 minutes ago \| parent [-]
		Not only this, but it's not super simple to update to the newest version anymore. I actually tried this today and I'm on `2.50.1 (Apple Git-155)`. It turns out I don't actually know how to update that. `brew install git` does not overwrite the system binary. I'm not the smartest person in the world, but if I had issues getting to the latest version, I assume a very small percentage of users actually has a Git version that will run `git history`. It was introduced in 2.54, which was in April of this year, so less than 4 months ago. Almost nobody can run this command unless they're _really_ on top of things.

▲

hungryhobbit 3 hours ago | parent | prev [-]

... until they decided it was a good idea to train all power users to grief new users off the site.

	▲	da_chicken 2 hours ago \| parent \| next [-]
		It was always like that. It's due in part to the number of people that kept posting screenshots of their code in their question, and the number of people that couldn't search to save their life. The noise ratio on incoming questions was always ridiculous, and the number of people who don't know how to ask a technical question is staggering. I do wish they had started to ask a series of questions to people for their first 5 or 10 posts to force them to ask questions in a useful way that was conducive to getting answers. The whole site never got over being hostile to new users. SO had a number of fundamental issues. If you found a duplicate and flagged it as such, you couldn't explain why you thought it was a dupe in the flag. This meant that "this is a different question but the answer is the same" was just tagged a dupe the same way "this is literally the identical question" was. I stopped participating entirely after a single event. When I was moderating the moderation, and the site decided to give me a trick question to "test if I was paying attention". Yeah, no. I don't have time for that bullshit. Apparently I'm still a top 1% user, though, and I think I've gained another 8,000 or 9,000 points since I left and stopped answering at anything.
	▲	jatora 2 hours ago \| parent \| prev [-]
		The rise of AI and the death of SO is a beautiful beautiful thing. That community is the worst, and this opinion seems to be shared universally by anyone who had extensive interaction with it.

▲

layer8 3 hours ago | parent | prev [-]

At least the answer is there. When asking ChatGPT (Plus) the same question, it only suggests the old ways.

	▲	locknitpicker an hour ago \| parent [-]
		> At least the answer is there. When asking ChatGPT (Plus) the same question, it only suggests the old ways. The old ways are still the right answer for multiple reasons, such as they still clearly work with the latest release and odds are you and everyone around you is not running the latest and greatest version of git installed.

▲

brewmarche 2 hours ago | parent | prev | next [-]

These answers are ~15 years apart, so the vote difference is not surprising.

I personally sort by ‘date modified (newest first)’ on StackExchange sites.

▲

no-name-here 3 hours ago | parent | prev [-]

It’s now the 6th answer instead of the 20th, and if answers are sorted by Trending (which I recommend people do) in the dropdown, it’s currently 3rd.