Sadly, its name was not "Babe"

[drwex]

In other news, what are people using for image sharing these days? The plusterfuck has invaded Picasa and rendered it nearly unusable (I can't just share a photo, I have to "post" and manage sharing on my posts and blah blah whocares and make sure you remember to turn off whatever Google thinks is its clever photo-processing hoo-hah). Imageshack wants paid signs-ups, pfui. Flickr? Pinterest? What's the most usable for quick photo shares?

Comments

[drwex]

So you're paying for hosting of domains, and they provide you with a Web server that serves up your HTML pages. So the question then comes down to the tradeoffs of writing one's own code versus using a vendor's code. That's sort of the classic build vs buy decision. So long as you can write the features you want and your desires for them don't change it's likely the case that build makes more sense.

The features I want (image resizing, slideshow capability, the ability to permission and link individual items as well as collections) are things I could do but don't want to be bothered with. I'm pretty sure I could script P'shop to do the sizing and the rest would be a reasonably easy set of PHP coding. Scripting the upload might be a little more annoying, but that could be a manual process.

I make less than you do, but let's ballpark that at $500 of my time to do this work. If I say it's taken me $100 of my time to select a vendor (so far it's been less but eventually) then over some number of years I'd pay out that $400 worth to have someone else provide the code and services I want. I then estimate the probability of the vendor failing or changing its features versus the probability that I'd have to go in and tweak or maintain/expand my own code.

So at some point in the future, it's likely that the "buy" decision turns out to be more expensive, assuming an otherwise-static world. I think I expect things to be more problematic and less static than you find them to be, but I understand your reasoning better now.