Those old school style forms were much better than today's single page scrolling pages that are difficult to navigate and take up so much RAM.
Winamp 5.9
31–40 of 50 posts
Re: Winamp 5.9
#32Earlier quoted context omitted.
Kind of a bummer to hear they are giving up on theirs (if it even exists lol) But at the same time I wouldn't expect the people that put out that abomination of a frontpage to even know what's an xm file.
WinAmp's mod player was wildly inaccurate anyway, so it's probably not a great loss. IIRC it specifically didn't support a lot of IT features (instrument filter envelopes, etc)
I remember using the "oldskool" plugin with it which made their comparability noticably better.
Re: Winamp 5.9
#33> but the largest and hardest part was actually migrating the entire project from VS2008 to VS2019 Worst I've ever had to do was 2008 to 2015 but damn I don't envy those teams.
That is a monster migration. I wonder how big the migration compatibility list was. I haven't used VS since about 2017, but in some ways I miss it. It's big and unwieldy, but very powerful and helpful and was a staple of my 20s as a software dev.
Maybe it won't be so bad. Let's click build and see what fails?
*errors scroll up screen faster than any mortal can read for 20 minutes*
You know? Maybe I should check the docs.
Re: Winamp 5.9
#34No post body was provided.
Re: Winamp 5.9
#35Earlier quoted context omitted.
That is a monster migration. I wonder how big the migration compatibility list was. I haven't used VS since about 2017, but in some ways I miss it. It's big and unwieldy, but very powerful and helpful and was a staple of my 20s as a software dev.
Maybe it won't be so bad. Let's click build and see what fails? *errors scroll up screen faster than any mortal can read for 20 minutes* You know? Maybe I should check the docs.
I remember doing it to one of our legacy projects and the list was so long I just created new solutions and projects from scratch and copy the files over one at a time and ran them independently so I could slowly ensure everything worked
Re: Winamp 5.9
#36Earlier quoted context omitted.
It was in fact leaked. https://news.ycombinator.com/item?id=29379346
Oh wow. Is that source code from a newish version? (I don't see any files in the main root.)
The leaked source is from somewhere between 5.65 & 5.66. https://getwacup.com/blog/index.php/2021/04/17/what-does-the...
Re: Winamp 5.9
#37Those old school style forms were much better than today's single page scrolling pages that are difficult to navigate and take up so much RAM.
Doesn't help that I have to scroll left and right to read the text on mobile though.
Would be nice to have a forum software that's:
* lightweight * mostly web 1.0 tech * UI usable on desktop and mobile
Re: Winamp 5.9
#38Those old school style forms were much better than today's single page scrolling pages that are difficult to navigate and take up so much RAM.
Doesn't help that I have to scroll left and right to read the text on mobile though. Would be nice to have a forum software that's: * lightweight * mostly web 1.0 tech * UI usable on desktop and mobile
If you subtract the web 1.0 requirement, then Discourse might be for you.
Re: Winamp 5.9
#39> but the largest and hardest part was actually migrating the entire project from VS2008 to VS2019 Worst I've ever had to do was 2008 to 2015 but damn I don't envy those teams.
I loved Visual Studio (and Visual C++ before it), but after firing it up again and seeing the same ridiculous defects 10 years later was pretty disheartening.
This is a pretty good rundown: https://goldmanosi.blogspot.com/2012/05/visual-studio-is-it-...
Re: Winamp 5.9
#40> but the largest and hardest part was actually migrating the entire project from VS2008 to VS2019 Worst I've ever had to do was 2008 to 2015 but damn I don't envy those teams.
Had to do many VS migrations and in the end, proper version control system hygiene has helped a lot. Moving the strict necessary code and metadata only (.sln, .csproj and so on) and letting the IDE rebuild the rest has been the easiest.