Skip Navigation

Posts
8
Comments
324
Joined
2 yr. ago

  • "I wasn't notified in triplicate, sent in, sent back, queried, lost, found, subjected to public inquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters".

  • Some sort of extensible message protocol?

  • Yup. If they'd just made the bowl out of something OTHER than ABS, they would have been good. Delrin, PTFE, even a thin layer of brass or broze, and those controllers wouldn't have had anywhere near the amount of issues they're known for having.

    There are third-party manufacturers who sell replacement bowls and sticks, made from everything from POM to steel.

  • They don't get sensor drift, but if the mechanical centering of the stick is sub par, you can get mechanical drift. The N64 is a good example. Flawless sensors, shitty mechanical construction

  • N64's issues came from the bushings wearing out, the sensors were still very good

  • Joycon drift, and all other thumbstick drift, is already a solved problem.

    1. Use bushings that actually have some abrasive resistance and aren't softer than a fingernail.
    2. Use a non-contact based sensor to determine the XY position of the stick. Hall effect, optical, strain gauge, whatever, we've had the tech for 50 years.

    The reason why they haven't done this is one very simple reason: $$$

  • Check out Elixir's Ecto. You basically do write SQL for querying, it's just lightly wrapped in a functional approach.

  • Either way it's a no effort account and you can basically ignore them, as their contributions will most likely be garbage either way

  • How can I use a sonoff to control my fireplace guys?

  • RSS is quasi-archival, so it can give you a listing of new content sorted chronologically with no other input. Even reddit's /new feed cannot guarantee this.

  • Not if they have a way to strip watermarks too, as has happened with every other system like this

  • Python belongs in docker for exactly thus reason

  • In theory yes, but it becomes a problem of ergonomics. The transpiled library feels like a transpiled library, it doesn't match the conventions of Nim/Zig. The best ports/wrappers/whatever typically use the C lib for all the heavy lifting and unique things, and build their own interface, that matches conventions of the calling language

  • Or just a line stamped into the metal reservoir tub

  • Just use the RSS feed

  • Its a neat language, very simple. Has a somewhat simple approach to codegen at compile time, which is both a boon and a curse; you can do a lot with it, and not get too deep into footgun territory, but once you hit the limits of what you can do, you're pretty much stuck there.

    The syntax and other features are very nice, and it makes rather small binaries. I'd say its comparable to Nim in this area.

    Sadly, it also suffers the same problems Nim suffers: dearth of libraries.

  • In some places they are.

    In Utah, for example, there's a system called Utopia. They ran fiber all over the place, to the home in most locations. The fiber itself is an Ethernet network owned by Utopia. ISPs then just provide service over said Ethernet network. You can have multiple ISPs at the same time, and they don't actually own the last-mile, or much else

  • If you can't list em, you shouldn't be able to charge for em

  • After switching to Pulumi, I don't ever want to use terraform again