News for hackers. Stuff that matters.
Re:Winamp source code leak by 0des on Monday November 29, 2021 @09:39AM (#29380344)
Winamp 2 was generally preferred. If I recall correctly, it skipped version 4 not because v2 + v3 = v5 but because nobody would want to download a Winamp 4 skin. Not kidding.
Re:Winamp source code leak by lelandfe on Monday November 29, 2021 @09:41AM (#29380371)
You're both right!

https://web.archive.org/web/20131219003849/http://www.winamp...

> What happened to Winamp 4? You're not imagining things. Yes, we skipped a version number for the following reasons: a) Winamp 5 combines the best aspects of Winamp 2 and Winamp 3 into one player. Hence Winamp 2 + Winamp 3 = Winamp 5! b) Who the hell wants to see a Winamp 4 Skin :P c) We think that a Fibonacci sequence for versioning might be pretty damn cool. d)We improved so much in Winamp 5 that we figured it warranted skipping a version. ;)

Re:Winamp source code leak by xmprt on Monday November 29, 2021 @03:40PM (#29384969)
I still don't understand. What's wrong with Winamp 4 skins?

Edit: Maybe I have to sound it out. Is it because 4 skin sounds like foreskin?

Re:Winamp source code leak by lelandfe on Monday November 29, 2021 @03:55PM (#29385176)
You got it :)
Re:Winamp source code leak by reaperducer on Monday November 29, 2021 @07:01PM (#29387046)
They thought a Winamp 4 skin would leave a bad taste in people's mouths, so they scratched it.
Re:Winamp source code leak by dequor on Monday November 29, 2021 @07:18PM (#29387170)
Well that definitely blew up in their face.
Re:Winamp source code leak by throwaway69123 on Monday November 29, 2021 @08:04PM (#29387506)
Downvoting this comment is like kicking someones dog.
Re:Winamp source code leak by diryawish on Monday November 29, 2021 @07:36PM (#29387311)
Snipped it.
[dead]
Re:Winamp source code leak by thedoctor_o on Monday November 29, 2021 @10:21AM (#29380832)
Supposedly they're still going to call it Winamp v6 assuming it happens. They've lied a number of times over the past 8yrs so don't hold your breathe but the new site is somewhat indicative of their disregard about why those still using Winamp (or clones of it) do so.

-dro

Re:Winamp source code leak by hermitdev on Monday November 29, 2021 @11:32AM (#29381783)
If the new website is any indicator of the quality of the new Winamp, it's going to be a huge nope from me.
Re:Winamp source code leak by lelandfe on Monday November 29, 2021 @11:35AM (#29381819)
They may win for the worst scrolljacking I've seen to date
Re:Winamp source code leak by 0des on Monday November 29, 2021 @11:13AM (#29381523)
>the clowns that made that awful new Winamp

You don't have to be like that.

Re:Winamp source code leak by zwirbl on Monday November 29, 2021 @12:12PM (#29382312)
The site didn't have to like that either
Re:Winamp source code leak by tomxor on Monday November 29, 2021 @03:42PM (#29384995)
> not because v2 + v3 = v5 but because nobody would want to download a Winamp 4 skin

I wish the people who named Gimp image editor were this thoughtful! Searching for image masking info has caught me out multiple times :/

Re:Winamp source code leak by monkeycantype on Monday November 29, 2021 @04:44PM (#29385670)
on multiple occasions when i've needed to know command line syntax I've googled 'man find'
Re:Winamp source code leak by scubbo on Monday November 29, 2021 @06:54PM (#29386984)
While learning jQuery and figuring out how to retrieve elements of the DOM, I googled "how to get head".
Re:Winamp source code leak by johnmaguire on Monday November 29, 2021 @10:26PM (#29388603)
Get the TLD for python.org wrong and it's less than work appropriate.
Re:Winamp source code leak by justbaker on Monday November 29, 2021 @10:58PM (#29388793)
Or school appropriate. I made this mistake circa 2008 lol
Re:Winamp source code leak by 3np on Monday November 29, 2021 @10:56PM (#29388777)
"how to get head" expertsexchange
Re:Winamp source code leak by iostream23 on Tuesday November 30, 2021 @12:15AM (#29389203)
Not to mention the hard coded file names a certain Linux screen capture utility leaves behind…
Re:Winamp source code leak by totetsu on Monday November 29, 2021 @10:03AM (#29380638)
NB four and fore are sound the same in some accents
Re:Winamp source code leak by lproven on Monday November 29, 2021 @10:55AM (#29381275)
Thank you for so delicately pointing out the problem/joke here -- I hadn't noticed it, not even back then.

My question is: in what English accents do "four" and "fore" *not* sound alike?

Re:Winamp source code leak by rrrrrrrrrrrryan on Monday November 29, 2021 @11:23AM (#29381665)
This is the Horse-Hoarse merger. [1]

> Accents that have resisted the merger include most Scottish, Caribbean, and older Southern American accents as well as some African American, modern Southern American, Indian, Irish, and older Maine accents.

If my understanding is correct, in some accents that don't pronounce their "R"s at the end of words, the vowel shape changes slightly while pronouncing "four," but "fore" is pronounced with a simple vowel.

[1] https://en.wikipedia.org/wiki/English-language_vowel_changes...

Re:Winamp source code leak by aasasd on Monday November 29, 2021 @12:37PM (#29382635)
Wiktionary sometimes comes handy in such musings, because it has IPA spellings and recordings of pronunciations, and marks the dialects—not always but frequently for more popular words.

https://en.wiktionary.org/wiki/fore

https://en.wiktionary.org/wiki/four

The IPA suggests that pronunciations of the two words are identical both with and without the merger, but I'm no specialist.

Re:Winamp source code leak by rrrrrrrrrrrryan on Monday November 29, 2021 @03:14PM (#29384661)
Just dug a little deeper, and I've arrived at this conclusion:

In accents with the merger, "four," "for," and "fore" are all always homophones.

In accents without the merger, "four" and "for" are never homophones.

And in some subset of these non-merged accents, "fore" may be pronounced identically to "four" (as listed in the IPA guide in your first link). In another subset, it may be pronounced identically to "for" (as implied by the "Homophones" section in that same link).

Re:Winamp source code leak by lproven on Monday November 29, 2021 @12:02PM (#29382171)
Fascinating. Thank you.

It is extremely hard for me to even _imagine_ this, as apparently my native accents both contain this merger. This is a rare experience for me, but a previous occurrence was discussing the rhotic-R phenomenon.

Re:Winamp source code leak by ziml77 on Monday November 29, 2021 @10:18AM (#29380810)
Thank you. This is what it took for me to realize why version 4 might be an issue. If I just saw "4 skin" I certainly would have gotten it. Somehow adding Winamp in front made it hard for me to interpret it the alternative way.
Re:Winamp source code leak by agumonkey on Monday November 29, 2021 @02:38PM (#29384208)
And now I have a totally different view on the smooth jazz band named fourplay
Re:Winamp source code leak by ConceptJunkie on Monday November 29, 2021 @10:13AM (#29380747)
Definitely true for American accents.
Re:Winamp source code leak by squarefoot on Monday November 29, 2021 @10:12AM (#29380740)
If memory serves, the latest unbloated version of WinAmp was called Winamp Classic, and its versions were in the 2.9x range.
Re:Winamp source code leak by thedoctor_o on Monday November 29, 2021 @11:10AM (#29381461)
5.x is just the 2.x base continued with newer plug-ins & newer apis for those plug-ins. Unchecking things during installation (e.g. choosing the lite install) or just removing the unwanted plug-ins was always an option to make a 5.x into a comparable 2.x install.

-dro