[MacAMP]( https://en.wikipedia.org/wiki/MacAmp ) was real and official, directly from Nullsoft, a million years ago.
Fun and easy to reskin as well!
Winamp clone in Swift for macOS
71–80 of 177 posts
Re: Winamp clone in Swift for macOS
#72I liked winamp when I was using windows. I think any winamp clone should run on OSX Windows and Linux. I understand that cross-platform code may be annoying, but we really need applications that work on the three main operating systems.
I’m not entirely sure we need a Winamp clone on MacOS anyway. It seems unreasonable to expect that everyone who ever builds consumer software should make it work on every machine, though.
Why not also insist that it should work on iOS and Android? Those are undoubtedly the most commonly-used OSes at this point.
Re: Winamp clone in Swift for macOS
#73Why do people insist on still calling macOS "OS X" (or "OS/X" for that matter)?
I mean, muscle memory & fatigue may be part of it. I used MacOS for a number of years, then I used Mac OS X for 8 years, then OS X for 5 years, and now macOS for 9 years.
During that time I also used Windows and Linux from time to time. Their names didn't change in a way where just calling them that was perceived as incorrect.
Re: Winamp clone in Swift for macOS
#74Minor point: I read this as OS/2. The author may want to correct that. macOS naming and versioning is confusing enough. macOS was never known as OS/X. It was formerly known as OS X and Mac OS X. As a former OS/2 user, it really threw me off for a second. Also, you're using a trademark ("Winamp") in the name. So, expect a C&D from Llama Group or whomever. Aside from that, it looks really nice and well-designed! And it…
That's how I read it, too! I got excited! "Finally," I thought "I can run WinAmp on my OS/2 Machine". Then I clicked to the repo and saw it was just a Mac thing.
Re: Winamp clone in Swift for macOS
#75Earlier quoted context omitted.
Would you trust a binary from a random developer to not contain/deliver a trojan? Russianness has nothing to do with it.
These days executing random code is standard and if you don't do it you're wierd. Case 1: browsers automatically execute code from random sources. Case 2: People tell you to curl someurl.whatever | sh to install compilers (ie, the only way to use the rust rustc on non-rolling distros). And it goes on and on. It's not really an exception to standard practice to install applications. The only difference here is that it…
1. Browsers aggressively sandbox the code they run.
2. If you’re running curl | sh on random urls you don’t trust, you’re asking for trouble.
Running random executables you find online is a good way to get spyware and ransomware installed. I’m not saying that’s the case for re:Amp, but it’s absolutely still valid to tell people not to run random programs they find online.
Re: Winamp clone in Swift for macOS
#76Why does the title call it OS/X? It's macOS and it's described that way on the repo. Unfortunately his is just a recreation rather than an actual port, since the license for the source that was released prevents derivative works. Foobar2000 is the spiritual successor to Winamp and it runs on Windows and macOS as well as mobile.
The "About" section on that page says "Winamp clone in swift for OS/X" but their description says "Winamp macOS [...] A native macOS application..." Not sure I understand what OS/X is--I thought it said OS/2 for a second.
Re: Winamp clone in Swift for macOS
#77Why does the title call it OS/X? It's macOS and it's described that way on the repo. Unfortunately his is just a recreation rather than an actual port, since the license for the source that was released prevents derivative works. Foobar2000 is the spiritual successor to Winamp and it runs on Windows and macOS as well as mobile.
The "About" section on that page says "Winamp clone in swift for OS/X" but their description says "Winamp macOS [...] A native macOS application..." Not sure I understand what OS/X is--I thought it said OS/2 for a second.
Oh, I originally missed it on the side I only looked in the README.
I don't think it was ever called OS/X? It's been called OS X and Mac OS X but never OS/X.
Re: Winamp clone in Swift for macOS
#78Every single time something like this comes up I feel compelled to mention Audacious. See my previous comments: https://news.ycombinator.com/item?id=32779590 https://news.ycombinator.com/item?id=39965620 Like most days, I am using it right now on macOS.
Supports old Winamp skins too, which is the whole point!
Re: Winamp clone in Swift for macOS
#79Nice! Speaking of Winamp - are you using any alternative music player for iOS that you would recommend?
I started using https://github.com/kushalpandya/Petrichor a while ago. Though design is more akin to the default Apple Music app than WinAmp.
I've wanted a music player like the early versions of iTunes for a while, and this looks like it might fit the bill.
Those who've only known Music.app and later iTunes versions might be surprised to learn that there was a time when iTunes actually had a clean, intuitive UI: https://www.versionmuseum.com/history-of/itunes-app
Re: Winamp clone in Swift for macOS
#80Minor point: I read this as OS/2. The author may want to correct that. macOS naming and versioning is confusing enough. macOS was never known as OS/X. It was formerly known as OS X and Mac OS X. As a former OS/2 user, it really threw me off for a second. Also, you're using a trademark ("Winamp") in the name. So, expect a C&D from Llama Group or whomever. Aside from that, it looks really nice and well-designed! And it…
[deleted]