Ofcourse, that ignores the fact that for many of these languages there are existing libraries and drivers to connect to databases that would not work with this embedded one, but still.
This reminds me of the Basicode system, which transmitted crossplatform programs over the radio... and in the Netherlands, some of the programs could then be checked against the checksummed program listings on Teletext...
Well, for the Dutch market there's Luna: https://www.nedap-luna.com/. This has the advantage of being integrated fully into a formal care structure and of several years of research in how to best present information specifically for patients with cognitive issues.
Well, the costs for the 'in' and 'out' reader are really not the major issue for most companies, as you could conceivably set a particular perimeter that cordons of 'secure' from 'not secure' and would only have to configure anti-passback for that perimeter. The real trick (and therefore problem) is in making sure that people do not walk through doors together, that is, making sure that only a single person passes the perimeter for a single access request. Single-person passages are way more costly than the readers, and have the additional problem of not allowing all that many people to pass per hour. That means that you may even need multiple for a given people flow. And that's leaving aside the convenience issues.
From TFA: 'pretty substantial code base too. About 55,000 lines of ruby code'. Am I the only one to think that 55k LoC is not pretty substantial? That's the amount of code you can easily deal with as a single person, no team required. No wonder doing CI locally sounds tempting, as there's probably not all that much integration in the first place.
I've run something similar for 5 years, using https://www.smartevse.nl/ as the brains. The main advantages over commercial EVSE's in my case were that I could loadbalance charging the car with the electricity demands of the house, and that I could have the EVSE itself inside, so that there's no 240V current on any circuit from the breaker box indoors towards the car when there's no car present.
I do intend to add a second sometime, so that I can put the EVSE in my home automation UI as well; the version 2 of smartevse that I use does not have a network connection, but it can be connected to be controlled by a version 3 that does.
Or a library who's code now only exists on the wayback machine... and of the modified version that you actually use only a single copy exists on an old machine that one of the devs in the company never bothered to hand in for recycling...
Never mind that it's part of a decade old contract stipulating a quarter century support...
Over the past decade, decade-and-a-half, it seems to have become quite common in at least the Netherlands to install taps that provide cold, hot and boiling water in new kitchens. These days, the higher end taps also do chilled and carbonated water.
The origin story for the boiling water tap is powdered instant soup, which isn't quite instant without instant boiling water... :)
I remember how I 'earned' my autographed copy... by asking 'so, how do you suppose we add interactivity to VRML? Binding with Java Applets? JavaScript?'
The world these days does look quite a bit different than it did in the 1990's... and yet some things aren't.
The problem with space sensing interfaces is one of intentionality. The best example of how this is hard that I can think of is that of a passive IR sensor wired to trigger opening a door. If that door is parallel to a hallway, the door will probably be opened a lot by people that have no intention whatsoever of going through the door.
It is that particular problem that is well captured by buttons: by decreasing the actual sensing area you increase the intentionality of the measurement. Furthermore, requiring specific directional movement increases it further.
Another example: the capacitive sensing 'buttons' on my washing machines can be accidentally activated by touching with the side of the arm, which can occur for instance when I'm loading detergent. That accidental activation is harder to achieve and easier to detect before accidental activation for physical buttons that have some travel.
Ofcourse, that ignores the fact that for many of these languages there are existing libraries and drivers to connect to databases that would not work with this embedded one, but still.