DS4Windows VS http-add-on

And there was also a fork available in the last year while the original dev was on a hiatus.

Personally I use CircumSpector's DS4Windows. It has restored rumble and lightbar passthru on my end. The lightbar passthru is kinda buggy but it kinda works.

Thankfully, Jibb already redirects the newer fork if you look at the Release page or literally the first Paragraph of README.md. So unlike DS4Windows (which took 6-7+ years to tell folks to move over to Ryochan4 fork...which said fork been discontinued and someone else took over. Welcome to FOSS. 😋), it should be easy enough to head over to Electronicks fork.

Final note: DS4Windows hasn't been updated since August 2021. Another group forked it and they're rewriting a lot of it. There is no release yet and no release date planned.

A couple of FOSS enthusiasts and myself have taken over the decade old game controller remapping tool DS4Windows (https://github.com/CircumSpector/DS4Windows) with the goal to rewrite major parts using latest dotnet patterns and technologies. There's still months worth of work left but despite being an ambitious task, it's quite doable and fun figuring out your way around someone else's massive code base. Join us if you like!

The DS4Windows project is not dead. There is a new team working on it called CircumSpector, but it may take a while for a update to be released since they are focusing on "modernizing" the code so it's easier to maintain it in the future. There are lots of changes going on under the hood, but "user visible" changes for now.

This is not exactly true. Check CircumSpector's DS4Windows.

KEDA ships with an HTTP add-on to enable HTTP scaling.

KEDA has a special scaler that creates an HTTP proxy that measures and buffers requests before they reach the app.

I am a core maintainer on the KEDA HTTP Addon project (https://github.com/kedacore/http-add-on). It's 100% written in Go and we are a small group looking for additional contributors. I believe there are interesting challenges ahead of us that will be enjoyable to solve.

If you're interested, please reach out. My username here is the same as my username on the Gophers and Kubernetes slack groups.

(You're of course welcome to just go pick up an issue in the repo if you'd prefer)

The KEDA HTTP Addon project contains three major components: the operator, scaler and interceptor.

Hacking on the KEDA HTTP Addon, I found myself having to do something familiar:

First, we need to finish the minimal infrastructure. The components and supporting artifacts (Helm charts, CI scripts, etc...) are being built in PR #2, and once we have them completed, we will merge it [5]. Second, we need to establish a roadmap. We're beginning to outline it now and will finish it shortly after merging.