10 ms·
The Homebrew Channel repository is archived (Apr 28, 2025)
- deng 1y agoDiscussed yesterday: https://news.ycombinator.com/item?id=43812995 https://news.ycombinator.com/item?id=43812995
- smcin 1y ago<deleted>. My mistake
- dharmab 1y agoWrong Homebrew. Totally unrelated to this.
- devixluvic 1y agoThe blog you linked is to Homebrew, the package manager for macOS. "The Homebrew Channel", the Wii project that is in discussion here, is unrelated despite sharing a name.
- smcin 1y agoThanks for the correction.
- trashburger 1y ago[flagged]
- chungy 1y agoSo, allegedly it stole Nintendo SDK code, and Nintendo never noticed nor filed any kind of injunctions, especially since this was an extremely popular jailbreak tool when the Wii was the current console? This isn't passing the sniff test. I think Marcan is just trolling.
- onli 1y agoNot sure trolling is the right word. But it is very strange behaviour, to get so worked up and confrontational publicly, especially as a non-injured party. Goes right in line with his behaviour in the kernel rust saga. Conclusions are up to the reader.
- karlgkk 1y agoIt seems to me that he very visibly took an L, and he is still tilted by that. This is also after a wave of harassment from the far right.
- TazeTSchnitzel 1y agoMarcan is an injured party! If you go to great lengths to build a legally clean open-source project on top of a foundation of supposedly legally clean open-source libraries — absolutely critical libraries that have no currently existing alternative — and then discover that their supposed cleanness was a lie all along, it's not just an abstract insult and betrayal, it's a realisation that the immature actions of others have put an entire scene in legal jeopardy.
- rootsudo 1y agoThis, but also it's so long ago and old, not current or a previous current gen system. The wii was discontinued october 2013, and released November 2006. Effiectively its 12-19 years old now, for me, while I understand it also kinda falls under "who cares" because homebrew always was always somewhat equal to piracy.
- notachatbot123 1y agohttps://mardy.it/blog/2025/04/no-libogc-did-not-steal-rtems-code.html https://mardy.it/blog/2025/04/no-libogc-did-not-steal-rtems-... is a rebuttal
- messe 1y agoI think this comparison by armada651 linked in yesterday's thread is a better example (https://news.ycombinator.com/item?id=43818214 https://news.ycombinator.com/item?id=43818214) https://github.com/atgreen/RTEMS/blob/2f200c7e642c214accb7cc6bd7f0f1784deec833/c/src/exec/score/src/thread.c#L1141 https://github.com/atgreen/RTEMS/blob/2f200c7e642c214accb7cc... https://github.com/devkitPro/libogc/blob/52c525a13fd1762c10395c78875e3260f94368b5/libogc/lwp_threads.c#L388 https://github.com/devkitPro/libogc/blob/52c525a13fd1762c103... Multiple functions in that file are near identical.
- karel-3d 1y agoI am not up-to-date with the drama The original code this was copied from was open source; why not "just" say "oops we are sorry" and add the attribution? Licensing issues? But the repo in OP is also GPL?
- deng 1y agoSee also: https://mas.to/@davejmurphy/114414723608693881 https://mas.to/@davejmurphy/114414723608693881 There's a legal and moral implication. Legally, saying that you took someone else's code as "source of information" would probably be seen as copyright infringement. Morally, I must say I find it difficult to get worked up about it. How to write a basic OS with a threading implementation shouldn't be rocket science for anyone with a good CS background (yes, I'm aware RTEMS was literally written for rockets, but still). Yes, he took a shortcut here by looking at an existing project, and if this was a commercial project, I might see why one could get angry. However, I also can't really understand why they simply refuse to give credit to the original project and maybe also change the license to GPLv2.
- msm_ 1y ago>Legally, saying that you took someone else's code as "source of information" would probably be seen as copyright infringement Not necessarily. There are ways to work around that, for example white box reverse-engineering[1]. Also there are exemptions for some use cases, like interoperability. I'm sure a lawyer could figure something out, but it looks like they didn't consult any, and didn't follow a rigorous process. [1] https://ospo.co/blog/modern-reverse-engineering/ https://ospo.co/blog/modern-reverse-engineering/ - a random link I found by googling, but presents the idea well.
- zombot 1y agoSo this has nothing to do with the Homebrew package manager on macOS? I'm confused.