urtie · HackerTrans

hace 2 mesesdiscuss

Well, there was a neat feature that Mac OS X 10.4 and 10.5 had that got killed because the iPhone couldn't do it: you could call and send SMS through integration with a Bluetooth enabled phone. That functionality was then removed, and reintroduced a decade later with great fanfare, but only if you had an iPhone.

urtie

hace 7 mesesdiscuss

There are projects such as https://github.com/wasmerio/wasmer-java and https://wasmtime.dev/ that extend this embeddability to Java, .net, C, C++, rust, Python, Ruby and Go. Wouldn't want to call those 'JS et al'.

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.

urtie

el año pasadodiscuss

This reminds me of the Basicode system, which transmitted cross platform programs over the radio... and in the Netherlands, some of the programs could then be checked against the checksummed program listings on Teletext...

urtie

hace 2 añosdiscuss

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.

urtie

hace 2 añosdiscuss

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.

urtie

hace 2 añosdiscuss

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.

urtie

hace 3 añosdiscuss

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.

comments