DefederateLemmyMl

  • Gen𝕏
  • Engineer ⚙
  • Techie 💻
  • Linux user 🐧
  • Ukraine supporter 🇺🇦
  • Pro science 💉
  • Dutch speaker
  • 0 Posts
  • 189 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle

  • Don’t agree with the aircraft carrier bit. The point of aircraft carriers has always been that they can sit way the hell back, because the aircraft are projecting all the firepower. The F-35 and Super Hornet for example have a combat radius of well over 1000km.

    They have always been vulnerable in the sense that it doesn’t take much to destroy them, a few torpedoes or ASMs suffice. The hard part is getting those weapons on target. That means either getting close enough in a very hostile electronic warfare and anti-air environment, or acquiring a weapons grade lock on a moving target from hundreds of kilometers away.

    Both are very hard problems to solve, and $10k drones do nothing towards solving that. The threat to worry about here is not drones, but hard to intercept hypersonic missiles that are self guiding through passive electro-optical sensors that allow them to intelligently pick out an aircraft carrier to home in on.















  • A core memory of mine is getting flung off of one of these things because of the centrifugal force, falling on my back, and being unable to breathe for like 20-30 seconds … until I screamed at the top of my lungs, and things slowly returned to normal, while the teacher just went: oh you’re fine, don’t be a baby. I was 6.





  • I’ve seen ‘Active / Passive’ used, that seems alright

    That’s not always an accurate description though.

    Consider a redundant two node database system where the second node holds a mirrored copy of the first node. Typically, one node, let’s call it node1, will accept reads and writes from clients and the other node, let’s say node2, will only accept reads from clients but will also implement all writes it receives from node2. That’s how they stay in sync.

    In this scenario node2 is not “passive”. It does perform work: it serves reads to clients, and it performs writes, but only the writes received from node1. You could say that node2 slavishly follows what node1 dictates and that node1 is authorative. Master/slave more accurately describes this than active/passive.

    There’s plenty of alternative terms to use without borrowing terminology from sexual roleplay.

    Do I have news for you …