HNHacker News
TopNewBestAskShowJobs

Gorilla1000kg

11 karma · joined January 29, 2024

submissionscomments
Gorilla1000kg··on Amiga Emulator: WinUAE 5.2.0
Cloanto does not singularly hold the authority to make AmigaOS open source. As you well know, the ownership and legal rights to AmigaOS have been entangled in intricate legal matters, particularly following the involvement of Hyperion Entertainment and the settlement agreement under Amiga Inc.

Mike, as part of the new Amiga company, is in a legal position that potentially allows for such a transition. However, decisions around making AmigaOS open source are not solely at his discretion but are influenced by a web of legal agreements and considerations.

"At the end of December 2015, Austrian self-proclaimed "hacktivist" Mr. Bernhard R. Fischer gave a speech titled "The Ultimate Amiga 500 Talk" [236] at the 32th Chaos Communication Congress in Hamburg, Germany. At about the same time as the speech, during which Mr. Bernhard R. Fischer cited his own past as a "cracker" and "spreader", the proprietary source code of Amiga OS 3.1 was leaked to that same event's file sharing network, and immediately became public [237]. Analysis of this leaked source code revealed how Cloanto had contributed to the Amiga operating system as far back as 1993 [230], leading to some speculation on whether it could use this status in relation to the complex legal proceedings between Hyperion Entertainment and the Amiga parties, and in the context of an open source scenario. Between 2016 and 2017, Cloanto added some details about "possible futures involving open source, a nonprofit and/or foundation, and other long-term preservation scenarios" to its cloanto.org page [238]. In what seemed like a response to this, Hyperion Entertainment director Mr. Timothy De Groote stated that "We cannot legally support this. Once it is open source, this is an irreversible decision that is beyond the scope of our license under the Amiga Inc. Settlement Agreement." [240]."

For a more detailed understanding, please read the Amiga Documents https://sites.google.com/site/amigadocuments/

Gorilla1000kg··on Amiga Emulator: WinUAE 5.2.0
Based on our current understanding, the Amiga documents appear to be accurate, including the identification of the individual funding Hyperion.

Their actions have caused considerable frustration. For years, they lied to us, fostering a climate of animosity and even hatred.

What Amiga could have been if not for their greed.

Gorilla1000kg··on Amiga Emulator: WinUAE 5.2.0
Yep - you summed it up best. We're all tired of the bullshit and many missed opportunities.

It's sad to see what the Amiga has become, but despite everything, the Amiga spirit is experiencing a renaissance, with more activity and passion than we've seen in a long time. Interesting things are happening.

Gorilla1000kg··on Amiga Emulator: WinUAE 5.2.0
You have it wrong -

The assertion that Cloanto harbored concerns over potential market loss to Hyperion's AmigaOS 3.2 for use in emulators doesn't hold up when considering Cloanto offers ROM images at a nominal cost—essentially a dollar—whereas AmigaOS 3.2 is priced significantly higher, making the former a more accessible option for enthusiasts looking to legally emulate.

It's important to correct a misconception here: the developers behind AmigaOS 3.2 volunteered their time; they weren't financially compensated. This fact shifts the narrative considerably, especially in light of the ongoing legal battles, which, contrary to some perceptions, have predominantly been instigated by Hyperion. Given that Hyperion's management includes legal professionals, their propensity for litigation isn't surprising. Moreover, there are rumors suggesting Hyperion's litigation efforts are financially supported by an entity with a direct interest in Cloanto's failure to retain rights—a speculation that adds another layer of complexity to the dispute.

My experience in the Amiga community spans back to its golden years, allowing me a unique perspective on its evolution. Throughout this time, it has become evident that the situation is far from straightforward, entangled in a web of legal, financial, and emotional factors. The narrative isn't just about one entity's actions over another; it's about a passionate community caught in the midst of corporate and legal maneuverings, each with its own implications for the future of Amiga.

Gorilla1000kg··on Amiga Emulator: WinUAE 5.2.0
The situation surrounding Amiga's legacy and its preservation is significantly more complex than it appears at first glance. Cloanto, holding a sincere desire for the Amiga's continuity, possesses the rights for the emulation of version 3.1. On the other hand, Hyperion Entertainment, which holds the rights to AmigaOS 4, opted for the PowerPC architecture over x86 to protect its niche in game porting, fearing that a transition to x86 would jeopardise this sector. Importantly, Hyperion does not hold rights to any version prior to OS 4. Indeed, Hyperion had a hand the death of AmigaOSXL / Amithlon.

A year or so ago, Mike Battilana of Cloanto, along with associates, has acquired the remnants of Amiga, establishing a new entity distinct from Cloanto itself.

Despite financial challenges, Hyperion is being financially supported by an undisclosed backer, aiming to initiate spurious legal action against Cloanto.

It's important to clarify that neither AmigaOS 4 nor AROS was ever at risk amidst these disputes. Mike Battilana has expressed a strong desire to see an end to these conflicts. He is firmly against the idea of undermining any Amiga-related initiatives. He said to me in passing that he would love to provide enhanced support for projects like AROS, so AROS can, if it wishes, call itself Amiga Research Operating System again.

Mike's actions and intentions throughout this ordeal have demonstrated a level of integrity and commitment to the Amiga community that stands out, marking him as a notably principled figure in the ongoing saga of Amiga.

He's a good guy.

Gorilla1000kg··on Ask HN: Those who've joined a friend's startup as an employee, how did that go?
A friend shared this thread with me... he said I should share my story.

Joining my "friend's" startup, I hoped to use my experience and connections to guide and support the team. My friend, twenty years my junior and someone I'd previously mentored, was leading the venture. He and his business partner left University, and had the dream of forming a silicon valley company. They spent several years grinding away at this dream, and fair play to them, managed to raise millions on the back of a very weak idea. They were now ready to build a team and start developing the product. They had never been an employee as such (unless you count working in McDonalds), and had no idea how to run a company. I was excited to help them, and to see if I could help them avoid the mistakes I'd made in my career. These lads were much maligned and laughed at - they were seen as a joke by many, and I didn't like that. I wanted them to win.

Despite witnessing some concerning behavior early on.... - He gatecrashed a christmas party I attended and made a scene by dry humping me from behind, and loudly proclaiming to everyone that I was 'his bitch' - I chose to join out of loyalty and optimism.

The job quickly turned sour. As CTO, his performance was far from what I expected. He was not only ill-equipped for the technical demands of the role but also struggled with the emotional and ethical aspects of leadership. His approach to technology was chaotic and misguided, often leading us down problematic paths. There was a particularly serious incident which I won't go into, but he refused to acknowledge how serious it was.

The work environment became increasingly difficult. His emotional outbursts, lack of accountability, and poor decision-making created a toxic atmosphere. When my colleagues and I attempted to intervene or suggest strategic changes, we were met with resistance and eventually dismissed for not being a good 'fit'.

Even though the company eventually pivotted towards our advice, the damage was done. The leadership remained a disaster. Their dev turnover is high. If people aren't fired they quit.

This whole mess taught me one thing: while I’d still consider working with a friend, it has to be someone I deeply respect and trust. Someone competent, with integrity, not a power-drunk disaster like this. Never again will I make the mistake of mixing business with misplaced loyalty.