Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What is mean by a lightweight framework? [closed]

Tags:

codeigniter

What is a lightweight framework? Why it is saying that codeigniter is lightweight?

like image 600
Sreehari Avatar asked Oct 08 '13 10:10

Sreehari


People also ask

What is meant by lightweight application?

In computing, lightweight software also called lightweight program and lightweight application, is a computer program that is designed to have a small memory footprint (RAM usage) and low CPU usage, overall a low usage of system resources.

What does lightweight mean in Java?

Lightweight Java (LJ) is a fully formalized and extensible minimal imperative fragment of Java. The language was designed for academic purposes within the Computer Laboratory, University of Cambridge.

Why is Spring Framework lightweight?

Spring is called lightweight because it doesn't reinvent the wheel and builds on top of existing technologies and standards. Java Spring framework is not a framework to develop a web application but rather a complete programming and configuration model for a Java-based enterprise application.

What is a lightweight Web application?

Definition. The light-weight, Web-based applications (“webapps”) of this essay are small, platform-independent programs that are downloaded on demand and execute inside a client program, such as a browser.


1 Answers

Here is a post i found on coderanch.com :

The term "lightweight" refers to the conceptual weight of a framework. Lightweight frameworks like Spring have minimal impact to an application. That is, it does not require as many code changes to incorporate them into your application as does the more heavyweight frameworks like EJB. When you create an EJB, you have to deal with several interfaces and it is pretty clear by looking at the code that an EJB is tightly coupled to the J2EE framework. On the other hand, a POJO is usually blissfully unaware that it is being used in the Spring Framework. Spring is minimally-invasive. There are also claims that it should not be a very difficult task to take Spring out and replace it with another similar framework.

With lightweight frameworks, you do not have to think too much about the underlying framework because there really isn't much code to write that explicitly ties you in with the "plumbing". On the other hand, traditional J2EE development with EJB entails writing a lot of "plumbing" code which weighs you down conceptually.

Hope it helps.

like image 93
HappyDump Avatar answered Sep 23 '22 19:09

HappyDump