Straightforward ? When 80%+ of your analysis code ends up marked as in conflict and the new code has a completely different structure you just say fuck it, who did that can finish the protection themselves. But of course they won’t.
-
-
Vastauksena käyttäjille @o_galibert ja @topapate
Gee, welcome to my world when a dev (who I at least have the fucking courtesy to not name) completely fucked up the AVR-8 core. You know what I did. I knuckled down and dealt with it.
2 vastausta 0 uudelleentwiittausta 0 tykkäystä -
You want MAME's codebase to stay at a standstill while you take 5-10 years to implement a single major improvement to some driver or CPU core, but welcome to the real world, other people will try to contribute in the meantime if you don't.
1 vastaus 0 uudelleentwiittausta 0 tykkäystä -
Vastauksena käyttäjille @TheMogMiner ja @topapate
In the meantime ? I had been working and pushing updates continuously for a couple of weeks when he did that. We’re talking hours there, not years. And yes, I’m still pissed about it because it’s never going to be finished.
1 vastaus 0 uudelleentwiittausta 0 tykkäystä -
Vastauksena käyttäjille @o_galibert ja @topapate
Dude. If you think I'm defending Haze, you've got another thing coming. I get that you aren't his biggest fan, to be succinct. But if you can engage in enough of a dialogue with me to tell me to fuck off, you can at least ask him to describe his changes.
3 vastausta 0 uudelleentwiittausta 0 tykkäystä -
Vastauksena käyttäjille @TheMogMiner ja @topapate
It was svn time, there was no coming back from a destroyed tree.
1 vastaus 0 uudelleentwiittausta 0 tykkäystä -
Vastauksena käyttäjille @o_galibert ja @topapate
Who brought up svn? I suggested actually engaging in a potentially productive conversation with David "Haze" Haywood, to ask him the nature of his changes, why they were made, and what the ultimate differences were to the codebase.
1 vastaus 0 uudelleentwiittausta 0 tykkäystä -
Vastauksena käyttäjille @TheMogMiner ja @topapate
It wouldn’t have mattered. The huge pile of local code I was relying on to trace what was going on was irremediably destroyed
1 vastaus 0 uudelleentwiittausta 0 tykkäystä -
Vastauksena käyttäjille @o_galibert ja @topapate
Man... look. I can't pretend to know what grief you went through. And since we've moved past SVN, yes, obviously, it's not easily remediated. But it occurs to me that this whole situation could have been avoided with some basic communication, which you *both* refuse to do.
1 vastaus 0 uudelleentwiittausta 0 tykkäystä -
If you want to continue to bear some grudge 6 years on, and use it as some kind of token to throw shade at another team member now, the fine, go off, man. But this kind of bitter acrimony doesn't help anyone. It doesn't help you, it doesn't help MAME, it doesn't help anything.
1 vastaus 0 uudelleentwiittausta 0 tykkäystä
At some point, it's worth acknowledging that every one of us is doing what we consider to be "best" for MAME in our own personal frame, and sometimes those mental frames differ. It's better to assume positive intentions than engage in years-long bitterness.
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.