Why would I rely on something that keeps being re-invented by everyone every month, with unknown future support?
I'm not insane. I'm writing my own web application framework. If I'm the one writing it, I know it inside-out. If I use it, I update it myself. That's the only way to be sure.
Truly, you are correct. In fact, why would you rely on a programming language that keeps being changed every few months. I am writing my own programming language. If I'm the one writing it, I know it inside-out. If I use it, I update it myself. That's the only way to be sure.
In fact, why would you rely on an operating system that keeps being changed every few months? I am writing my own operating system (written in the programming language I created of course). If I'm the one writing it, I know it inside
You don't need to worry as much about security vulnerabilities
It's mantras like these that lead to so much insecure web code being written. You should always be equally worried about security no matter if you're using a framework or homegrown code.
I don't really get why people use a framework for php at all. The whole point of php is so you can write web app code anyway you like. Writing to CI spec is such a waste of time since you literally have to track their APIs back to the source, and the functions defining these APIs are all over the place. Inject your own modules or applications into the existing session is hours of work just to track down what the hell they did. All the customer code are sitting in an include container, that handle sessions. Attempt to use custom session verification for binary data transfer is a royal pain. Those who think CI documentation is good are kidding themselves or just trying to do something extremely simple.
I beg to differ, there is no difference tracking down a piece of code in your mountain of framework definition and tracking down a piece of code in a mountain of procedural spaghetti code. In fact, it probably is easier to track down the procedural spaghetti code via grep than search recursively over 6 directories deep framework definition with the same code appear over and over again in 500+ different self inclusive source files. It doesn't matter how large your project is, as long as you maintain a sane c
Philosophy: A route of many roads leading from nowhere to nothing.
-- Ambrose Bierce
Web application framework? (Score:0)
Why would I rely on something that keeps being re-invented by everyone every month, with unknown future support?
I'm not insane. I'm writing my own web application framework. If I'm the one writing it, I know it inside-out. If I use it, I update it myself. That's the only way to be sure.
Re: (Score:0, Redundant)
Re: (Score:5, Insightful)
You don't need to worry as much about security vulnerabilities
It's mantras like these that lead to so much insecure web code being written. You should always be equally worried about security no matter if you're using a framework or homegrown code.
Re:Web application framework? (Score:2)
I don't really get why people use a framework for php at all. The whole point of php is so you can write web app code anyway you like. Writing to CI spec is such a waste of time since you literally have to track their APIs back to the source, and the functions defining these APIs are all over the place. Inject your own modules or applications into the existing session is hours of work just to track down what the hell they did. All the customer code are sitting in an include container, that handle sessions. Attempt to use custom session verification for binary data transfer is a royal pain. Those who think CI documentation is good are kidding themselves or just trying to do something extremely simple.
Re: (Score:2)
I beg to differ, there is no difference tracking down a piece of code in your mountain of framework definition and tracking down a piece of code in a mountain of procedural spaghetti code. In fact, it probably is easier to track down the procedural spaghetti code via grep than search recursively over 6 directories deep framework definition with the same code appear over and over again in 500+ different self inclusive source files. It doesn't matter how large your project is, as long as you maintain a sane c