Free Shopping Cart
Introduction
PHP Shopping Cart
Layout Guide
ASP or PHP Cart
Your Choice
Retail Shopping Cart
Benefits - FYI
Transfer To Our Free
Shopping Cart
Shopping Cart Real
Issues-Answers
Shopping Cart FAQ
Store Set Up
Store/Shopping Cart
Pre-Installed
Shopping Cart
Merchant Account
Privacy and
No Cookies
Email Us
|
Supercharged Shopping Cart
Used by over 9,986 Live Stores
Free shopping cart Supercharged
Here is what we mean by Supercharged
|
I will attempt to clear up any confusion about free but supercharged and the concept of bloated software versus the necessities as needed by an individual merchant. This is how the free software was likely derived.
Conceptual Integrity:
In order to make a user-friendly system, the system must have conceptual integrity, which can only be achieved by separating architecture from implementation. A single chief architect (or a small number of architects), acting on the user's behalf, decides what goes in the system and what stays out. A "super cool" idea by someone, may not be included if it does not fit with the overall system design seamlessly. In fact, to ensure a user-friendly system, a system may deliberately provide fewer features than it is capable of. The point is that if a system is too complicated to use, then many of its features will go unused because no one has the time to learn how to use them. That is why this shopping cart/storefront contains the usual components and more versatility can be added if needed.
Code Freeze and System Versioning:
Software is invisible. Have you ever considered that premise? Therefore, many things only become apparent once a certain amount of work has been done on a new system, allowing a user to experience it. This experience will yield insights, which will change a user's needs or the perception of the user's needs. The system will therefore need to be changed in order to fulfill the changed requirements of the user. This can only occur up to a certain point, otherwise the system may never be completed. At a certain date, no more changes would be allowed to the system and the code would be frozen. All requests for changes, will be delayed until the next version of the system or the intervention of a programmer.
Creeping featurism:
Creeping featurism, or creeping featuritis, is a phrase used to describe software which over-emphasizes new features to the detriment of other design goals, such as simplicity , compactness or bug reduction.
A related term, feature creep, describes the tendency for a software project's completion to be delayed by the temptation to keep adding new features, without a specific goal. One such code addition came about after numerous merchant complaints that shoppers sometimes did not click the "Update Button" after changing quantities, resulting in orders being recorded incorrectly. Here was a need for an automatic update feature. But I found that the update button could not be dispensed with because most shoppers used it properly and were dismayed if it was removed. I ended up instituting the auto update feature but left the update button in place.
This phrase is sometimes rendered as the spoonerism "feeping creaturism", which brings up the image of each new feature being a small creature which runs around going "feep, feep".
Many people criticize Emacs as being a prime example of creeping featurism. Emacs proponents, however, tout Emacs' all-in-one nature as one of its primary benefits. Multi-paradigm languages such as C++ have also faced such criticism. I once wrote an email to Microsoft, complaining about new version releases. Saying that I didn't have the old version sufficiently utilized and understood and here comes the new version. Looks to me like they are more interested in churning out versions for profit than usefulness.
Software bloat:
Software bloat is a derogatory term used to describe the tendency of newer computer programs to use larger amounts of disk space, more CPU power and/or more RAM than older programs. Software exhibiting this tendency is referred to as bloatware or, less commonly, fatware.
Why bloatware? :
Software developers involved in the industry during the 1970s had severe limitations on disk space and memory. Every byte and clock cycle counted, and much ingenuity went into avoiding waste. The extra time spent by programmers to avoid this waste translated directly into smaller, more efficient software products, and hence was seen to translate directly into sales revenue.
However, technological advances have multiplied processing capacity and storage density by orders of magnitude and reduced the cost per MIPS and cost per bit by similar orders of magnitude (see Moore's Law ).
Additionally, the spread of computers through all levels of business and home life has produced a software industry many times larger than it was in the 1970s.
As a result, the emphasis in software design is argued to have shifted away from tightness of design, cleverness of algorithm and thriftiness of resource usage. Instead, time-to-market has been seen to become the key.
I have toyed with the idea of taking my shopping cart code and re-writing it using Visual C++. Fortunately, experience taught me that compiled code, while extremely fast and lending itself to feature creation, would be impossible to use on a daily basis because it would require re-compilation for every change required by individual merchants. Believe me, each merchant has his own idea of selling.
Some hold that the result of modern rapid application development practices, forgoing the optimization practices of the past, is that modern software running on faster computers does not present a user impression that is significantly faster—this user impression, due to the consumption of underlying technical advances by layers of software abstraction in pursuit of time-to-market, is the essence of bloatware. Unfortunately the abolition of this software abstraction can hamper the underlying development of the program. Software structures that are well crafted in place to allow for easy extensibility and maintenance will assist software developers in that upgrading existing code will be simpler and faster.
However, the optimization at the machine-code level need not be done by hand. Modern compilers often take optimization of code into consideration, and this forgoes the need for hand-manipulation of assembly code. Naturally, this software optimization is never one-hundred percent perfect, but then the resulting effect from a programmer making the optimized code fully optimized is negligible.
Products commonly considered bloated are Windows XP , Microsoft Office , Windows Media Player , RealPlayer , emacs , the Netscape suite, Adobe Reader , and a couple of instant messengers like ICQ (before ICQ lite) and MSN Messenger
As a Do-It-Yourself enthusiast you should be prepared for frustration when trying to add or alter the basic PHP code. As an experienced programmer with 25+ years I saw lots of overkill features being implemented but I had no desire to jump in and eliminate them. I try to let alone things that are working. (Murphy's Law, you get the idea).
So after all is said and done I add or modify only the code that my client asks for. And that is what supercharging is all about.
|
|
- Get It Now
Just call (386) 738 3080 to get this free shopping cart. You will be very happy.
Over fifty million orders processed since 1995.
Is your business unusual in some respect? Tell us about it.
We answer all Email within 2 hours.
Call Tech Support for more details - Six Days.
Orlando/Daytona Beach, Florida
Hours 9 to 9 EST
Tech Support and Questions - (386) 738 3080
We Operate
Shopping Cart Servers in 26 Cities Nationwide
Atlanta, Bethesda, Boston, Casper, Chicago, El Paso, Dallas, Dayton, Daytona Beach, Denver, Detroit
Fargo, Houston, Las Vegas, Los Angeles, Macon, Malibu, Miami, Nashville, New York, Orlando, Richmond
San Jose, Seattle, Tacoma, Toronto, Washington DC
|
See This Free Shopping Cart In Action!
Click here!
© Copyright 1994 to 2006 Florida Cart
|
