trq

The simplest way to gain request-start to request-end speed is to cache using something like akamai.

Composer ships with an autoloader, just stick to one of the standards and use that.

The official site will have the best most up to date documentation, not that it's a very popular framework IMO.

That is correct.

CodeIgnitor will teach you nothing.

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.

Your code is unreadable.

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.

The second question in particular assumes you are talking about client side (executed in the browser) javascript. Server side javascript is becoming more and more popular these days and is capable of making use of many different database systems.

vim for Windows? Yuk.

We do not delete accounts. If you don't want it, don't use it, simple.

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.

Not at all. That's why I said I rarely use it.

vim's code completion is the best (quickest and most flexible) Ive used, not that I use it often.

Silex (http://silex.sensiolabs.org) is an awesome micro-framework built on the shoulders of Symfony (another great though full stack framework).

This resonates with me more than anything else. http://blog.sanctum.geek.nz/series/unix-as-ide/

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.

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

I'm a massive vim fan so don't really have much of an opinion when it comes to IDE's.

That's because MS sux balls.

Hmmm, I smell spam.

There is no definitive answer, just opinion. Often the one that is well suited to your style of development and specific project requirements will be the best one to use.

I used to use dynamically loading js, but it ended up being allot more efficient to put all js into one file and the minify it. Its the actual http requests to multiple files that hurts more than size. Of course it would also depend on what sizes where talking about. Loading a 50k-80k file just to use one function etc etc.

Have you checked out some of the editors mentioned in this thread?

This board is here for questions directly relating to already existing Third Party code. It is NOT a code repository or the place to post requests looking for specific scripts. If you can't find the script you are looking for on Google, you either don't know how to use Google or the specific script does not exist. DO NOT request help with searching.