This is endemic of those who write “just enough code to be dangerous.”
Now, if you were to say, “hey Eric, I just don’t grok this CSS purity
stuff. I’m a reasonably good HTML programmer and even used Notepad quite
a bit in my day” (paraphrasing his PHP comment), I suggest you’d be
playing in his sandbox and get a very impassioned response about why
his area of expertise matters.
I’ve been dealing with frameworks for years and the realization I came
to is that there is nothing you can do using a sound, tested, robust
framework that you can’t also do using lots of lines of spaghetti Basic.
This is to say that if you don’t see the benefits of the framework and
think you can write all the code justfinethankyou, then you aren’t
going to come around soon.
Rails is not mass hysteria. Neither are all the other frameworks 90%+ of
the professional software developers in the world rely on. There are
Java frameworks, C++ frameworks, Python framworks, and you name it. Why?
Because software would take far longer to build, without frameworks; it
would be inherently more flawed because each new project would be
essentially new code; Web 2.0 would grind to a screeching halt.
Frameworks are about leveraging investment and capturing common cases in
base, tested, optimized code. DRY.
Of some concern is the “me too … i don’t get it either” set of
Is it really possible that someone would feel absolutely comfortable
with the notion of memorizing all the CSS rules, cross-browser
idiosyncracies, and hacky work-arounds, yet at the same time feel the
learning curve on an application framework is too steep?