Jim Atkins, thedosmann, is a website programmer who started programming in the early 90's. He has worked professionally as a Manager of Technical Services, Website developer, hosting provider, and consultant since 1995.
In programming code it is possible to theorize about several aspects of code flow and dependency through coding models. One such model is the Actor Model.
By making programming languages less difficult to work with you increase the number of people writing programs and successively increase the number and variety of programs available.
In a previous article I described how, in order to have a true Semantic Web, we would need to have a user action to direct the program. I would like to examine some of the motivations for this point of view.
Online banking continues to be an increasing method of choice for conducting business and paying bills. According to a recent Pew report, fifty-one percent of U.S. adults, or 61% of internet users, bank online.
The original concept was for the system to display a number of images on a tabbed-page HTML layout. Each tab/page of images needed to be centered and allow a user to touch a thumbnail to bring up larger rendering of that image.
Most search engines do an adequate job at sorting out some of these FLUFF sites but they still somehow show up in search results. Maybe what we need in the search engine tools arsenal is a FLUFF filter.
Within the next few years, we will see an exponential growth in micro touch screen devices that can be unfolded from 3x6 to 12x6 (and other sizes) to form a touch screen. These devices will have no hard drive, no CD/DVD, no memory other than an ultra-thin EPROM, and no external ports.
When talking about the Semantic Web there are a few premises one must acknowledge. One premise is that any data exchange on the internet is originally initiated by a human. There is no information retrieval without a request for that information and that request can be directly tied to a human request for the information.