Re: Is too much abstraction a bad thing?

Have you seen CGI::Application yet? [update: yes, yes you have]

use WebApp;
my $webapp = WebApp->new();
$webapp->run();
[download]

But ... there really is more to it than just that. You actually have to implement the WebApp class.

I'm not going to write an essay on this, but do consider what you are doing 9 times out of 10 when you write a piece of software -- you are writing it for a client. And that client will ensure that no matter how much abstraction your tool provides, you will need to open the hood and change things around to fullfill the client's ever shifting requirements.

"What will the future of Perl be once we have a framework written for most common applications?"
A starting point. The client will always want something different, something more flexible, something that was not originally specified.

Everything in moderation -- too much of anything surely is not a Good Thing ™.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Comment on Re: Is too much abstraction a bad thing? Download Code

Replies are listed 'Best First'.
Re^2: Is too much abstraction a bad thing? by Anonymous Monk on Jul 26, 2005 at 19:00 UTC
Is too much abstraction a bad thing? Yes. Abstraction, by definition, limits the amount of data that is available about a given topic at one time. It's bad to be flooded with too much data, so abstraction is clearly "good". Specification, by definition, gives specific details about a specific scenario. It's often important to get all specifics down to know what's going on, so specification is clearly "good". The two terms are opposites. Deciding how much information you want to specify, and how much should be left abstracted is a central problem for communications. Computer programming is all about communications: both a computer (via a programming language), and to fellow programmers ( via your choice of individual programming elements and constructs, as well as explict comments and documentation). If you have to ask: "Can there be too much of <X>", the answer is usually "yes".	[reply]
Re^2: Is too much abstraction a bad thing? by radiantmatrix (Parson) on Jul 27, 2005 at 18:54 UTC
Everything in moderation -- too much of anything surely is not a Good Thing™. Too much abstraction is called Java™. ducks... <-radiant.matrix-> Larry Wall is Yoda: there is no `try{}` (ok, except in Perl6; way to ruin a joke, Larry! ;P) The Code that can be seen is not the true Code "In any sufficiently large group of people, most are idiots" - Kaa's Law	[reply]


Welcome to the Monastery
	PerlMonks