• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: August 4th, 2023

help-circle



  • Phrodo_00@lemmy.worldtoLinux@lemmy.mlHow terminal works
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    6 months ago

    Yeah, they’re mostly bits of hardware that turn ttl/serial into a USB device. Then you can use minicom or dterm to connect to the host. Mostly used for embedded development, but also useful for debugging servers that are not connecting to the network without having to lug a keyboard and screen.

    After they’re connected, if they speak vt110, your terminal emulator can display everything properly


  • when you format a 256GB drive and find out that you don’t actually have 256GB

    Most of the time you have at least 256GB. It’s just you 256GB=238.4GiB, and windows reports GiB but calls them GB. You wouldn’t have that problem in Mac OS that counts GB properly, or gnome that counts GiB and calls them GiB.

    (This is ignoring the few MB that takes to format a drive, but that’s also space on the disk and you’re the one choosing to partition and format the drive. If you dumped a file straight into the drive you’d get that back, but it would be kind of inconvenient)
















  • all interpreters have a compilation step that produces machine code

    Very much not a thing. JIT interpreters are actually not that common. Most interpreters parse code to an AST in memory and then run execute said AST, without any compilation to machine code.

    the output of the standard javac compiler is not machine code that a processor understands. This is what makes Java not a compiled language.

    Listen to yourself the output of the compiler makes it not a compiled language. Java is a compiled language, and jvm bytecode can be compiled (see graalvm), or interpreted (and when interpreted it can be JITd)