Hear Hear! This brings me to the point of responsibility.
If you slap up some code that, say, parses some CGI-params and slaps them in the database, shouldn't you at SOME point be made aware that there is actually a large chance you're opening up the server you're putting this crappy code on to Injection or CSS attacks? I mean... frameworks represent code re-use but they also represent best practices which means that they help you to educate yourself more about problems that can occur and best practice solutions to these problems. Thus, frameworks FTW! :-) On 17/11/2008, at 2:40 AM, Michael Klishin wrote: > > 2008/11/16 weepy <[EMAIL PROTECTED]>: >> Consider the approach: >> >> 1) Take a standard HTML page >> 2) Modify it to include some simple PHP (e.g. <%= $myvar %>) >> 3) Rename the file to .php >> 4) Upload page. > > You can do it with a flat merb app, Apache and sftp. But rapid > prototyping not always equals to "write some crap to throw away" > because some prototypes of this sort later put into production and > someone has to maintain them. That's just anti humane in my mind. > > So prototype carefully. > -- > MK > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
