• 0 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle









  • Reading the article, I learned that the author does not really have a clue what he is talking about.

    A mechanical clock is anything but analog. Look up what an escape wheel is for if you doubt it.

    For “analog is easier” keep in mind that it is very hard to get chip based circuits do precisely reproducable analog behavior. Indeed, this is one of the main reasons why we have digital computer chips: the output of the circuit is sufficiently unambiguous.

    And “can run things in parallel” - That’s what e.g. FPGAs are for. One if my designs runs audio compression on 32 channels with a meagre 12MHz clock, among many, many other tasks. All at the same time.











  • With such a codebase, once it is settled to a certain point, you stop adding things. You write new things, and carefully interface with the old stuff.

    Imagine a bank. Their software core is usually neolithic, i.e. written in COBOL or even worse, FORTRAN. You don’t add the “online banking” or “web client” interface in the original language. You add them in something more contemporary, which interfaces to the neolithic core via files, pipes, libraries, whatever, and translate it into a frontend as needed. As long as the core works, nobody needs to touch it.