Jump to content


Staff Alumni
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by trq

  1. The simplest way to gain request-start to request-end speed is to cache using something like akamai.
  2. CodeIgnitor will teach you nothing.
  3. 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.
  4. 2 & 3 will never happen using vim's autocompletion. And 1, well, vim gets its context from a few different locations depending on the keystroke you use to start completion. Generally, I only ever use the context of the current buffer. This meens variables will only be completed if they already exist in the current buffer. Not that I use completion often anyway.
  5. Not at all. That's why I said I rarely use it.
  6. vim's code completion is the best (quickest and most flexible) Ive used, not that I use it often.
  7. trq

    PHP Micro-Frameworks

    Silex (http://silex.sensiolabs.org) is an awesome micro-framework built on the shoulders of Symfony (another great though full stack framework).
  8. $lstr needs to be the second argument to prepare() not query().
  9. Instead of using variables directly within your query, you use placeholders. You then pass your variables in as extra arguments to prepare().
  10. Have you looked at the documentation for the prepare method? It looks similar to sprintf, and it looks like your code is not using it properly.
  11. Why would you change it in the first place knowing you only get 1 change every 365 days? I think you should keep the name you have, at least for a little while.
  12. Just a heads up. I have changed my display name. thorpe -> trq
  13. This resonates with me more than anything else. http://blog.sanctum.geek.nz/series/unix-as-ide/
  14. My main motivation for working in vim is the fact that we do allot of remote stuff via ssh on client machines at work. So, now I can use the same editor under all circumstances. Even when I work from home, it's so much easier to just connect to the vps, ssh in and open vim in a terminal. I don;t have to worry about the overhead of a Desktop.
  15. Have you tried an IDE? I used to think a simple text editor was all I needed too, but then I tried an IDE. The only time I use a regular text editor now is just for real quick edits, or stuff that I don't want to make into a project in my IDE. IDE's tend to get in my way. All I use is vim with a few plugins: https://github.com/tpope/vim-pathogen https://github.com/tpope/vim-fugitive https://github.com/tpope/vim-unimpaired https://github.com/vim-scripts/taglist.vim https://github.com/vim-scripts/sessionman.vim https://github.com/vim-scripts/bufexplorer.zip https://github.com/tpope/vim-surround https://github.com/vim-scripts/FuzzyFinder
  16. I'm a massive vim fan so don't really have much of an opinion when it comes to IDE's.
  17. Jeeze, big move. I had been thinking of doing the same but feared it might throw to many off.
  18. Done. Old: ryanweekly New: ryanfilard
  • 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.