Hacker News Reader

I'm talking about professional development.

And scalability is one of the reason for which you may want to avoid frameworks.

If you're a professional you want to fully understand your data and how it is generated/modified if you want to solve both functional and load scalability issues.

View on HN

Sure, but I don´t want to scatter all the SQL clauses over the code. Also, what would happen when you want to modify the way the data is accessed? I.e, you want a write-through cache in front the DB?

I can agree with you if we talk about generic frameworks. I would not take none of them for a big site, or at least I would not take it as is. But I would definetivelty use a framework, either a completely custom one or a modified one.

Reply on news.ycombinator.com