• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle



  • Not sure about the self-driving, but he had a video challenging the idea that electrons in wires that carry electricity. Basically arguing that it was the electric fields themselves that carried the power, which is largely outside of the actual wires.

    Not sure if that’s the same one where he asked what would happen if you used a light switch connected to a lamp by two wires. Apart from some truly egregious mistaken units (1s/c as unit of time), I vaguely recall thinking it was basically a huge clusterfuck of misunderstandings about what an electrical circuit diagram even is (stuff like real vs idealized components, parasitic capacitance / inductance etc.)

    They’re the kind of ‘Well actually’ half true factoids that you never hope to encounter in the wild if you actually understand the stuff. For someone claiming to be enthusiastic about science communication he did one heck of a job poisoning concepts with subtly wrong/misleading explanations that make it a lot harder to explain stuff to anyone with the misfortune to encounter his version first.




  • Fair. It’s not too hard, but most lemmy UIs make it a bit harder than it needs to be because they want to be a fancy JavaScript-ridden mess of html tags.

    On old.lemmy.world it is supremely easy, you just use the element picker tool of uBlock to select all posts, add the ‘magic’ command :contains(reddit) to filter out the word you don’t want (in this case reddit), and you’ve got your filter. This would result in old.lemmy.world##.post:contains(reddit).

    On lemmy.world it is trickier because it is the kind of HTML no sane person would write. Doing the above you end up with lemmy.world##div.mt-2.post-listing:contains(reddit) which is messy, and misses a line that is used to divide the posts. With some manual tuning you can first simplify the first part to ##.post-listing:contains(reddit) and then add :xpath(.|following::hr[1]) to get rid of the annoying line. This results in ##.post-listing:contains(reddit):xpath(.|following::hr[1]).






  • The images can get big, but they’re fairly clever about it so it is manageable. Performance wise they don’t take up more CPU and RAM than a regular application.

    There’s an (unofficial) image running nodemon on dockerhub about 250MB in size. The official NodeJS image is about 300MB (presumably they’ve preinstalled a bunch of stuff). You could start with the official image and install nodemon on it, that would probably be most future proof (no way of knowing if the unofficial image keeps getting updates, if any).


  • To understand it you’ll need to know roughly what an OS is. Very roughly speaking an OS provides a program with a way to access files, connect to the internet and launch other programs.

    What docker does is make something a bit like a ‘virtual’ OS with its own filesystem, network and task manager, and then start running programs in it (which then may launch other programs).

    Since you’re not making a VM which must simulate all of the hardware, this is a lot cheaper. However since a docker container gets its own filesystem, network etc. it can do whatever it wants without any other programs getting in the way.

    Among other things docker containers make installation a lot easier since a program will only ever see its own files (unless you explicitly add your own files to the docker container). To a large extent you also don’t need to worry about installing any prerequisites, since those can just be put into the container.

    Making a docker container is a bit (a lot) like installing a fresh OS, just putting the stuff you need in it and then copying the whole OS whenever you want to run the thing again. Except it’s been optimized such that it takes about as much effort as launching a program, as opposed to a VM which needs dedicated resources and are generally slower than the machine that hosts them.