HackerTrans
TopNewTrendsCommentsPastAskShowJobs

user-the-name

no profile record

comments

user-the-name
·5 miesięcy temu·discuss
[dead]
user-the-name
·7 miesięcy temu·discuss
[dead]
user-the-name
·8 miesięcy temu·discuss
[dead]
user-the-name
·9 miesięcy temu·discuss
[dead]
user-the-name
·5 lat temu·discuss
Yes. Yes, we should.

Yes.

Then man kept other humans as slaves. That is evil. There is no question about this. People in his own time thought this was evil. He did it anyway. He was evil.
user-the-name
·5 lat temu·discuss
> Buuuuut he was a slave-owner

You say this mockingly, as if being a slave owner should not overshadow everything else you do in life.

Yes, it should. It absolutely should. Being a slave-owner is massively, grotesquely evil. It should be what you are remembered and rightly denounced for.

> Particularly when you use today's more sensitive moral yardstick to measure yesterday's actions!

Considering slave-owning to be morally wrong is not a modern invention. It was considered wrong at the time too, just not by those who were profiting off it.

For instance, I don't think you'd find many slave who did not think it was evil.
user-the-name
·5 lat temu·discuss
> The Earth is the edge case

You do not know that. All available evidence points to the opposite: We have no knowledge, not even a hint, of any other physical process that could sustain life than that of Earth's carbon-based chemistry.

The idea that life could take a myriad of different forms is beautiful, but it is pure fantasy, based on no evidence at all.
user-the-name
·5 lat temu·discuss
> training ML systems on public data is fair use

So, to be clear, I am allowed to take leaked Windows source code and train an ML model on it?
user-the-name
·5 lat temu·discuss
This is an argument for why this is a bigger problem, not a smaller one.
user-the-name
·5 lat temu·discuss
Why? You don't need to. GitHub will show you that diff, git itself will show you that diff. There is no need to permanently rewrite history to do this. That makes no sense.
user-the-name
·5 lat temu·discuss
> And many tech leads simply don't have the time to review every single WIP commit

Do you usually review every commit? I usually just review the diff between the PR'd branch and master, as does everyone I work with.
user-the-name
·5 lat temu·discuss
None of those require a "meaningful history that tells a bigger story".
user-the-name
·5 lat temu·discuss
But why? What problem are you actually solving with this?
user-the-name
·5 lat temu·discuss
> Managers, tech leads, or users of your OSS project don't care about the "fix typo" comments. They are interested in a meaningful history that tells a bigger story.

Why would they be looking at the version control system for this? That is not what it's there for.
user-the-name
·5 lat temu·discuss
But why should any of that apply to my version control system? I'm not developing the Linux kernel on a mailing list.
user-the-name
·5 lat temu·discuss
That seems connected to the initial claim in only the most tenuous way.
user-the-name
·5 lat temu·discuss
> Ideally, each commit should be something that you could submit as a stand-alone patch to a mailing list

Why?
user-the-name
·5 lat temu·discuss
Why not? I do not see any reason to have a history at all for anything except to be able to go back to a specific version to track down a problem. Inaccurate history makes that less useful.
user-the-name
·5 lat temu·discuss
(That is not the whole point of art)
user-the-name
·5 lat temu·discuss
And if the timezone changes, should the meeting you booked at 9 AM now happen at 8 AM?