if you accept my precognition.. I bet you have not to expect any issue.

My point of view is: according to this cnet serie of articles they are betting on hyper-high-level integration with mobile devices and they as always will not touch the under hood ecosystem. Our work in Perl on Windows is at a level they probably will never touch.

Fewer Win32::* XS modules we have on CPAN that interact directly with internal system calls survived since the WindowsNT era and they still works because the underlying OS component never changed.

Microsft OSs still supports ancient things like CLSID: EXPLORER ::{2227A280-3AEA-1069-A2DE-08002B30309D} (to open printers) never stopped working across versions.

The major mess they introduced over ages is the 32bit vs 64bit madness and the confusing path names and subtle filesystem redirection.. but we already survived to this.

Following in the realm of precognition, you can face minor issues in highly OS integrated fields like Task Scheduler or Services, so if you write Windows services in Perl (congratulations!) you must double check them on a newer OS. But, again, I still use year 2k code to parse events in Event Viewer and never faced "newer" problems: always same old ones :)

Anyway I'd really appreciate if you update this node as you find something related.

L*

G'day Discipulus,

Thanks for your feedback and thoughts on this.

The first linked article seemed very much like a marketing exercise. I was surprised at repeated references to "more Mac-like"; and, of course, the WOW-factor seems to be that they've discovered CSS:

.ms-window {
    border-radius: 0.5em;
}
[download]

OK, so that's very much a tongue-in-cheek comment; however, if the main changes are superficial, GUI-related ones, I can live with that.

It also looks like I could accidentally upgrade to Win11 when doing my normal, weekly updates: I'll need to keep an eye on that. That's under the "How will you download Windows 11 once it's generally available?" heading. Thanks for the indirect warning.

"Anyway I'd really appreciate if you update this node as you find something related."

That's more likely to come from respondents to this thread; however, if I do find other information, I'll certainly post it.

— Ken

Win11 replaces Win10

As we predominantly use refurbished Dell 4th generation Intel machines, we won't have the option to upgrade to Windows 11. I very much doubt these will be able to be upgraded to meet the pesky TPM requirement of Windows 11.

Given that it is four years in the future, I am confident that both Strawberry Perl and Active State will have their products compatible well before Windows 10 support ends. Of course it is one thing having Perl itself compatible with the platform, quite another to expect all the CPAN modules designed for Windows to become compatible. I guess that's where the issues will be most prevalent.

G'day Bod,

That's a good point about modules in, or associated with, the Win32:: namespace. I'll keep an eye on that. Thanks.

— Ken

I'm wondering if it's not still too early to ask, especially since you are not migrating soon.

Or do you hope this to be a "pinned" constantly visible thread which is actualized over months and years?

G'day Rolf,

I had also wondered if I was perhaps jumping the gun somewhat; however, if there is a fundamental change in 11.00 (I'm guessing at version number format) I'd like to know about it sooner rather than later.

My computer is for both personal and $work use — working remotely from home is the norm for me; I've been doing this for several years; it's not a temporary, Covid-related measure. For my own usage, I'd probably leave migration until as late as possible, perhaps mid-2025; but, for $work, it may need to be earlier (I don't have any dates on that yet).

There are potentially issues that affect $work computers but not my computer at home. The "Git for Windows", that I mentioned above, could be an example of this: some colleagues run Perl applications via "Git BASH". Although not affected directly by these, I'd still like to be in a position to offer feedback to others in the office.

I wasn't planning on providing ongoing updates to this thread as the 11.xx series matures. To be honest, I hadn't really given this any thought: I'd probably deal with future problems in separate threads: something like "Perl issue with MSWin 11.26" (as a purely fictitious example).

— Ken