There are many rumours about MVC and that things like cgi::application force a programmer to follow definite rules as he design his application, I have read about this way of making applications and didn't find any advantage in this way.

MVC that's what make me curious, is it really better than simply using single scripts for single tasks

Reading is never as convincing as understanding :) and the right kind of exercise can promote understanding

I remember reading about MVC before I did any OOP, and I didn't see any benefits either :)

Its like trying to understand the benefit of stick-frame-housing-in-earthquake-zones when you're living in a cave :) You mean to tell me I have to cut trees down, then nail them ... but the cave is right there :)

Based on this thread along with is this script secured enough from internet attacks, I believe you need to read/write more code, more programs, more big and OO programs, before you can appreciate the benefits of MVC or scaffolding like mojo/dancer/catalyst/cgi-app

Oh look, a single script for a single task, without MVC or OOP, admin.cgi

use MyShinyPoodle::Admin::CGI;
MyShinyPoodle::Admin::CGI->run;
[download]

Now you can test MyShinyPoodle::Admin , and it doesn't depend on any html templates or protocols like CGI

See also Object Oriented Orientation

Good luck