back

by toddmorey·8y ago·view on hn ↗
This cycle blankets every new technology as a misstep that we’ll revert back from. The real cycle is that we continually test new ideas and new approaches, learn their strengths and weakness, and ultimately keep what works and discard what doesn’t. Sure we miss the ball more than we connect. But take this example: We now have native JSON support since Postgres 9.2. So did we abandon the document model or learn more about how and where it might be appropriate? Some advancements are even more sweeping: I don’t think we’ll ever go back to FTP or even CVS from the Git-centric workflows we now have.

Technology, in my experience, never seems to reward too much optimism or too much cynicism.

2 comments
FTP workflows are so extremely widely used in today's world that it's inconceivable you think it's behind us.
Maybe in frontenddev/small companies/small largely static websites FTP pervades, but I'd argue that most developers that deal with any real complexity probably use some kind of source control system to 'share' files rather than some kind of FTP program. And I'd be very surprised if relative FTP usage hadn't decreased significantly over the last 3-4 years (But this is all quite anecdotal, and I could be wrong).

Something that does surprise me is that Panic's Coda and Transmit apps still seem quite successful, so maybe my perception is out of whack.

In some industries FTP is used quite heavily as part of batch workflows. Payment processors and things seem to love it.
FTP is still extremely widespread in the form of SFTP.
Git centric workflows are ripe for change. FTP or sftp is still used very often.