- cross-posted to:
- privacy@lemmy.ml
- hackernews@derp.foo
- cross-posted to:
- privacy@lemmy.ml
- hackernews@derp.foo
cross-posted from: https://derp.foo/post/265688
There is a discussion on Hacker News, but feel free to comment here as well.
You must log in or register to comment.
Haha, I kinda agree with Rachel’s quote on hass Javascript plus a “curl | sudo sh” attitude to life indeed.
However, as the lesser of two weevils, I know which one I’ll eat.
Quick question, you do know the phrase is “lesser of two evils?”
It would just be hilarious if you thought the phrase was about weevils, which I could totally see.
Haha, yes, I do know the phrase. I just love using the line.
Home Assistant and its developers may not be perfect, but at least the imperfections are out in the open. We can’t comment on the quality of the commercial black boxes because we can’t see it.
I think that quote is a bit harsh, JavaScript is not inherently bad, or at least no worse than the people writing it. Install script piping is not an officially recommended installation method by HA. Both are also found in projects far more critical than HA.
Giving a kneejerk rejection to Home Assistant to instead adopt another proprietary hub a bit earlier in the enshittification pipeline doesn’t seem a great plan to me.
I agree. The standard nerdsnark can be a bit grating, when the person on the receiving end is, basically, doing the best they can to offer an open solution, while also balancing funding the project without everyone feeling they’re just milking.
HASS hits a really good balance, imho. They offer a paid service on top, but have no problem with people just running locally, or using a VPN to access.
Philips are providing another demonstration of the dangers of using proprietary smart home platforms. If you don’t control the platform, you don’t control your home. The only way to avoid this is to use an open platform such as Home Assistant, which just celebrated it’s 10th birthday and continues to go from strength to strength.