• 3 Posts
  • 36 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle








  • He tweeted “Her”, which explicitly tells us it’s a deliberate imitation of Scarlett’s voice in that movie. And he tried to negotiate licencing her famous voice, which she rejected.

    So it’s more than just a coincidence, it’s deliberate bad faith behaviour. Legally you can’t misrepresent a product as being from a famous person when it wasn’t, and he very much did that. I guess he was hoping she’d give in and accept the licensing agreement post-facto. But instead it looks he’s in legal deep water now.







  • zik@lemmy.worldtoProgramming@programming.dev*Permanently Deleted*
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    edit-2
    1 year ago

    It’s also a fallacy that rust code is memory safe. I audited a couple of large rust projects and found that they both had tens of unsafe constructs. I presume other projects are similar.

    You can’t use “unsafe” and then claim that your program’s memory safe. It may be “somewhat safe-ish” but claiming that your code is safe because you carefully reviewed your unsafe sections leaves you on the same shaky ground as c++, where they also claim that they carefully review their code.






  • The STM32WB55 in the flipper has a versatile wireless peripheral built in which can be used to implement various protocols including Bluetooth, zigbee, etc… Support for I2C, I2S and CAN is pretty standard stuff - the ESP32 is nothing special in these respects.

    Maybe they chose the STM32WB55 because its wireless support is more flexible than the ESP32 and allows them to implement a wider variety of protocols? Or possibly just better documented, giving them the chance to do things they can’t on the ESP32? I haven’t compared the inner workings of the two chips’ wireless support so I can’t say for sure.