4 ms·

Ah yes, the inevitable "I write my own framework" post. This completely overlooks the fact that with a well-known framework you have thousands of other develope

Ah yes, the inevitable "I write my own framework" post. This completely overlooks the fact that with a well-known framework you have thousands of other developers available to help you if you should run into a problem. It also overlooks the value of not re-inventing the wheel. > I've looked into frameworks like Django. It's not good because it abstracts away the functionality of the database. The Django ORM is no more or less easy to do your own queries as CakePHP, Propel, Doctrine, Hibernate, or SQLAlchemy: blogs = Blog.objects.raw('SELECT * FROM myapp_blog')

mgkimsal 16y ago
"with a well-known framework you have thousands of other developers available to help you if you should run into a problem" Not always true - I'd say often not true. 1. I have to learn where to get support from these thousands of other developers. 2. I have to read through dozens of posts from others asking the same questions I have, but often phrased inconsistently. 3. I have to figure out which answers are correct, and which are wrong, and which were correct 2 years ago, but aren't right currently because 2 libraries are now deprecated. 4. I have to learn enough about the framework to be able to formulate coherent questions using the proper terms and express my specific problem. 5. I have to deal with 0 people responding after 4 days of posting. 6. I have to deal with responses just being "me too". 7. I have to deal with responses being "RTFM" or "LMGTFY". 8. I have to deal with well-intentioned people who ask me for help replicating my setup in their environment so they can help me. And there's likely more variations I could think of that make the magic "there's thousands of developers to help" argument null and void in many situations.
- hdctambien 16y ago
  I think stackoverflow.com pretty much solves all of these problems for you.

mgkimsal 16y ago

"with a well-known framework you have thousands of other developers available to help you if you should run into a problem" Not always true - I'd say often not true. 1. I have to learn where to get support from these thousands of other developers. 2. I have to read through dozens of posts from others asking the same questions I have, but often phrased inconsistently. 3. I have to figure out which answers are correct, and which are wrong, and which were correct 2 years ago, but aren't right currently because 2 libraries are now deprecated. 4. I have to learn enough about the framework to be able to formulate coherent questions using the proper terms and express my specific problem. 5. I have to deal with 0 people responding after 4 days of posting. 6. I have to deal with responses just being "me too". 7. I have to deal with responses being "RTFM" or "LMGTFY". 8. I have to deal with well-intentioned people who ask me for help replicating my setup in their environment so they can help me. And there's likely more variations I could think of that make the magic "there's thousands of developers to help" argument null and void in many situations.

hdctambien 16y ago
I think stackoverflow.com pretty much solves all of these problems for you.