• 0 Posts
  • 54 Comments
Joined 2 years ago
cake
Cake day: July 31st, 2023

help-circle
  • Might be. It is definitely a thing, though.

    When I used to work for a large American corporation that sold products to consumers, they took it extremely seriously and breaking it would result in disciplinary action. It probably had something to do with advertisement laws, but it also easily could have just been because it makes the company look very bad.

    one place even asked people to write fake reviews on Trustpilot/job sites

    That sounds unethical, to say the least. Did they verify if you actually did it, or just “suggest” you do?







  • pivot_root@lemmy.worldtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    41
    arrow-down
    1
    ·
    28 days ago

    In a Musk-approved world:

    • You’re hit by a Tesla in FSD mode, the driver gets sued for not driving.
    • You’re hit by a fully autonomous Tesla taxi, you get sued for vandalism.
    • You’re the driver and FSD hit someone, you get sued.
    • You’re the owner and the car hits someone while you’re not in it, you get sued for owning it.
    • You’re the owner and it catches fire with you inside, you(r estate) gets sued for “not maintaining it”.



  • JavaScript was a mistake, but this is one of the few things they did correctly. Implicitly importing everything from a package into the current scope makes it difficult to follow where variables or functions come from, and it’s prone to cause problems when two packages export the same identifier.

    If you’re an absolute masochist, there’s always a workaround. Against all best practices, you can use the deprecated with statement. Or, you can Object.assign() the packages into the global object like a monster. Or if you’re using node, you can use the node:vm module to create a new V8 context with its own global object of your choosing.