I would guess that the "typical" Windows user of Perl would prefer the MSI version because it will automatically associate .pl files with perl.exe thereby allowing them to double-click the script to run it. (And sadly, many Windows users, probably even many who have enough skills to write a simple script in perl, or at least copy/paste it, wouldn't know how to do manual associations in Windows without an MSI or installer-exe to do it for them.)
Personally, I use one of the PDL-portable copies of Strawberry with manual file associations, because I like the double-click, but I really want all those extra math libraries that come in that bundle that aren't in the normal MSI or portable Strawberries.
"poke the bear"
I'd much rather that they keep their focus on figuring out how to build newer versions of perl, so that we could get strawberry versions of 5.34 and 5.36. (Commit messages from November seem to indicate they are at least working on 5.34, but it seems to have paused again.)
I would guess that the "typical" Windows user of Perl would prefer the MSI version because ...
Yeah, but they're giving an unqualified recommendation for all users.
It's not the right recommendation for me, and it's apparently not the right recommendation for you.
I'd much rather that they keep their focus on figuring out how to build newer versions of perl, so that we could get strawberry versions of 5.34 and 5.36.
Sure, that's their important job ... but I don't see that getting the "recommendation" right is going to impact heavily on their capacity to get that job done.
I wouldn't be surprised if MSI also involved some Registry-Settings.
I'm also fond of the Portable Edition and hope newer Perl Versions will be supported soon.
StevieB's BerryBrew is also worth mentioning here.
But still, I can see the remains of an old installation can also sabotage the usage of a new Portable Strawberry.
One still needs to purge old remains, the advantage of a portable version is that there are none if it's the old version.
> But still, I can see the remains of an old installation can also sabotage the usage of a new Portable Strawberry.
..mmh this line in portableshell.bat should be enough to play it nicely, no?
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
It made me wonder why Strawberry Perl promoted the msi edition as the "Recommended version" ...so much
I think it's because strawberry perl use a hacky way to make perl portable. IIRC, it modify Config infomation in run time by a module named Portable.
I am trying to improve my English skills, if you see a mistake please feel free to reply or /msg me a correction