Some Thoughts on Designing a Linked Open Code Schema

As I start thinking about what should go into the core of a linked open code schema, I'm tempted to put a lot of high-level operations into the core so they run faster. History tells us that's the wrong way to go.


CPU instruction sets were dominated by two camps: CISC (complex instruction set computing), and RISC (reduced instruction set computing). CISC CPUs had complex instructions for manipulating strings, copying blocks of memory, and managing return and data stacks. CISC chips tended to have CPU registers dedicated to certain tasks
(e.g., a stack pointer).

RISC CPUs on the other hand had the simplest instruction set necessary to operate a computer (not by number of instructions but by amount of responsibility any instruction had), but often with a large number of registers resident in the CPU that could be used for any purpose, as stack pointers, accumulators

Continue reading "Some Thoughts on Designing a Linked Open Code Schema"

Linked Open Code

I've been working off and on over the last six months on a programming language that sits on top of linked open data. Think of it as linked open code.

von Neumann Architecture

Before von Neumann made his observations about code and data, computers typically had some memory dedicated to code, and other memory dedicated to data. The processing unit might have a bus for each, so code and data didn't have to compete for processor attention.

This was great if you were able to dedicate your machine to particular types of problems and knew how much data or code you would typically need.

Von Neumann questioned this assumption. Why should memory treat code and data as different things when they're all just sets of bits?

Today, our machines are built based on the "von Neumann architecture." Code and data share memory and the pipeline to the processor. If we

Continue reading "Linked Open Code"

Switching Things Up

I've decided to move to a different blogging platform: Ghost. All my old content is still around, but it's just a static copy of the former WordPress site.

"But WordPress has so many plugins and features," you say.

It does, but that's part of the problem. Blogs have grown into sites with feeds and toggles and social networking tie-ins. They've lost sight of their purpose: to connect people on their own terms.

I want this blog to be simple. It shouldn't have to give you a list of the top five things that strangers find useful, or encourage you to provide fodder to the commercial social networking world. That said, I am on Twitter as well as some other sites.

Blogs started as simple places where we published our thoughts. We could find other bloggers and read what they were thinking. If we wanted to follow them, we could add

Continue reading "Switching Things Up"