Poems in true chronological order by post date
-> file: fediverse/874 ═══════════════════════════════════════════──────────────────────────────────────── oh yeah well if SSH keys are so secure then why doesn't every website on Earth require them really though why doesn't every website on Earth require them ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧════════════════════════════════───────────────────────────┴───────────┘ -> file: fediverse/875 ═══════════════════════════════════════════──────────────────────────────────────── @user-192 block input/output TO the protocol? versus the other one which blocks the input/output protocol ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧════════════════════════════════───────────────────────────┴───────────┘ -> file: fediverse/876 ═══════════════════════════════════════════──────────────────────────────────────── @user-246 there is a reason to be annoyed, and that reason is that storing numbers as "dynamically typed" string values is both inefficient and frustrating due to the bugs it provokes. Not sure how common those bugs are in HTML, but dynamically typed languages like Python and Javascript have a whole class of potential errors that are significantly more difficult to debug than on C or Rust where the variables are statically typed ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧════════════════════════════════───────────────────────────┴───────────┘ -> file: fediverse/877 ═══════════════════════════════════════════──────────────────────────────────────── @user-617 never forget, never forgive. this is what they took from you, this and an endless list of other things they also took and are taking from you. ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧════════════════════════════════───────────────────────────┴───────────┘ -> file: fediverse/878 ═══════════════════════════════════════════──────────────────────────────────────── @user-192 omggg would it kill them to add a "synchronous" / "asynchronous" to the end of the name, sheesh ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧════════════════════════════════───────────────────────────┴───────────┘ -> file: fediverse/879 ═══════════════════════════════════════════──────────────────────────────────────── @user-501 also it's only undefined behavior because the order of the bits aren't defined, so if you do bitfield "pointer arithmetic" then you're screwed if you try and be portable with it. However if you're just using bitfields as compressed data storage then you can safely access integer.a integer.b integer.c etc safely and easily. The compiler doesn't care what order they're in if you don't write logic that requires them to be in a certain order ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧════════════════════════════════───────────────────────────┴───────────┘ -> file: fediverse/880 ═══════════════════════════════════════════──────────────────────────────────────── @user-246 the color of the sky 🤩 ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧════════════════════════════════───────────────────────────┴───────────┘ |