Given the state of that repo, all would have been forgiven and looked deliberate - like a nod to the fanbase if they had also left a folder in there with a bunch of .mp3.exe and Napster/Kazaa/Limewire installers… 😂
Not uncommon. My boss, a developer, doesn't know either. He's used a few VC systems and doesn't want to learn this new one that is entirely different lol
@@JilvinJacob It's ancient and sucked for 75% of its life. It still sucks, but it is now at least usable. If you do not know why, you must be a Millennial or Gen-Z. Always ask the question as to why something exists and then if it did everything it set out to do. Just because the why is fully reasonable, logical, and necessary does not mean the solution did not end up as total bollocks.
3:20 - It is funny to me that the license sais it is Version 1.0.1 in the headline and a couple lines below defines "The License" as referring to version 1.0 of the Winamp Collaborative License.
Hard to comment this but: 1. It was clear from day 0 it isn't open source 2. But you can build your own private copy Basically they don't want anyone to rip them off what they want/allow is: a. Skilled people with nostalgia build their own version. b. Allow the code to be studied so people can find out how to process mp3/sounds c. Triggering people with OCD to clean up their old code.
The LAME MP3 codec has existed for a long time and has a proper open-source license. People can learn from it if they want to understand how MP3 works and is implemented. There are also many open-source media players that already exist. This move is just for clout and attention.
I think it's more likely that after about a decade of stagnation and empty promises they're trying to get the hardcore winamp fans to fix it up for them, so they can monetize their aquisition one way or another. I don't even believe a) is really ok under that license. Firstly, if you make a copy and edit it, you have a fork. Then, unless you want to use winamp on the same machine that you build it, you have to copy the binary over, which is probably distribution.
Oh this ABSOLUTELY made me feel good. Good about my code, about my Git practices, about my general knowledge of licences… And yes, also of the times I accidentally included an API key or cert in a git repo and had to do some cleaning.
Probably the reason they decided to open source it. Maybe a library owner was filing suit that would have buried them and they tried to spin it as positive PR, which has since backfired badly.
@@privacyvalued4134 I doubt it. If they use GPL code, the entire project must be released under the GPL, without exception. They are attempting to release it under a different license.
18:18 "Why is it not a c?" Prime, this is English. The entire English spelling doesn't make sense. My favourite example? Every "c" in "Pacific Ocean" is pronounced differently.
To put a programming angle on that, grabbed this from usenet a loooong time ago: "The world would be a better place if Larry Wall had been born in Iceland, or any other country where the native language actually has syntax." -- Peter da Silva
Yes we all remember the default wav file it shipped with. You don't deserve upvotes just because you vomited out into a comments section. This is just as bad as, if not worse, than "first".
it's not the weirdest approach to have all the development-related stuff to be in the repo. And 7zip absolutely can be part of the build tools, as part of an intermediate or final packaging process
I like to keep sanitary files in directory and make use of environment exports for out-of-directory sensitive configs. This means I can publish a tarball of my local project directory.
These are the perils of taking private code repos to open source... I've seen many bad private repos that include checked in tools, private versions of third party sources, etc. Taking legacy code public requires a lot of careful, thoughtful work, which they clearly didn't have time or ability to do.
As a self taught programmer from back in the day, long before youtube. There are plenty of things I read about and had never heard pronounced. Words like "pseudo", "gif", or "sha". My programmers vocabulary is littered with them. The one saving grace, is that I am mainly talking to normies and all they hear is "blah, blah, blah, blah".
@@mattmurphy7030 Dude, I was 16 in 1982. We moved all the time, I had been in 8 schools over the previous 5 years. Totally had no friends. Had not been in town long enough to make any. Plus those were they days where "nerd' was still not a respected term. Also reading a word and hearing it pronounced is not the same thing. It was a decade before I realized the word I had seen on paper "ennui" was the same word that I had heard pronounced as "on-wee".
I keep running into this. Like, "wait, _that's_ how you say it? I'm not sure I can handle that now..." Like "GIF." I ain't saying jiff because that's too stupid sounding. "Combinator" is another one I've mostly got right now; I read it as com-bine-uh-tore years before hearing someone say it. And "segue" is not pronounced seeg as it turns out. A fun one was not something I first read but something I first heard pronounced, but by foreigners, namely Australians via the tech TV show Beyond 2000, who taught me to say "composite" like cawm'puh-zit rather than cuhm-paw'zit like the USian I allegedly am 😅 which drove one of my college buddies nuts 😆
@@Varadiio That's a good one. So is carb-you-retter. (Un?)fortunately I'd already heard those hundreds of times already so I didn't pick up the silly foreign pronunciation.
Shoutcast was a early video streaming service that provided indexing and codec support(I think they've pivoted to UA-cam in the modern) they did not host videos(as modern sites do) instead broadcasters had to upload directly from themselves to the audience or through server they rented and set up themselves. Mystery Science Theater 3000 stream was one of the most popular draws and specific seasons of South Park were also popular on the service.
I didn’t realize it was a video streaming service. I think it started as live audio streaming. I remember tuning into Shoutcast streams when I was in college and discovering new bands! There was a ton of great content there because community radio stations were putting their broadcasts on it
Wow, for a fairly popular media player back in the day, it's surprising to see what most devs would consider rookie mistakes today. Perhaps a sign that their dev is the type that figures out a way to hack things together, a process that works for them (e.g. putting git exes in the repo), and then move on with their day.
How hilarious, peanut gallery takes about a production codebase that was in use for a long time. I guarantee that there is expert level techniques and design in that codebase. Not using modern C++ idioms, because it wasn't invented when the code was written, isn't a legitimate critique.
@@cyberpunkspikewhile you have a point that there's probably expert level code there, that's not what the comment was about. It certainly wasn't making commentary on how modern the c++ may or may not be. It was about the utter incompetence suggesting whoever is currently developing winamp may be that sort of dev. The competence of code in the codebase says practically nothing about the current maintainers, as much of it was likely written more than 20 years ago. Hell, the code could be older than the person maintaining the repo.
The people involved in putting together this git repo are not the people who wrote WinAmp. They're simply the current right holders. Justin Frankel (the original creator) left AOL (the right holder at the time) back in 2004, 20 years ago
@@Bobbias That was not clear from the degenerate peanut gallery, they did not pay any respect to what was was obviously created by highly skilled people.
2:10 I think, if it's only internal, it's a mess. If I have a personal project, and then decide to publish some component, I clean it up and put it into a new repo as a library, which is then very clean.
I remember the first time I used Winamp, a friend gave me two 1.44mb floppy disks with Winamp.exe and a super compressed mp2 song. These files were compressed and split with Zip files to make it fit these diskettes. I can't remember what song it was but I do remember clearly that I was impressed with how good Winamp was compared to Windows Media Player and never used WMP ever again! That's also during this time when I first heard about Linux and I started to code with Visual Basic 4... 😆
@@Lodinn I like to believe it was mistrust in AOL. Nullsoft really didn't like AOL's corporate leadership, and Justin Frankel was straight up fired for being a rabblerouser making P2P stuff like Gnutella and Waste (secure p2p IM), so I think that left a bad stench for enthusiasts. The talent fled to Foobar2000 which to this day has a lot of impressive components that supplies everything the audiophile wants in a player, with the exception of fancy skinning.
@@lorenzo42p That's not the point. The point was that all they want to "fix" you can see anyway including proprietary code. And you can do whatever with them code. They'll cry to microsoft to remove forks, but the cat is out of the bag. Besides, why make troll pull request if you can just take the code and distribute closed source (I'm sure that somewhere in china already is a winamp, and even in us). As a note, winamp was the greatest program in my youth, the other players didn't even compared to it. Is a shame that they didn't put a lame bland GPL licence or MIT to really protect them rights and to allow good faith devs to contribute.
Oh, how the mighty have fallen. As a person that worshipped Winamp and became a designer due to my obsession with Winamp skins. This is tragically funny.
I recently had to figure out how to compile a really old version of ffmpeg that we use on Windows VMs on Linux, and it involved grabbing every dependency and building those from source as well. One of those dependencies could only be retrieved from SVN, that's probably why that binary exists in Winamp's build tools, considering how old the source code is...
Honestly while I do agree there is some level of amateurism going on, I don't think what Brodie did is a good way to behave either. It was closer to mockery than genuine criticism, and had too much derision to be considered advice. They have to start somewhere, and while they made a lot of mistakes, they were acting in good faith, and it'd be the least thing to do to at least give them some respect for that. Constructive criticism would have made for a much better video on top of being more fair. It also wouldn't feel like an asshole move. And love you Prime for highlighting the people who are actually trying to help Winamp to fix their shit.
@@Naruto-oc6mi Although correct there is no audible differences between flac and AAC a human can perceive. The point here is valuable learning around the codec itself. Google's Spatial Audio is the future, no more Dolby "ransomware" on the industry. Advances in Artificial Intelligence combined with Video and Audio Spectral Research is going bankrupt them, so "Dolby" enjoy that oil field for the moment. Atmos is the last of its kind.
In case it didn't come up later, Shoutcast DNAS was the Distributed Network Audio Server -- the actual exe that ran on windows or linux to act as the "connection point" for broadcasting and listening to streaming mp3 audio back in the days before places like Twitch and UA-cam brought their fancy video streaming. Interesting that they'd leaked that source too-- I thought they'd released the source for that a while ago, but it's been a very long time since I messed with that stuff.
The report is like that because it an escrow package of the source code. When you create an escrow package you must package up everything needed to recreate the product. That includes binaries, libraries, etc… everything needed to build it on every platform your product supports.
Woah.. SHOUTcast too? I know I at least have the sc_trans code because I'm the guy who ported it Linux. I might have had DNAS too but definitely never got access to the Winamp codebase. It was right around the time AOL bought out, so my contribution didn't last beyond the above described. Winamp, really whips the Llamas ass!
To clarify, sc_trans took the place of Winamp in a SHOUTcast station, streaming a playlist and re-encoding the output for the DNAS (which, while efficient, was bytes in/bytes out and had no encoding capabilities!) which allowed you to run a station completely on Unix-like machines no longer requiring a Windows machine and instance of Winamp for each channel (and bitrate - it was also handy for re-encoding the primary stream down to lower, actually personally I had a main instance passing through 320kbps mp3 to a local DNAS where 3 other sc_trans would re-encode to 128, 64, 32 (eventually 192, 128, 64) to avoid re-encoding an already lossy 128k stream into lower as most others did) Many of the huge stations at the time ran like this, but not all I don't think, most of the owners I knew did thought or (eventually) had custom software. Originally sc_trans was coded and compiled for Solaris Sparc boxen. Linux VPS were increasingly common around the time, so I pinged TP on AIM and got the code and ported it to work on Linux/x86. Which I don't recall being that difficult, but it wasn't getting done unless I was gonna do it. Many of the old big stations also had access to some special servers, that's partly why there wasn't such a push to port anyhow. Once those servers shut down, unfortunately I couldn't afford the bw costs to continue my station - I was one of the only ones to never run ads (audio or banners) or sponsorships. What a trip down memory lane. I was like 15 when I ported that sh*t.
Public reveals of formerly private code are a mess because already public code has people thinking about "I should make this better" and not just "I should make this work"
My understanding is that statute of limitations (or effectively that) does exist for copyright claims. But it relates to the time of learning about the infringement. So if you learn about someone infringing your work, you have 3 years from that date.
the reason you don't write your own license is because you have no idea how it will hold up in the courts the various GPLs, Apaches, etc have held what they promise when you actually try to legally enforce them
Their license satisfies Stallman's main gripe about closed software, so this is still a win, even if it's a shame they didn't go all in although it's understandable as many software companies would have a hard time convincing their legal and finance departments that communal software is a good idea.
Copyleft is the legal technique of granting certain freedoms over copies of copyrighted works with the requirement that the same rights be preserved in derivative works. It does not refer to FOSS.
Is dolby the reason I have to turn the volume up to hear voices and quickly turn it down when action happens to not wake my kids and neighbors? I appreciate the dramatics in the theater, but ffs, less than 1% of the movies I watch are in the environment.
@ThePrimeTime @ 16:05, if you rely on internet as much as you do (clearly), I suggest getting a load balancer (I use a relatively cheap TPLink all-in-one with hardware firewall), and balance between two types of internet connections (SDL, Cable, Fiber whatnot, etc.). It will be the most reliable and low latency connection you have ever used (assuming hardline) and no one connection will use all the bandwidth (unless you explicitly use a software that can bond them). So, it's like built in QoS but better because of no real overhead. Most people don't even know you can do it. I can't state enough how much of a difference it makes. Best!
"may not distribute" doesn't mean you can't fork - just means the fork can't be public repo you _can_ indeed use the source for personal usage, and I think GH let's you PR that back but maybe I'm wrong - IDK - I'm just a dumb dev
Im pretty sure that every fork of a public repo must be necessarily public too, so up until the moment you get merged (if ever) you will be distributing modified winamp code and going against the license
15:20 It's already absolutely clear that Winamp developers never RTFM for Git. And they probably don't fully grok Windows either keeping those .exe files in random locations.
2:00 It's because Brodie is a Linus glazer...anything other than the GNU/Linux kernel after the holier-than-thou spaz makes his final judgements could ever be considered "clean code" or a release.
In all fairness to 7z not being a build tool... It could be. Part of the build process could be packaging data files into an archive. Games do this all the time.
This is one of the main reasons games have huge updates, btw. Most devs are lazy. Archive files are massive. Individual files need edits. Just ship a new archive. Responsible devs will instead ship you the loose files, and their launcher/patcher is also an archiver. It does the repacking on the client, saving a ton of bandwidth.
For my personal projects I often have them as "Source Available" so if someone can learn from anything I did then cool but not to just take my work and sell it.
Open source doesn't require you to lead a community. You can use MIT, and state that you're not committing to anything in the README. That way, people can do whatever they want, without expecting anything from you.
The developers not caring about licences is kinda crazy, since there are ready made licenses for exactly the same reason. I'm confident there is a "Idc, do whatever" license that's well written a 3 min google search away.
Winamp was fine. The thing is there was nothing better at the moment so it kinda rocked. Simple, efficient, customizable. It was the chocolate ice cream. Only a few crazy ones would not accept it. But it grew old, probably most of the user base now uses either default OS music player or foobar and only in those cases where youtube music, spotify and itunes don't cut it, which is a niche population. This does not spark joy.
21:45 Hmm. There's a valid argument to be made against the GitHub TOS rules regarding licenses restricting forks. It's possible to create a repo where forking the repo creates a major legal risk for the person forking but NOT the original repo owner. Something along the lines of, "You can fork this repo BUT you take on the legal risks associated with doing so. Here are the reasons for this warning.... We won't sue you, but someone else probably will! Therefore forking this repo is highly discouraged and you should consult a lawyer first." That doesn't technically violate the GitHub TOS rules regarding forking but will cause most people to pause before hitting the fork button.
Unfortunately this right here is exactly why companies don't usually open source their commercially obsolete software. Even if the software would still have a dedicated cult following and it would be a major PR victory for the company. To properly release anything the code base needs to be fully verified and it will cost money and time as the last thing companies want, is that random people from internet will do this verification publicly.
The Winamp situation really whips the llama's ass
It whips it, hard.
llama tested, mother approved.
The late 90's are calling
From every direction.
Those were the days.
Winamp + Topaz skin + LimpBizkit.mp3.exe
Should be freely distributed again in 2024.
you summed up my youth right there
just double click this sketchy limewire link, and we're IN.
The time where you curated your own music and copied from friends. Damn I missed those times.
Given the state of that repo, all would have been forgiven and looked deliberate - like a nod to the fanbase if they had also left a folder in there with a bunch of .mp3.exe and Napster/Kazaa/Limewire installers… 😂
.mp3.exe ☠
This isn't regular incompetence, this is advanced incompetence!
Terminal stage incompoopness
I think they want to do it -- lol. This whole thing is hilarious to me.
100% agree!
I'd give a thumbs up but it's currently at 69 and I don't want to change that.
? does not compute..
The guy approving the changes was the CTO of Winamp and has been a CTO for some 20 years, but doesn't know how to use Git 🙄
Not uncommon. My boss, a developer, doesn't know either. He's used a few VC systems and doesn't want to learn this new one that is entirely different lol
Git is not that old.
Bro was there when they forged the first bit, 3000 years ago 😅
Oof
@@JilvinJacob It's ancient and sucked for 75% of its life. It still sucks, but it is now at least usable. If you do not know why, you must be a Millennial or Gen-Z. Always ask the question as to why something exists and then if it did everything it set out to do. Just because the why is fully reasonable, logical, and necessary does not mean the solution did not end up as total bollocks.
Src instead of src is gonna give me nightmares today.
Macintosh folders used to have a resource fork. Sometimes you would decompress a fresh copy of an archive and all the icons were crooked.
@@overclucker that sounds a𝘯noying
Windows.
Program Data
It's a Windows app.
This is the multi-dimensional opposite of "JUST GIVE ME THE .exe" situation
JUST GIVE ME THE CODE
lol
3:20 - It is funny to me that the license sais it is Version 1.0.1 in the headline and a couple lines below defines "The License" as referring to version 1.0 of the Winamp Collaborative License.
It's a rounding error. Pay it no mind. 😂
OMG that's hilarious and is a further display of the complete incompetence.
It’s a no-copy license 😂😂😂
I prefer "copy-nope" as Prime said 😆
It's a left-copy right license.
I worked on Winamp, this isn't the original Winamp2/3/5 codebase. Not even close!
What's different?
👀
interesting, you should publish about this. What about details here ?
I also worked on winamp, this is the original Winamp2/3/5 codebase. Not even far!
"The Good Luck With That Shit License" alone made this worth the watch.
Hard to comment this but:
1. It was clear from day 0 it isn't open source
2. But you can build your own private copy
Basically they don't want anyone to rip them off what they want/allow is:
a. Skilled people with nostalgia build their own version.
b. Allow the code to be studied so people can find out how to process mp3/sounds
c. Triggering people with OCD to clean up their old code.
EXCELLENT take
The LAME MP3 codec has existed for a long time and has a proper open-source license. People can learn from it if they want to understand how MP3 works and is implemented. There are also many open-source media players that already exist. This move is just for clout and attention.
I think it's more likely that after about a decade of stagnation and empty promises they're trying to get the hardcore winamp fans to fix it up for them, so they can monetize their aquisition one way or another.
I don't even believe a) is really ok under that license. Firstly, if you make a copy and edit it, you have a fork. Then, unless you want to use winamp on the same machine that you build it, you have to copy the binary over, which is probably distribution.
2c cannot be done if you cannot create a fork
@@mattymattffs CANNOT MAKE A PUBLIC FORK! Anyone can clearly make a private fork and issue a pull request.
Oh this ABSOLUTELY made me feel good. Good about my code, about my Git practices, about my general knowledge of licences… And yes, also of the times I accidentally included an API key or cert in a git repo and had to do some cleaning.
Just to add to the issue, it seems several GPL licensed libraries were found in the code base.
Probably the reason they decided to open source it. Maybe a library owner was filing suit that would have buried them and they tried to spin it as positive PR, which has since backfired badly.
@@privacyvalued4134 I doubt it. If they use GPL code, the entire project must be released under the GPL, without exception. They are attempting to release it under a different license.
@@privacyvalued4134 Yeah, but they didn't actually open source it, and the GPL requires *no additional restrictions*
@@privacyvalued4134 Well they didn't open source it, so no
O_O
"Here's a license for you to not be able to do anything."
You'll be able to work for them for free!
They'll still let you whip the llamas a$$
@@swdev245 that's the neat part, you can't.
30:23 Exactly why I never allow UA-cam videos to end when screen sharing.
😭 ikr...
also, i accedtly clicked on next video trying to pause that
18:18 "Why is it not a c?"
Prime, this is English. The entire English spelling doesn't make sense.
My favourite example? Every "c" in "Pacific Ocean" is pronounced differently.
That is the best thing I've heard today holy moly
Lucky you don't have a ton of conjugations and verb tenses, like we do in Spanish 😅 although it's nice to have one sound per letter.
The c from Ocean is the same c from the first c of pacific
So ur example is wrong
To put a programming angle on that, grabbed this from usenet a loooong time ago: "The world would be a better place if Larry Wall had been born in Iceland,
or any other country where the native language actually has syntax." -- Peter da Silva
@@arjix8738 Nope. The first C is pronounced like an S, the second is like a K or CK, and the third is SH. Three different sounds.
Winamp was the mp3 player of choice back in the 90s. I had all kinds of crazy skins for it and it was amazing.
It whipped the llamas ass.
Frauhofer for encoding and winamp for listening.
You can still use it.
Its still the player of choice for me. Nothing beats the custom skins and visualizer imo
and fb2k rules the scene now
_It really whips the llama's a*s!_
I heard that in my head along with the baaaaa 🐑 sound after 😂
Yes we all remember the default wav file it shipped with. You don't deserve upvotes just because you vomited out into a comments section. This is just as bad as, if not worse, than "first".
The llama is laughing it's a$s off at this! No way it isn't..
You can say ays, UA-cam is ass sometimes but not that ass.
TortoiseSVN is there most likely because WinAmp probably used SVN in the past.
Or still does, which would explain at least to some degree, the utter incompetence with git of whoever is managing the repo.
I run a (private) repo with a whole chonk of git-svn commits when I imported from SVN. I had previously imported from CVS to SVN.
i would be even more sympathetic to them not using verisoning then
all versioning systems are convoluted shit
it's not the weirdest approach to have all the development-related stuff to be in the repo. And 7zip absolutely can be part of the build tools, as part of an intermediate or final packaging process
@@mduvigneaud Did Perforce -> SVN -> Git migration, for a 30 years old code repo, most initial senior devs probably are retired or dead by now.
I started using git and created a repo for the first time a few weeks ago. One of the first things i did was learn how to exclude files from commit.
I like to keep sanitary files in directory and make use of environment exports for out-of-directory sensitive configs. This means I can publish a tarball of my local project directory.
These are the perils of taking private code repos to open source... I've seen many bad private repos that include checked in tools, private versions of third party sources, etc. Taking legacy code public requires a lot of careful, thoughtful work, which they clearly didn't have time or ability to do.
After you mentioned "Grammarly" I got a "Grammarly" ad. And I'm re-enforcing this youtube behavior with this commnent. Let me say it again: Grammarly.
Grammarly
As a self taught programmer from back in the day, long before youtube. There are plenty of things I read about and had never heard pronounced. Words like "pseudo", "gif", or "sha". My programmers vocabulary is littered with them. The one saving grace, is that I am mainly talking to normies and all they hear is "blah, blah, blah, blah".
Being self taught != having no friends
And pseudo is plain English lol
@@mattmurphy7030 Dude, I was 16 in 1982. We moved all the time, I had been in 8 schools over the previous 5 years. Totally had no friends. Had not been in town long enough to make any. Plus those were they days where "nerd' was still not a respected term.
Also reading a word and hearing it pronounced is not the same thing. It was a decade before I realized the word I had seen on paper "ennui" was the same word that I had heard pronounced as "on-wee".
I keep running into this. Like, "wait, _that's_ how you say it? I'm not sure I can handle that now..." Like "GIF." I ain't saying jiff because that's too stupid sounding. "Combinator" is another one I've mostly got right now; I read it as com-bine-uh-tore years before hearing someone say it. And "segue" is not pronounced seeg as it turns out.
A fun one was not something I first read but something I first heard pronounced, but by foreigners, namely Australians via the tech TV show Beyond 2000, who taught me to say "composite" like cawm'puh-zit rather than cuhm-paw'zit like the USian I allegedly am 😅 which drove one of my college buddies nuts 😆
@@PassifloraCerulea Gotta hit 'em with the AL-YOU-MINI-UM! It's just so much better right guys? *crickets*
@@Varadiio That's a good one. So is carb-you-retter. (Un?)fortunately I'd already heard those hundreds of times already so I didn't pick up the silly foreign pronunciation.
Shoutcast was a early video streaming service that provided indexing and codec support(I think they've pivoted to UA-cam in the modern) they did not host videos(as modern sites do) instead broadcasters had to upload directly from themselves to the audience or through server they rented and set up themselves.
Mystery Science Theater 3000 stream was one of the most popular draws and specific seasons of South Park were also popular on the service.
I didn’t realize it was a video streaming service. I think it started as live audio streaming. I remember tuning into Shoutcast streams when I was in college and discovering new bands! There was a ton of great content there because community radio stations were putting their broadcasts on it
Shoutcast was amazing. It's since been closed down, but there's stil Icecast.
17:22 - I needed this. Thank you.
Bro doubled the runtime and the story. Prime magic.
There are two types of devs, those who use secret scan in their pipelines, and those that will use secret scan in their pipelines after they leak
Thanks for the heads-up, I guess.
Wow, for a fairly popular media player back in the day, it's surprising to see what most devs would consider rookie mistakes today. Perhaps a sign that their dev is the type that figures out a way to hack things together, a process that works for them (e.g. putting git exes in the repo), and then move on with their day.
How hilarious, peanut gallery takes about a production codebase that was in use for a long time. I guarantee that there is expert level techniques and design in that codebase. Not using modern C++ idioms, because it wasn't invented when the code was written, isn't a legitimate critique.
@@cyberpunkspikewhile you have a point that there's probably expert level code there, that's not what the comment was about. It certainly wasn't making commentary on how modern the c++ may or may not be.
It was about the utter incompetence suggesting whoever is currently developing winamp may be that sort of dev. The competence of code in the codebase says practically nothing about the current maintainers, as much of it was likely written more than 20 years ago. Hell, the code could be older than the person maintaining the repo.
The people involved in putting together this git repo are not the people who wrote WinAmp. They're simply the current right holders. Justin Frankel (the original creator) left AOL (the right holder at the time) back in 2004, 20 years ago
It's just a company sold and sold and sold and is now the source code is in the hands of the last remaining person.
@@Bobbias That was not clear from the degenerate peanut gallery, they did not pay any respect to what was was obviously created by highly skilled people.
"we busy building rn cant be bothered with legal" is such a funny line
2:10 I think, if it's only internal, it's a mess. If I have a personal project, and then decide to publish some component, I clean it up and put it into a new repo as a library, which is then very clean.
"as a kid" - I was 26 when WinAMP was released.
Time flies.
At least you were not released when WinAMP was 26. 😇
I remember the first time I used Winamp, a friend gave me two 1.44mb floppy disks with Winamp.exe and a super compressed mp2 song. These files were compressed and split with Zip files to make it fit these diskettes. I can't remember what song it was but I do remember clearly that I was impressed with how good Winamp was compared to Windows Media Player and never used WMP ever again! That's also during this time when I first heard about Linux and I started to code with Visual Basic 4... 😆
The good old days. This suddenly reminds me of the songs I listen back then. Time to listen to them again, I guess.
"I can't believe I didn't think of that." That's because you have a soul.
Winamp, ICQ man those were the days!!
icq was the best back then, as was winamp. I still remember my icq number, but can't remember any phone number other than my own current phone number.
UH OH!
Makes me wonder how and why they've died. ICQ I kind of get it, but why did Winamp get displaced by foobar and AIMP and what have you?
@@lorenzo42p Same. 45168594. It's muscle memory mostly. I still don't get why MSN took over, it was inferior in every way to ICQ.
@@Lodinn I like to believe it was mistrust in AOL. Nullsoft really didn't like AOL's corporate leadership, and Justin Frankel was straight up fired for being a rabblerouser making P2P stuff like Gnutella and Waste (secure p2p IM), so I think that left a bad stench for enthusiasts. The talent fled to Foobar2000 which to this day has a lot of impressive components that supplies everything the audiophile wants in a player, with the exception of fancy skinning.
You cannot fork it, but you can git clone with all the modifications
Someone should tell em
if you clone it, how do you make a pull request?
@@lorenzo42p That's not the point.
The point was that all they want to "fix" you can see anyway including proprietary code.
And you can do whatever with them code.
They'll cry to microsoft to remove forks, but the cat is out of the bag.
Besides, why make troll pull request if you can just take the code and distribute closed source (I'm sure that somewhere in china already is a winamp, and even in us).
As a note, winamp was the greatest program in my youth, the other players didn't even compared to it. Is a shame that they didn't put a lame bland GPL licence or MIT to really protect them rights and to allow good faith devs to contribute.
I'm certain Winamp had a license for Dolby stuff to use, but obviously doesn't allow them to distribute the source outside of the company.
AmigaAMP from the 1990's is now retroactively in violation of the license. Someone please dig up Commodore and sue them.
FlappyBird is not a trademark of original creator anymore. Nguyen Ha Dong confirmed he has nothing to do with this "new flappybird".
This happens all the time, but for unknown repos with little numbers of eyes on them. I would know, I do it all the itme
Oh, how the mighty have fallen. As a person that worshipped Winamp and became a designer due to my obsession with Winamp skins. This is tragically funny.
@ThePrimeTime Thanks for doing this! I sent it to you via Twitch and a subscriber! So wanted to see and hear your commits!
Winamp - it really whips the lawyers ass!
From every direction
I recently had to figure out how to compile a really old version of ffmpeg that we use on Windows VMs on Linux, and it involved grabbing every dependency and building those from source as well. One of those dependencies could only be retrieved from SVN, that's probably why that binary exists in Winamp's build tools, considering how old the source code is...
Honestly while I do agree there is some level of amateurism going on, I don't think what Brodie did is a good way to behave either.
It was closer to mockery than genuine criticism, and had too much derision to be considered advice.
They have to start somewhere, and while they made a lot of mistakes, they were acting in good faith, and it'd be the least thing to do to at least give them some respect for that. Constructive criticism would have made for a much better video on top of being more fair. It also wouldn't feel like an asshole move.
And love you Prime for highlighting the people who are actually trying to help Winamp to fix their shit.
I would have very much liked to see them move to a GPL, but this was still a win. Seeing Brodie and other's adverse reaction embarrases me.
Brodie's annoying af
Wanted a leak of AC-3 and E-AC-3 compression methods. AAC codec is good for research as its still used for stereo audio broadcasting.
That deleted directory Src/vlb/ contains lots of goodies.
git checkout 0003d3d^1
cd Src/vlb/
No no aac is lossy, the minimal standar is flac, lossless and small size
@@Naruto-oc6mi Although correct there is no audible differences between flac and AAC a human can perceive. The point here is valuable learning around the codec itself.
Google's Spatial Audio is the future, no more Dolby "ransomware" on the industry. Advances in Artificial Intelligence combined with Video and Audio Spectral Research is going bankrupt them, so "Dolby" enjoy that oil field for the moment.
Atmos is the last of its kind.
Prime needs to commit to the mullet like Brodie commits to the neck beard.
oh yes
This as well as the wild speculation on how good AI will be at programming gives me a ton of hope as someone who just got into software engineering.
Github would bare the blame if they dont take it down after a DMCA request
Nope GitHub explicitly allows forking in TOS
That's right. And UA-cam had the right to the first child after you post a comment on UA-cam. Thanks for your support!
1:32 video should’ve ended right here when prime skips to the end of the video
In case it didn't come up later, Shoutcast DNAS was the Distributed Network Audio Server -- the actual exe that ran on windows or linux to act as the "connection point" for broadcasting and listening to streaming mp3 audio back in the days before places like Twitch and UA-cam brought their fancy video streaming.
Interesting that they'd leaked that source too-- I thought they'd released the source for that a while ago, but it's been a very long time since I messed with that stuff.
Now just imagine if video game studios had to release their game servers when shutting down a game that makes no money
The “look, but don’t touch” license
The report is like that because it an escrow package of the source code. When you create an escrow package you must package up everything needed to recreate the product. That includes binaries, libraries, etc… everything needed to build it on every platform your product supports.
I'm just glad that no matter how bad I am at actually using Git, I'll always be good enough for Winamp.
This project makes me feel good!
Woah.. SHOUTcast too? I know I at least have the sc_trans code because I'm the guy who ported it Linux. I might have had DNAS too but definitely never got access to the Winamp codebase. It was right around the time AOL bought out, so my contribution didn't last beyond the above described.
Winamp, really whips the Llamas ass!
To clarify, sc_trans took the place of Winamp in a SHOUTcast station, streaming a playlist and re-encoding the output for the DNAS (which, while efficient, was bytes in/bytes out and had no encoding capabilities!) which allowed you to run a station completely on Unix-like machines no longer requiring a Windows machine and instance of Winamp for each channel (and bitrate - it was also handy for re-encoding the primary stream down to lower, actually personally I had a main instance passing through 320kbps mp3 to a local DNAS where 3 other sc_trans would re-encode to 128, 64, 32 (eventually 192, 128, 64) to avoid re-encoding an already lossy 128k stream into lower as most others did)
Many of the huge stations at the time ran like this, but not all I don't think, most of the owners I knew did thought or (eventually) had custom software.
Originally sc_trans was coded and compiled for Solaris Sparc boxen. Linux VPS were increasingly common around the time, so I pinged TP on AIM and got the code and ported it to work on Linux/x86. Which I don't recall being that difficult, but it wasn't getting done unless I was gonna do it.
Many of the old big stations also had access to some special servers, that's partly why there wasn't such a push to port anyhow.
Once those servers shut down, unfortunately I couldn't afford the bw costs to continue my station - I was one of the only ones to never run ads (audio or banners) or sponsorships.
What a trip down memory lane. I was like 15 when I ported that sh*t.
Been following STL for a long time. This guy is great!
That ending is sus though... AI generated tomfoolery 👀👀👀👀
Public reveals of formerly private code are a mess because already public code has people thinking about "I should make this better" and not just "I should make this work"
Wow, this *really* whips the llama's ass!
My understanding is that statute of limitations (or effectively that) does exist for copyright claims. But it relates to the time of learning about the infringement. So if you learn about someone infringing your work, you have 3 years from that date.
The real heros wear their capes backwards 😷
As in, aprons?
I loved Winamp as a kid, now it’s worse than my wall clock
17:11 "Winamp: It REALLY whips the llama's ass" :J
the reason you don't write your own license is because you have no idea how it will hold up in the courts
the various GPLs, Apaches, etc have held what they promise when you actually try to legally enforce them
Their license satisfies Stallman's main gripe about closed software, so this is still a win, even if it's a shame they didn't go all in although it's understandable as many software companies would have a hard time convincing their legal and finance departments that communal software is a good idea.
Copyleft is the legal technique of granting certain freedoms over copies of copyrighted works with the requirement that the same rights be preserved in derivative works.
It does not refer to FOSS.
I've been using winamp since 2004. I still use it. You just have to download a dll to run the latest release, which must have been like 2005.
Easier to just get WACUP these days. WinAmp Community Update Project. It has all the files needed to run it on modern computers.
the clip of trying to scroll through yaccine's timeline is so funny
Where’s JetAudio now?
24:00 to be fair, the twitter post didn't say they'd make it open source, it said they'd make the source available.
Brodie is my favorite Linux UA-camr!
Linux Vtuber
Chill 😭 @@PragMero
Is dolby the reason I have to turn the volume up to hear voices and quickly turn it down when action happens to not wake my kids and neighbors? I appreciate the dramatics in the theater, but ffs, less than 1% of the movies I watch are in the environment.
@ThePrimeTime @ 16:05, if you rely on internet as much as you do (clearly), I suggest getting a load balancer (I use a relatively cheap TPLink all-in-one with hardware firewall), and balance between two types of internet connections (SDL, Cable, Fiber whatnot, etc.). It will be the most reliable and low latency connection you have ever used (assuming hardline) and no one connection will use all the bandwidth (unless you explicitly use a software that can bond them). So, it's like built in QoS but better because of no real overhead. Most people don't even know you can do it. I can't state enough how much of a difference it makes. Best!
You mean that their ChatGPT'd license is wrong? Nice :D
@28:38 you can see in the Answer that Winamp was later sold to Radionomy. So it's not really AOL's responsibility anymore.
"may not distribute" doesn't mean you can't fork - just means the fork can't be public repo
you _can_ indeed use the source for personal usage, and I think GH let's you PR that back
but maybe I'm wrong - IDK - I'm just a dumb dev
Im pretty sure that every fork of a public repo must be necessarily public too, so up until the moment you get merged (if ever) you will be distributing modified winamp code and going against the license
I find it really surprising that there aren’t more video/audio players available for desktop OSs.
15:20 It's already absolutely clear that Winamp developers never RTFM for Git. And they probably don't fully grok Windows either keeping those .exe files in random locations.
Let me just remind everyone that Andrew Kelley is working on remaking the ultimate music player Groove Basin using Zig
2:00 It's because Brodie is a Linus glazer...anything other than the GNU/Linux kernel after the holier-than-thou spaz makes his final judgements could ever be considered "clean code" or a release.
10:05 Dolby isn't going to care about 10+ year old AAC code.
...they ARE going to care that it was released to begin with. :P
23:00
Capes?
There's a possibility they don't even wore any pants atm.
bro, i have never seen better kekw definition than this 🤣
WinAmp appears to have run out of llamas. Yikes.
I love that Bobs in the end 🤣
In all fairness to 7z not being a build tool... It could be. Part of the build process could be packaging data files into an archive. Games do this all the time.
This is one of the main reasons games have huge updates, btw. Most devs are lazy. Archive files are massive. Individual files need edits. Just ship a new archive. Responsible devs will instead ship you the loose files, and their launcher/patcher is also an archiver. It does the repacking on the client, saving a ton of bandwidth.
For my personal projects I often have them as "Source Available" so if someone can learn from anything I did then cool but not to just take my work and sell it.
So is source available vs. open source the new open source vs. free software?
Is Winamp still a thing? I haven’t used Winamp since what like 2000
Open source doesn't require you to lead a community. You can use MIT, and state that you're not committing to anything in the README. That way, people can do whatever they want, without expecting anything from you.
Just checked the repo, they still haven't taken it private or deleted it. Thanks for the commercial release of Qt 😂😂
The developers not caring about licences is kinda crazy, since there are ready made licenses for exactly the same reason. I'm confident there is a "Idc, do whatever" license that's well written a 3 min google search away.
Winamp was fine. The thing is there was nothing better at the moment so it kinda rocked. Simple, efficient, customizable. It was the chocolate ice cream. Only a few crazy ones would not accept it. But it grew old, probably most of the user base now uses either default OS music player or foobar and only in those cases where youtube music, spotify and itunes don't cut it, which is a niche population. This does not spark joy.
S-H-A is how I and very very many non-native english speakers say because it just makes a whole lot more sense.
Primeagen probably has some problems understanding text. First, it's SQL, and now it's SHA. He can't even get the vowel right, and he said shaw.
The day this video was released Winamp was at the top of the trending repositories. Funny that.
21:45 Hmm. There's a valid argument to be made against the GitHub TOS rules regarding licenses restricting forks. It's possible to create a repo where forking the repo creates a major legal risk for the person forking but NOT the original repo owner. Something along the lines of, "You can fork this repo BUT you take on the legal risks associated with doing so. Here are the reasons for this warning.... We won't sue you, but someone else probably will! Therefore forking this repo is highly discouraged and you should consult a lawyer first." That doesn't technically violate the GitHub TOS rules regarding forking but will cause most people to pause before hitting the fork button.
Unfortunately this right here is exactly why companies don't usually open source their commercially obsolete software. Even if the software would still have a dedicated cult following and it would be a major PR victory for the company.
To properly release anything the code base needs to be fully verified and it will cost money and time as the last thing companies want, is that random people from internet will do this verification publicly.
The original IBM PC's Bios is also "open source"... guess what happened to the manufacturers who copied it.
honestly the PRs were absolute gold
14:22 what's with that diagonal screen tear in the top left whenever the video content scrolls?