My Blog aims to be simple to use while taking care of many advanced features for the user.
Yes, of course you're aiming for simplicity! Aren't we all? Do these developers really believe that everyone else designs with complexity in mind? And as feature-creep sets in will they revise their stated goal? Not likely!
And don't get me started about "lite"!
-sam
Euphemism (Score:1)
"Aiming for simplicity" is usually a euphemism for "I've just started this system from scratch and it doesn't do anything yet."
Not all of us... (Score:1)
No (Score:2)
Obviously you haven't talked to enough Java developers.
Simple*r* (Score:2)
I sort of regret the name DBIx::Simple. Yes, it is simpler than DBI, but I never designed for simplicity. I designed for usability and readability, and simplicity is in this case just a tool.
Still, from a Perl module marketing POV,
Oh, and I do think some people design for complexity. One w
Re:Simple*r* (Score:2)
Yup, that's pretty obvious. But so what? Most new projects start out simpler than their older alternatives. And as time goes on they'll get more complicated as they expand to fill nearby niches.
Good! It's a terrible name. It tells me almost nothing about the module that I couldn't already tell from DBIx. Just by writing a DBIx module you must be
Re:Simple*r* (Score:2)
Re:Simple*r* (Score:2)
just to be snarky (Score:2)
:-)
Re:just to be snarky (Score:2)
-sam