Fun fact, IE is still on windows 11, and it can be used though not through normal means. To any C#/.NET devs out there, on winforms the “browser” control is IE, and is still supported. Additionally some programs (like my company’s ERP) still can and do launch full standalone IE under certain situations.
It gets better. PowerShell 5, which is still the default installation on Windows 11, aliases `curl` and `wget` to `Invoke-WebRequest`. The fucked-up part is that Win11 includes the real `curl` too, but the alias shadows it, and you have to use `curl.exe`. The even more fucked-up part is that `Invoke-WebRequest` **still uses Internet Explorer** to parse the result, and will panic if `-UseBasicParsing` is not passed every time, or IE isn’t installed and initialized. I used to develop applications in PowerShell. I still wear the mental scars.
drcobaltjedi@programming.dev 5 days ago
Fun fact, IE is still on windows 11, and it can be used though not through normal means. To any C#/.NET devs out there, on winforms the “browser” control is IE, and is still supported. Additionally some programs (like my company’s ERP) still can and do launch full standalone IE under certain situations.
f4f4f4f4f4f4f4f4@sopuli.xyz 4 days ago
According to @rtxn@lemmy.world:
ReginaPhalange@lemmy.world 5 days ago
Oh man I’m still dreading the day that the backwards operated stuff in SAP GUI, made possible because of the IE engine, suddenly lose support.
I’m looking at you adobe interactive forms.
That shit is gonna cost thousands of dollars to migrate.
The_v@lemmy.world 5 days ago
Hmmm… wait a minute I have nightmares about this one - JDE