Skip to content

The weaponization of Waymo

Technology
26 19 23
  • 33 Stimmen
    8 Beiträge
    0 Aufrufe
    gandalf_der_12te@discuss.tchncs.deG
    The article is well-written. I wonder how many employees will still be needed in 10+ years from now. In case you haven't heard about it, the labor market is regulated by supply and demand. That means, if there's less demand, but supply stays equal, wages decline. That's what people experience for the last decades. If this trend continues, demand for human labor might become very weak. That's why people for one can no longer rely only on the incomes through the labor (wages), but need good safety nets (Universal Basic Income, UBI). And also, demand for labor is another way of saying "how much are humans needed to perform tasks". What if humans aren't needed? Will people be ok with that?
  • 6 Stimmen
    3 Beiträge
    0 Aufrufe
    V
    I'm so ready to stop even talking about it.
  • Large Language Model Performance Doubles Every 7 Months

    Technology technology
    53
    1
    97 Stimmen
    53 Beiträge
    13 Aufrufe
    V
    in yes/no type questions, 50% success rate is the absolute worst one can do. Any worse and you're just giving an inverted correct answer more than half the time
  • 12 Stimmen
    1 Beiträge
    10 Aufrufe
    Niemand hat geantwortet
  • 386 Stimmen
    9 Beiträge
    9 Aufrufe
    C
    Melon Usk doomed their FSD efforts from the start with his dunning-kruger-brain take of "humans drive just using their eyes, so cars shouldn't need any sensors besides cameras." Considering how many excellent engineers there are (or were, at least) at his companies, it's kind of fascinating how "stupid at the top" is just as bad, if not worse, than "stupid all the way down."
  • 131 Stimmen
    67 Beiträge
    166 Aufrufe
    I
    Arcing causes more fires, because over current caused all the fires until we tightened standards and dual-mode circuit breakers. Now fires are caused by loose connections arcing, and damaged wires arcing to flammable material. Breakers are specifically designed for a sustained current, but arcing is dangerous because it tends to cascade, light arcing damages contacts, leading to more arcing in a cycle. The real danger of arcing is that it can happen outside of view, and start fires that aren't caught till everything burns down.
  • 2 Stimmen
    2 Beiträge
    16 Aufrufe
    quarterswede@lemmy.worldQ
    I give it 5 years before this is on our phones.
  • Microsoft's AI Secretly Copying All Your Private Messages

    Technology technology
    4
    1
    0 Stimmen
    4 Beiträge
    24 Aufrufe
    S
    Forgive me for not explaining better. Here are the terms potentially needing explanation. Provisioning in this case is initial system setup, the kind of stuff you would do manually after a fresh install, but usually implies a regimented and repeatable process. Virtual Machine (VM) snapshots are like a save state in a game, and are often used to reset a virtual machine to a particular known-working condition. Preboot Execution Environment (PXE, aka ‘network boot’) is a network adapter feature that lets you boot a physical machine from a hosted network image rather than the usual installation on locally attached storage. It’s probably tucked away in your BIOS settings, but many computers have the feature since it’s a common requirement in commercial deployments. As with the VM snapshot described above, a PXE image is typically a known-working state that resets on each boot. Non-virtualized means not using hardware virtualization, and I meant specifically not running inside a virtual machine. Local-only means without a network or just not booting from a network-hosted image. Telemetry refers to data collecting functionality. Most software has it. Windows has a lot. Telemetry isn’t necessarily bad since it can, for example, help reveal and resolve bugs and usability problems, but it is easily (and has often been) abused by data-hungry corporations like MS, so disabling it is an advisable precaution. MS = Microsoft OSS = Open Source Software Group policies are administrative settings in Windows that control standards (for stuff like security, power management, licensing, file system and settings access, etc.) for user groups on a machine or network. Most users stick with the defaults but you can edit these yourself for a greater degree of control. Docker lets you run software inside “containers” to isolate them from the rest of the environment, exposing and/or virtualizing just the resources they need to run, and Compose is a related tool for defining one or more of these containers, how they interact, etc. To my knowledge there is no one-to-one equivalent for Windows. Obviously, many of these concepts relate to IT work, as are the use-cases I had in mind, but the software is simple enough for the average user if you just pick one of the premade playbooks. (The Atlas playbook is popular among gamers, for example.) Edit: added explanations for docker and telemetry