Stage 1: Web Development

Tagged on: ,

19 thoughts on “Stage 1: Web Development

  1. trodmi

    If one is forced to work with php and mysql then what would be the best practice? Is there something better than smarty?

  2. GammaSouljah

    whether your doing static dynamic pages or full Ajax applications you still need to select and insert data to a database, process it and format it in either full html content or xml/json requests back to the browser. PHP is still the easiest language to do this with.

  3. TheMetalPerson

    With ajax features becoming more in demand, it becomes harder to manage older systems based on the back end creating while pages dynamically on the server side. It causes you to have to rewrite the javascript every single time you change the php templates. Its much simpler to just have a web server feed static pages (seeds) that are rich in javascript and talk to a now viewless server.

  4. TheMetalPerson

    I’m more against the paradigm of generating html/tempate content on the server side. The html, css and javascript (and whatever else you use on the front side) should be talking to whatever you have on the back-end through a defined convention instead of php generating a bunch of html to spit out.

    using this approach, it doesn’t really matter what you use on the back end, as long as it can handle web requests and interface with your client. the server side becomes simpler.

  5. GammaSouljah

    OK that is not fair. Coding Object oriented PHP 5 is a lot easier and securer than coding Server Side C or C++ if you want to have raw speed. Java is about the same speed as PHP code that make use of caching with APC so good PHP code is powerful, fast and a lot easier to learn and code. PHP is also so ubiquitous that yo app will run on any host. You will definitely need a dedicated server to run c++ and java apps on.

    Learn PHP if you need to create real production apps in the shortest time.

  6. TheMetalPerson

    server side template systems of any kind (including php hypertext preprocessor) are counter intuitive to a decent AJAX architecture.

  7. TheMetalPerson

    i wish recruiters and HR would stop asking me to learn retarded shit. why must i always sink down to this level.

  8. TheMetalPerson

    smarty is retarded. i used it for a year at my job and it served absolutely no purpose. I later decided that php served no real purpose as well. Want a good template system? how about html and css. use javascript and a protocol to talk to an ajax server. server side template systems create are redundant as users demand more interactive javascript anyway and any change to the server side template must be changed in JS anyway..

  9. GammaSouljah

    in the grand scheme of things smarty just makes working with php variables in html content a little easier to understand if your are the designer. But is pointless if your the developer and designer as its just another level of time waste to achieve nothing you can’t do with raw php.
    It can potentially also slow your applications down (even with caching) so i would not bother with it. only use it if your designer has no clue about php or you don’t want to give them access to the php parts.

  10. GammaSouljah

    Kohana PHP – (codeigniter fork)

    Wipes the Floor with codeigniter. if your serious about writing Fast, Light weight but Powerful php apps, then use that.

  11. GammaSouljah

    this guy is the worst teacher ever.
    Why don’t you get you facts right before confusing people even more than they need to be

  12. disolvedboi

    Just a correction, HTML is NOT how you format a page… you do it through CSS. Please make sure you correct that so people do not get confused.

Leave a Reply