The ever-ongoing debate about what is the best programming language to use split off a few years ago into the ‘web programming’ languages and the ‘application programming’ languages. People used languages such as asp and perl for doing things on the web, and C++ and java for things that would be installed desktop applications. A few years ago, with the increased demand for portability in applications, everything started moving toward the web, with applications on demand, aptly named Software as a Service (SaS). This let you do your job pretty much anywhere you had an Internet connection, even better if you have one of those nifty mobile connects for your laptop or phone. Now you can pretty much pick up a language and be able to use it somewhere on the web (depending on the server and installation package of course).
So what differentiates one approach to programming on the web from another? It’s usually a matter of preference and almost always a matter of application. Here at DDA, we have been a Coldfusion shop since the beginning, mixing it up with PHP and ASP when we take over a client’s previously written projects. That basically means that when we start a project from scratch, we will probably be writing the code in Coldfusion, but we are quite capable as a business to take on existing projects written in other programming languages. We choose Coldfusion not only because it’s familiar, but because it is robust enough to do just about everything we’ve tried to do, and because it’s a JAVA-based system, we are able to access JAVA as needed. Usually the JAVA pieces tend to be more traditional application sorts of things, like image processing or file processing, which would be normally unlikely for any website to use due to restrictions on what web languages are allowed to access. These are the nuts and bolts of the ddaApps.
We put it all together at DDA, along with great designs, to bring applications to you, wherever you need to go.