Purchasing a function – intentional programming

One of the really cool traits with Hyperlambda and Phosphorus Five, is that it allows for non-developers to at least to some extent create rich and interactive web apps. With P5, there is no need to understand JavaScript, CSS or C# – Still, you can at least to some extent, create fairly rich web apps, simply by declaratively consuming what other developers have created for you. This process is almost similar to the process of assembling LEGO bricks. One example of this, was shown in my previous blog.

You could very well create most rich web forms, gathering data from your users, by using the [micro.widgets.wizard-form] extension widget, and the [micro.form.serialize] Active Event. This creates an interesting opportunity for non-developers to actually create their own web applications. Something which I kind of indirectly touched upon here. This opens up a whole new range of opportunities, for really cool constructs, which at least I have never seen before. One example is assumed in the header of this blog; The ability to purchase or sell a “function”.

Imagine having an app-store for function objects, or Active Events to be more specific. Hard core software developers could be creating these functions, and allow non-developers to purchase these, and use them almost like LEGO bricks when they create their web apps. This could open up for an app-store where normal people could purchase extension widgets, and/or Active Events, which they could consume in their apps, to create whatever they feel for creating themselves.

Then as a purchase of such a function object is placed, the system could automatically download the function object, and/or extension widget, and install it into the server of the end consumer – Which then of course could use it to assemble his own apps as if his function objects where simply xerox-copied LEGO bricks.

A function object like the above, could of course be sold dirt cheap once P5 has massive adoption. Simply because first of all, the creation of such function objects, would be significantly cheaper in regards to resources, than to create an entire app to sell through an app-store. Hence, one “vendor” of such named function objects, could easily within a month or two, create dozens of these functions, selling them for pennies. In addition, once P5 reaches tipping-point, inevitably selling such function objects, to thousands of non-developers, would be a no-brainer. That way, the non-developer could create complex and rich apps, using the ideas of intentional programming, declaring his apps, by combining extension widgets and function objects, he or she purchases at some “function app-store”.

This would fix the problem of the “long tail software development”, where a domain problem is too small, for any commercial vendor to be interested in participating in solving it. For instance, ask yourselves the following question …

How many ornithology software programs does there exist out there?

The reason why the ornithologists of the world has been underserved by the software industry of course, is because there are simply too few of them. Still they would obviously benefit from having access to all sorts of data gathering apps, making their jobs easier.

With the above suggestion, the ornithologist himself, could easily create his own software, by consuming pre-built building blocks, purchased through a “function object app-store”, where the developer of the function object, have created a generic solution, which could be used for everything from creating ornithology software, to ERP software.

The above idea is why I often refer to Hyperlambda as a “fifth generation programming language”.

Could you spare me a function bro?