Tools and Techniques

Frame(s)work was born out of the vacuum of common sense web programming solutions. Browser based programming is the most powerful and lightweight user interface environments. Solutions like React and Angular began as streamlined solutions for aggregating the many available features available to the web programmer.  BUT as is the case with many attempts to be to create rules and structure, the frameworks become bloated and complicated. In addition, every new attempt to leverage basic features of browser programming, compound the complication. It is not sustainable. 

As any competent software designer will tell you, "Complication is the excess over complexity". Software must always be extended, refactored and reduced. The world is always changing and this forces a change in the definitions of what is Optimal. Much of the recent developments in the web development are based on the changes offered by HTML5 adoption. For those old enough to remember, prior to HTML5 the most prominently available virtual machine was flash. Created by Macromedia and later sold to Adobe, the plash player was installed on 90+% of all pc's. And for those older enough to remember the 1990's, may remember what a java Applets being the chosen technology for creating rich internet experiences.  

The reason for the history lesson is to remind us all that technologies are temporary but the need for software is perpetual. This understanding is the primary driving force for constantly iterating to newer and newer technology stacks.  This isn't to say that newer is always better but, carefully selected, they can be better equipted to leverage new hardware and software.  We must always be ready for change!

At present, the typical application has a 'Front-End' and a 'Back-End'.  Let's explore a little about the history of this architecture. Since the advent of the internet there has been a desired to make the experience greater than its design. It has been said "the internet's greatest challenge was its own success". The 'webpage' was born with 3 primary characteristics: HTML, Javascript, CSS. Although the 'birth' wasn't in the conventional sense, it was a little like an external gestation. The true birth was the wide-spread adoption, like a picture being taken.

The first webpages were static but quickly the incorporation of dynamic content become the goal. Technologies like Java Server Pages and Active Server Pages were born out of the need for dynamic content driven by database data. Web pages were created by calling web servers that processed programming and generated the HTML, Javascript and CSS for browser rendering. Although this step in the evolution of interfacing with the web, was a significant advancement it would make way to other forms.

The point I am making is that the solution was temporary but the requirements became even greater. This brings us to the demand for technology. As tiring of monotony and disire to solve problems, are parts of the human condition, the need for better software will always be present. Since this is the reality, to only accept change is not enough, we must pursue software development paradigms that are plug and play for new technologies.

A framework should provide the scaffolding for hosting software solutions. A framework should not be the totality of availability. For example Angular, React, and Vue each have their own technology and development foundations. They are not compatible nor are they easily integrated with each other.  In short, they are 'CLOSED'. 

HOW IS FRAME(S)WORK DIFFERENT?

1. NOT COMPILED... Javascript frameworks are 'compiled' as they are converted from the framework structure and syntax to HTML, JS and CSS. Frames(s)work is HTML, JS and CSS.

2. BASED ON W3C... Javascript frameworks are managed by themselves and guided by the priorities and tenants of their roadmap. Frame(s)work adheres to the guidance of W3C much like the javascript frameswork, but Frame(s)work developers implement changes on their timeline and not the javascript frames.

3. OPEN... Frame(s)work is designed to provide easy integrations with other frameworks through the major interfaces availble (Session Storage, Local Storage, IndexedDB, WebSQL, MainPage Cache, MainPage Functions, Query String Variables).

4. BUILT FOR CHANGE...The heart of the Frame(s)work is interchangeability.