Tuesday, May 19, 2009

FTP Technology rant

I have been building websites for more than 15 years now. I build locally then upload to a server. Often I will make changes spanning across many files in several directories. For 15 years I have been wondering why I cannot tell my ftp client to push EVERY file with a date stamp since X date/time.  I've purchased dozens of versions of different ftp clients totaling well over $1,000. Many have complicated tools that allow you to synchronize folders local to remote. These tools are invariably buggy and about as much fun to set up as having your wisdom tooth yanked out through your left nostril.

Why is it too much to ask that I remote to a folder and then say push from this local folder any file newer than X?  This is what I wish to do 999 times out of 1,000 when I am pushing files. This is what thousands of other programmers and designers want to happen when they ftp. You build, test locally, and then push your friggin changes live.  I do NOT want every file to be the same, I do NOT want every file in my local project to go live, I just want my recent changes to get pushed without having to dig into half a dozen different folders and move them manually.

Current FTP client: SmartFTP  (Other than the rant above, this is a solid client)

Last FTP client: wsFTP (Used it for years, but most recent version made re-installation too difficult)

Posted via email from tcoakley's posterous

No comments: