If that sounds reasonable I'm happy to raise a PR for it

makes sense. please do. that and ci/cd for windows should go a long way in smoothing out windows stuff going forward

For sure. I can test macOS runners work correctly too, not sure if it's worth enabling them as well. The run times are relatively low (when it works... haha) so I don't think they're too expensive on build minutes

if it becomes a problem, we can always turn it off later

Yeah even with wsl you can have problems on Windows

@User yeah... I like WSL (as a developer/SRE who used to work for a Windows-heavy org), but I always found myself carrying both a Windows and Ubuntu system around with me because it was just more reliable and predictable

I'd use Linux at my new job given the choice, but it's not (yet) company policy 😅

Windows OpenSSH bugs were such a time sink pre-WSL: https://luke.carrier.im/notes/5bf79814-a7f0-40e9-9fb9-48112018fbde.html

i recently spun up a windows 2019 server for testing dendron on windows. spend the first ten minutes figuring out how to turn off

Internet Explorer Enhanced Security Configuration

so I can download chrome. i was also trying to avoid installing cygwin since i was just testing a npm script but realized I couldn't do edits because there wasn't (to my knowledge) a power shell based text editor available. so I ended up using notepad...

PowerShell should be able to run Vim/Emacs with some reasonable degree of competence

Or you use code with remote-ssh

The biggest issue IMO is the total mess of package management on Windows... you have to install Choco or Scoop to get anything done. WinGet is in a limited public preview and the quality of packages there is much better, but for some reason it doesn't even try to keep track of package versions. It's basically just a silent installer wrapper, there's no

winget update

apt/rpm/brew are amazing and it scares me that most developers I've encountered who work on Windows don't understand the value in working in the shell

That said, PowerShell is such a productive environment if you give it some time, and Windows sysadmins who work in it by default restore some faith in the ecosystem 😅

The only trouble i have with wsl is my yubikey and my openpgp Smartcard xD

Yubikeys should just emulate keyboard input, right?

(it's been a while since I've used mine haha)

hmm, the powershell in aws windows server 2019 doesn't seem to have it 😅

Yes and no like i said i have an gpg key on it. That i use for signing, encription and Auth use (ssh)

i've had productive windows setup before, I just need to tune it (usually involves cygwin since I've done most of my windows development there). at the time, i was just hoping for a quick in and out test without trying to replicate a unix based dev environment first 😨

They've gotten a lot more features since I last used one 😅

Yup, you'd have to install it yourself 😿

i believe that powershll is... powerful. i've heard anecdotes and the unix shell is certainly not perfect. was at a conference with Jeffrey Snover, the creator of powershell, who made some compelling points about it

I love the object pipeline, I think it's a great concept

yeah, its definitely more expressive than everything is text

do you know how powershell compares to running something like ipython? (besides piping since python really support that)

I've been curious about this too, but never tried it

those are some path based issues with eleventy and windows. working on fixing those issues, in the meawhile, if you're running windows 10, it should work if you run this under WSL or use cygwin

Did you run the plugin tests under Windows, @User? I'm getting this output before the suite just hangs: https://gist.github.com/LukeCarrier/d8381d6b2c199aa7c5da0f9b915fe995

This is directly under PowerShell and I'm not sure if the paths should look like that