I came here to post this one. For about 25 years of my life I was tying my knots the wrong way and I just thought shoelaces just had to be re-tied periodically. I don't remember where I learnt to just tie the loop the other way. Now strain on the laces just serves to tighten the knot.
I like the board UI and it's a cool project idea. Did you find any good resources on programming the board representation and identifying legal moves? There doesn't seem to be a standard library or algo reference that I've seen for such a common problem.
They have some major differences. Enough so that I first tried Duplicati and ran into corruption issues so frequently that I sought out an alternative and luckily found Duplicacy.
Duplicacy has been stable for years now and I gladly pay the commercial license. It seemed like Duplicacy constructs a giant DB of all the files and manages everything that way, whereas Duplicacy's approach is much simpler and is less prone to corruption. The large DB approach seems to fail when the backup set contains a large number of files that many users manage.
That's right -- Duplicati constructs the giant house-of-cards DB). I sometimes need to run a $> ps -ax to remember which one I'm using when it comes time to change the config.
I suspect you're using the rtsp protocol to get the A/V streams from the camera, in which case I would consider your software another front-end for an IP CCTV system-- is that right?
There are plenty of IP CCTV solutions that use any number of manufacturer's cameras because of standard protocols, and that sort software should be fine to publish. However, if you're spawning the streams because the camera mfg. has a closed protocol and you're exploiting some bug, then maybe give it some more thought.
I don't really want to comment on whether or not DL is doomed to fail on the EMR, but coming from an EMR background, I can say he lays out very accurate points. I particularly like how he explains #3 concisely, and it's a point I use to criticize the private healthcare system.
The continual war between hospitals having to opportunistically charge for their services vs. the insurance industry having to take a default stance of deflection creates the massive, meaty layer of coding and billing waste. Thousands upon thousands of jobs exist just for this purpose, and I think any inefficiency in a single-payer system is more than offset by getting rid of that layer and everyone benefits.
