Jump to content

trq

Staff Alumni
  • Content Count

    30,999
  • Joined

  • Last visited

  • Days Won

    26

trq last won the day on September 10 2014

trq had the most liked content!

Community Reputation

255 Excellent

About trq

  • Rank
    Prolific Member
  • Birthday 06/12/1975

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The simplest way to gain request-start to request-end speed is to cache using something like akamai.
  2. Composer ships with an autoloader, just stick to one of the standards and use that.
  3. The point I'm trying to make is why have the rewrite at all if you're just going to use normal querystring parameters? I understand you want to force everything through a front controller, but why stop there? But yeah, you could just use the QSA flag to have apache append existing parameters. RewriteRule ^(.*)$ index.php?uri=$1 [PT,L,QSA]
  4. That rewrite rule removes the need for typical GET parameters by making your urls "pretty". So instead of this: users/activate-account?email_address=test&token=test You would use something more like: users/activate-account/test/test Of course then you need some sort of "router" to parse and handle these parameters for you. If this is your own framework you need to decide how your urls are going to be formed.
  5. The official site will have the best most up to date documentation, not that it's a very popular framework IMO.
  6. CodeIgnitor will teach you nothing.
  7. Codelgniter is an abomination and a dying project so forget it. Any of the other 3 are probably worthwhile though I don't hear much about Cake these days (but that is likely just the circles I hang in). As for where to start. This question gets asked all the time and the answer is always the same. Try them all and see. If I were in your position I would spend a weekend with each, and then decide. They are all very capable, so it's just personal opinions as to which one you like best.
  8. There's nothing you can do in Perl, Ruby or Python that you can't do in PHP, however, some of these languages do already have certain specific tools writen in them that can come in very handy when developing PHP. For instance, Vagrant (a tool for managing development environments) is written in Ruby. Provisioning tools such as Chef and Puppet are written in Ruby while Salt is written is Python. Capistrano (a deployment tool) is written in Ruby, though there are also deployment tools such as Rocketeer written in PHP. Basically, learning another language is never going to harm you. A decent dev should have at least a handful of languages under there belt IMO.
  9. It is. I use it on a daily basis with a few large Symfony2 based applications. It's a great tool. http://thorpesystems.com/blog/debugging-php-in-vim I'm pretty interested in taking a look at http://phpdbg.com one of these days too as it ships with PHP5.6.
  10. You have got to be kidding. http://www.w3fools.com
  11. We do not delete accounts. If you don't want it, don't use it, simple.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.