From a pragmatic perspective I agree. But I think you’re missing the point here. A lot of the most entertaining, and dare I say inspiring content, found on Hacker News is about exactly things like this. Things that seem silly, but are also very intentionally pushing the boundaries to the extreme/absurd.

I still have fond memories of the open source community’s warm welcome and amazing contributions to the project.

This is too weird for me. At least with programming languages I can consult the documentation and if the programming language isn’t behaving as documented, it’s obviously a defect and if you’re savvy enough you often have open channels that accept contributions. Can we say the same for Claude or other AI solutions?

However this conclusion made no sense as we had similar scenarios across our project that worked flawlessly. After intervening I determined the root cause was a combination of an async issue with the production code and some incorrect mocking that was covering up the async issue.

It never occurred to the AI agent to do some simple cross examination before essentially throwing in the towel?

Well that and I have to be mindful of running too many resource starving processes at the same time including WSL. Otherwise performance will quickly degrade. But that’s not much different than my 2015 ASUS zenbook running Linux off of 8gb of ram. In comparison my work laptop runs on 32gb of ram with much more powerful cpu cores.

WSL is my favorite and most used feature of Windows 11. So I’ll be happy as long as they don’t screw that up.

On the other hand, pipe “|” is brilliant!

https://www.newsweek.com/policing-thought-crime-should-have-...