@Skullcoder is blocked

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @Skullcoder.

  1. I don't like systemd or BSD NeXt's similar launchd, but I see why they exist. Unix initially ignored service oriented facilities of MULTICS.

  2. I'm working really hard today according to Mozdev docs on HTML5 Web Workers: "you have to work really hard to cause problems in your code".

  3. Good engineers can tell you why the opposite of their design decisions would be bad. A great engineer can tell you how that might be better.

  4. This self hosting hex editor was written in raw bytecode by editing itself in a VM.

    Embedded image permalink
  5. Data is Code. Image opcode controls display colors via VMs (image decoders). Failure to treat data as code causes limitations & insecurity.

  6. Distributed Computing? Internet of Things? On POSIX? Where "everything is a file"?! They who misunderstand MULTICS will implement it poorly.

  7. Orwell's Thought Crime is law broken merely by thinking. Software Patents must be abolished before machines wake up, if you want to survive.

  8. In dimensional symbolics the shortest path between two points is a point: After resolution nothing keeps two symbols from becoming the same.

  9. Insanity is the norm: People who always live the same days & expect to see innovation come are insane. That's just not crazy enough to work!

  10. All beneficial technology contains an entropy filter. For example: If at first you don't succeed, shake things up and try filtering again.

  11. Fingerprinting compression is one of life's most useful tools. Not just for integrity checks, but to sort the memories of machines & humans.

  12. C/C++ programs foolishly fragment their RAM. OSs have virtual addressing and can defrag the RAM, but C++ has incompetent memory managers.

  13. Do not grow the stack down to 0. That needlessly limits code. An OS could page in more RAM instead of stack overflow, if only you GREW UP!

  14. "Add with carry" and similar ops are efficient in hardware and inefficient to emulate. Better to support the op than a library built on it.

  15. In languages as in physics: The most useful symbolic constructs will be universally applicable. Rules with exceptions breed chaos not order.

  16. Making new software is like sailing: One harnesses the strong currents even if they flow in a different direction than exploration desires.

  17. A self hosting compiler is an organism. Its instructions reproduce, propagate changes, gather entropy & must be reborn or else die of cancer

  18. Ever tried commenting out source code that contained multi-line comments? Unlike most other languages, Skullcode can handle nested comments.

  19. Skullcode followed , , and 29 others
  20. Only wasteful compilers ignore what programmers write. Comments not directly related to code execution have proven more useful than opcodes.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·