He/Him Jack of all trades, master of none

  • 0 Posts
  • 85 Comments
Joined 3 years ago
cake
Cake day: August 10th, 2023

help-circle



  • Well nowadays there is “someone else” (for a given definition of “someone”) with a set of controls. Kids are being taught to drive in machines that literally drive themselves, and they need to learn that every decision that the self-driving computer makes ultimately falls on them as the driver. I think they were saying that this is a concept that needs to be taught, not a law that needs to be enacted.

    That’s not to say that a manufacturer is blameless when a FSD car careens into the side of a building at 80 mph. Just that immediate legal responsibility for the movement of a vehicle generally falls on a driver.





  • I didn’t know that symbolic links were a thing until like 2 years into using Linux daily. I didn’t know there was a difference between symlinks and shortcuts until I saw this comment!

    To save others a trip to Wikipedia, both a symlink and a shortcut store a path to another file or directory. The biggest difference is that symlinks are resolved by your file system, whereas shortcuts are resolved by whatever program accesses them. So if your software doesn’t know what a symlink is, that doesn’t matter. It tries to access the symlink, and your file system says “oh hey they want that jpeg” and serves them that jpeg. Whereas if your software doesn’t know what a shortcut is, it’ll try to access the shortcut and be like “wtf this is just a file path, I was expecting a jpeg”

    They can also store relative file paths, while shortcuts can only store absolute filepaths. So if your symlink references a file that’s in the same directory, you can move that directory and the symlink still works. Can’t do that with a shortcut.