undefined | Better HN

0 pointsjsmith454y ago0 comments

He is a paid Home Assistant core developer. (Hired by the company the project's founder created to generate sustainable income for developing the project by offering optional value-add services).

This library was written specifically to be used in Home Assistant, as per project policy the code that interfaces with devices needs to live in a separate python package. So there is no real fame to be had from this particular package.

He surely sees this repackaging as a source of potential headaches. If the nix folks could convince him that the package would never contain modified code (no no untested/unsupportable modifications), and further that the home-assistant package in nix would always use exactly the version specified upstream (so no version mismatch concerns), he would likely be less opposed.

Unfortunately the latter is very much not true right now.

0 comments

apple4ever4y ago

> If the nix folks could convince him that the package would never contain modified code (no no untested/unsupportable modifications), and further that the home-assistant package in nix would always use exactly the version specified upstream (so no version mismatch concerns), he would likely be less opposed.

They did everything possible to try to convince him but he had his ears closed and refused to listen.

> Unfortunately the latter is very much not true right now.

Based on the above, it is very much true.

lsaferite4y ago

I mean, if it's written 100% for HA out of the gate as part of his employment by NC, why wouldn't it just live under a namespace for HA instead of a personal namespace. Using a personal namespace is about building a personal brand at that point.

j / k navigate · click thread line to collapse