View RSS Feed

Brandon W

Why use Frameworks?

Rate this Entry
by , 03-01-2009 at 03:14 AM (632 Views)
From me learning jQuery lately, it has been the first framework I have ever used on any language. I always saw programmers speaking of them and knew
what they did, but I never actually tried to use one.

There are many frameworks available for many programming languages, such as PHP, Javascript, ASP etc. There are not just one or two frameworks for each
but many. It's hard to choose which one that will fit your needs, but I think it would be best to get one and at least try it as it will save you
plenty of viable programming time.

The main objective of a framework is to shorten the amount of typing required to do something. The motto of the jQuery, a Javascript framework, is
"Write less, do more". This is very true as it can reduce this code from this;
Code:
getElementByID('name');
To this;
Code:
$($name)
So in saying this, a framework is basically a list of pre-written functions that will help you while you program. Not always functions, this can also
be a class. If it is a class, you will new to create a new instance of it and then using OOP techniques you can do what you want.

Most probably the most greatest thing I think about frameworks is, it is quicker to learn. Learning a framework is easier than ABC. You might alrady
know a programming language but you wish to use a framework, it might take you a while to get use to it but it will help you a lot in the process. If
you don't know a programming language that you wish to use a framework for, it might be harder to learn based on the framework. But it's always best
to have a fairly brief idea on the programming language.

What is your opinion on frameworks?

Submit "Why use Frameworks?" to Digg Submit "Why use Frameworks?" to del.icio.us Submit "Why use Frameworks?" to StumbleUpon Submit "Why use Frameworks?" to Google

Tags: None Add / Edit Tags
Categories
Uncategorized

Comments

  1. amrosama's Avatar
    nice blog!
    i like frameworks, but any JS framework will require a link to the framework itself on every page for example:
    Code:
    <script type="text/javascript" src="someframework.js" ></script>
    which is the sweet sour of frameworks, users will need to download the entire framework to run the framework functions. thats why (IMO) frameworks are best suited when you know you will use them alot..i mean alot
  2. WingedPanther's Avatar
    I think one of the other keys to frameworks is they make your code more robust. A framework has generally been robustly tested, resulting in a few "simple functions" that are easy to debug, rather than attempting to write code in raw JS that may be loaded with bugs.
  3. Jordan's Avatar
    I like frameworks and prefer them whenever possible because of Winged's comment but only use them when they are in agreement with Amr's comment.
  4. Brandon W's Avatar
    A JS framework is normally under 200kbs at MAX! The one problem with using a framework and trying to debug it is, it might not be the most popular so you will have trouble finding the problem. And now many tools out there support every framework, such as Firebug for Firefox.