Introducing FrameFrame

FrameFrame is the framework that we should have kept to ourselves; it adds nothing to the pre-existing toolsets, and empowers you to keep on making the same mistakes you already make in a new and slightly more uncomfortable way.

Bringing next-generation value from big-data and other empty phrases!

You probably think this sounds too good to be true — of course! We offer all the possibilities of the semantic web entirely hampered by shoehorning old-fashioned ideas about workflows into a vanity framework in an unfamiliar language, ideally ignoring pre-existing mainstream work.

Incremental steps towards the semantic web

FrameFrame makes it basically impossible to make any serious effort at creating real semantic content because the core model is fixed by the kind of thinking one typically finds in domains dominated by tabular thinking since the 1960s. It supports conceptual structures that claimed to be standardized and yet are mysteriously interpreted in many, many different ways even within this single application.

The steps we make here are so incremental, in fact, that they are hard to distinguish from inertia.

Serialization-acronym documents

We also present mistaken ideas about “what constitutes best practice” by confusing the bad ideas we had in the 1970s with modernity; a case in point being our insistence that a turd sandwich is not a turd sandwich because we put it in a wholegrain spelt baguette rather than sliced white, even though it is both a sandwich and contains turd. You might well ask why wholegrain spelt is better than sliced white — it doesn’t taste as good to everyone and costs three times as much, but we’ll respond in a way that makes it clear we haven’t thought our argument through.

We did for a moment look at what the semantic web actually is, but then realized we neither understood it or cared because we had better, fully formed documents to spew onto the web in a one-to-one mapping process.

The important news

What’s really important here is to realize that we’re not alone in doing this! Everyone is doing the same; everyone is producing their own FrameFrame in their own idiosyncratic way flavoured with dogmatic belligerence and arrogance.

What’s more, you can find FrameFrame from many, many different GitHub repositories, even though we know you’re more likely to code your own.


Dear Butthurt, this isn’t aimed at you. We’re all guilty of this. And if you can’t understand that, then you’re still in phase 1.

Posted in Uncategorized
2 comments on “Introducing FrameFrame
  1. bencomp says:

    I feel I should answer that your FrameFrame looks promising, but with a link to and a comment about WorkWork. The FrameFrame handles Task is probably a tiny bit better than WorkWork does, but did you know that Gigantic Software Company employs a developer who in his free time once glimpsed at WorkWork? That means WorkWork’s developers can now use Gigantic Software Company’s name on the website as if GSC endorses WorkWork.
    Obviously that is the best reason to stop trying to improve FrameFrame.

  2. […] the schema larger. Larger schema, more bandwidth; covers more edge cases. Great. I wrote about FrameFrame a while […]

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s