• 0 Posts
  • 21 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle

  • To my surprise, Nanoleaf tech support responded to me within 4 hours, with a full description of the protocol that’s used both by the Desk Dock as well as their RGB strips. The docs mostly confirmed what I had already discovered independently, but there were a couple of other minor features as well (like power and brightness management) that I did not know about, which was helpful.

    Combo of investigating and a foot up from the manufacturer.

    When I’ve done this in the past for game controllers I’ve not received such an emphatic response (other than when I was working for the vendor).

    Did get some via FOI for a few other products though.








  • Why is it when I miss a day of Daily Show it’s eviscerated from my feed entirely, but no matter how many Jordan Peterson thumbnails I hastily pass over, they still appear week in week out?

    To date I’ve watched one JP video: Matt Dillahunty verbally tearing him a new asshole.

    The right wing rabbit hole is real and, even if you’re explicitly against it, YouTube is like “if I can get him to watch just one …”, because they know they’ll have you watching videos like the guy from Clockwork Orange in no time. It’s disgusting.

    Pro tip: never press “do not show me this” on right wing videos, just skip over them. That engagement causes the algorithm to mark you as emotionally triggered by politics and they’ll just shovel more of the same in your face. For them it’s just a roll of the dice, and the value of them flipping you is too high to avoid.










  • I’ve found this to hold true in almost every hobby I have but particularly in technology, engineering and music playing/making: avoid hitching your wagon to one approach. It’s easy to get trapped under a pile of ‘musts’ when trying to do anything that you are skilled in, but that’s also the worst environment for innovation; and almost every innovation in your hobby of choice was borne from people pushing boundaries, not forcing themselves to fit within them.


  • The lack of ABI stability in Rust means they don’t have to commit to language changes that may prove to be unpopular or poorly designed later.

    Swift went through the same growing pains and, IMO, has suffered for it a bit with even quite basic code often needing lots of availability checks. This may seem counter intuitive but Swift is in the unique(-ish) position of having to serve both a huge corporation demanding significant evolution on a regular basis and a cross platform community that don’t want to write an encyclopedia every time a major version of the language is rolled out.

    Rust doesn’t have this issue and I think it’s right for them to allow themselves the freedom to correct language design errors until it gains more traction as a systems language - and it’s quite exciting that we’re seeing that traction happen now in realtime!