Reminds me quite a bit of websocketd as well, which converts a stdin/stdout program to a websocket: http://websocketd.com/. - Source: Hacker News / 15 days ago

I hadn't even considered collecting traces/spans in this way yet, and have taken the approach of "stuff outputting logs in JSON format to stderr/local file". I usually end up writing a (temporary, structured) log message with the relevant span tags, but wouldn't it would be much better to run the actual trace/span code and be able to verify it locally without the ad-hoc log message? The prototype I built is a web... - Source: Hacker News / 10 months ago

I also used to use this (http://websocketd.com/) along with netcat(1) before just biting the bullet and writing my own websocket library for our server as we needed to scale up slightly. Source: over 1 year ago

Http://websocketd.com/ (Runs command line C or C++ programs as websocket programs, similar to inetd / CGI). Source: over 2 years ago

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around. Source: 6 months ago

Before actual update, confirm your shell is independent on python. It is important when you use fish:. - Source: dev.to / 10 months ago

> As for why I don't think that's their goal, just look at https://fishshell.com/ not one of the listed features requires them to drop POSIX compatibility entirely. “Sensible scripting” is right there. - Source: Hacker News / 10 months ago

This is the default behaviour of fish[1], by the way! [1]: https://fishshell.com. - Source: Hacker News / 10 months ago

Last suggestion? Give fish a go. Its amazing. https://fishshell.com/. Source: 11 months ago