I started Strawberry Perl (or more specifically, the original push for Vanilla Perl) because I wanted equality for Windows.
I spend most of my day on both Windows (desktop) and Linux (server) and I just wanted to not have to care about which one I happened to be on that moment.
While things have improved enormously, we're still not there yet. But I think we're now close to achieving something we can call "good-enough equality". I'll define this as the set of things that you would expect to work if Perl was written for Windows in the first place.
There are three things left to go to achieve this goal. They are (in order of importance)...
The continuing lack of a web scraping framework has the effect of disconnecting Windows users from the world of web services we've built. No online banking modules, no Flickr automation, or phpBB scripts, or ISBN queries, or Bugzilla queries, or Google/Yahoo/Baidu searching, or website testing, or any of the other hundreds of things that a normal internet citizen might want to do.
What makes it more annoying is that Mechanize itself actually works, it's just the test scripts that fail, because of HTTP::Server::Simple not working on Windows.
You can see the full sweep of CPAN out of bounds to Windows users here.
The good news is that Jesse Vincent is making progress on getting this working thanks to David Golden and up-and-coming Win32 build star KMX (who's also working on a new generation of bundled C libraries for Strawberry).
But the day that this starts working can't come soon enough, and I for one wouldn't mind if the mechanize tests would just skip the HTTP::Server::Simple things in the mean time.
Recently, we've seen a lot of traffic on #win32 from biologists trying to install BioPerl on Windows, but being unable to. One of the main reasons is due to the lack of DB_File, which that KMX has also helped us to fix (and hopefully will be available in Strawberry October).
Windows is the natural home of games, and the lack of SDL on Windows is a big deal. Any chance of providing an alternative to the PyGame behemoth (and it's attraction to younger developers) is moot until this works.
The new push to get the SDL back working again looks promising here, and I'm hopeful we'll see this resolved via some suitable Alien:: package in the next few months.
Once these three packages are working, I think we can say we have a Windows Perl that meets the standard for the types of tasks that most people do on Windows.
That will just leave crypto is our main deficit, but this isn't quite as obvious a failing as the others, and is not something we can fix in a single step.