I believe we’re entering the Functional Reactive Programming paradigm shift. At least I hope we are.

Behaviors that update views on data only when that data changes.

Named resources ala URIs that expose those views, thereby exposing that data through APIs ala REST, ala CouchDB.

Views that can then be dynamically compiled into pages using transclusion (the embedding of externally identified, content) and functional reactive programming client behaviors ala Flapjax or more conventionally Redux. Views that can be programmed live using FRP techniques ala SuperGlue.

Flat tables ala CouchDB, Googles BigTable, Hadoop? and Vertica, storing large datasets viewed with client-driven(pay?) behavioral views that form customised APIs. Behaviour Orientated Architecture. BOA.

Forget about maintaining the APIs and worry about maintaining the data and the ability to view that data. ie. computational resources to generate and distribute those views, as well as uptime and security permissions for that data. HTTP Digest, view access permissions? [Insert Identity Layer Here] Better yet, automated content-centric networking, encrypted packet creation of those views as named data that can be pushed into the cloud.

Next we take it to the architecture level and synchronous reactive programming. Then we get functional reactive AI systems.

A friend sent me a link to an article on ultra wide-band wireless being the next big thing in wireless.

Bah. Another brute force attack at the problem. It’s just Moore’s Law. It’s the same shit just at higher frequences in order to gain throughput. Only; high frequencies don’t like walls.

What the network needs is intelligence.

The next big thing in networking, in my opinion, will be; medium agnostic and low-frequency wireless, mesh content-centric networks. Encrypting data and not the pipes makes firewalls redundant. This way any device can talk to any other device, over *any* medium (wifi, broadband, infrared, satellite) that supports the protocol, all because content-centric networking secures data instead of securing the pipes. In content-centric internet networking, IP packets are encrypted and shared with everyone because they’re encrypted, from peering eyes. The encryption level of that data can then depend on the data security requirements, with algorithms and bit length evolving as computing power increases.

Because every device can now access the encrypted packets - but not open them - every device within range of you can be a proxy server of that data. Even your phone or your neighbours toaster. This way you download the named data in swarms from p2p clients but can only open the data if you hold the key.

This system creates an enormous range of possibilities. Free for all internet access through credits for uploading, sharing of computing resources through ‘contracts’ and many other benefits. The key is that with this network, everyone has a key. An identity. An anonymous number if they choose to be. And because any data you send will include your key, the data integrity can be checked, approved or revoked. Because that data integrity can be checked, spammers and denial of service attacks, etc. can be pushed out of the system. It’s more secure because as things stand pipes, aren’t secure unless they’re quantum cryptography pipes. However, with content-centric networking, critical data can be obtained from multiple sources and checked for integrity that way. That’s the strength of quantum cryptography. Noise on the line at any point in time. This effect can and has been replicated in electrical copper pipes so why not wireless? With enough localised nodes this could be replicated so any man-in-the-middle attacks are prevented for data requiring that kind of security. For data that requires that kind of security. Not all data does. And in such a network; there are no edges.

Everyone is in the middle. Everyone is treated equally.

Anyone can get lost in the cloud.