3 ms·
I think you should write a micro-framework. I feel the same way about ORM. It's completely irrational on my part because I'm extremely comfortable writing absur
by lysol 15y ago
I think you should write a micro-framework. I feel the same way about ORM. It's completely irrational on my part because I'm extremely comfortable writing absurd numbers of joins using crazy criteria for my day-to-day at work, and have some cognitive dissonance because here I am, about to let a library do all the heavy lifting for me.
The end result is in order for me to accept ORMs I had to know the pattern. To know the pattern, I had to write a simple ORM layer on my own. It wasn't pretty, it wasn't as good as SQLAlchemy, by far, but it gave me enough insight to appreciate them, and to know when to use them. By all means, keep using CGI, but leave it to the small projects.
And yes, you're too used to PHP. Branch out, it's more fun.
- chromium 15y ago"you're too used to PHP" So I should write the micro-framework in Ruby? Any suggestions for starting out with that?
- lysol 15y agoNot at all. It's just good sense to pick up other languages in general. Find one that has something interesting, play along with the official tutorial, writing the code as you go along.
- robflynn 15y agoI will second the write your own micro-framework statement. When I first began toying with frameworks, I felt much you, chromium. I understood the concept and the idea behind everything, but some of it felt like "magic." So, I sat down and wrote a basic clone of rails in PHP. It lacked a lot of features but it had basic routing, models, views, controllers. I even wrote some code to generate migrations and applying/rolling back those migrations. I never even finished that little faux framework because once I got into it and started mucking around, everything kind of clicked into place for me as far as demystifying the "magic" of everything.