Hacker Newsnew | past | comments | ask | show | jobs | submit | _suoiruc's commentslogin

I used to suffer with Cygwin. It is really slow to work with if you are used to native UNIX.

I never seriously tried this but I'm curious if it works:

http://www.suacommunity.com/tool_warehouse.htm


This made me laugh. Perfect follow-up.

That's the way to get the good stories onto the front page.


Maybe you could add in price comparisons to Dropbox, since they are just an S3 reseller.


I think they are a bit more than just a reseller.


Perhaps you could expand on that?

If you pay for Dropbox what exactly are you paying for? Software to communicate with S3?

I'll accept that the software (python+rsync+an icon) is arguably "value added", but for the paying Dropbox user, what they are getting is still S3 storage.

Am I missing something?


You're paying for a service that auto syncs your data across multiple devices efficiently and keeps versioned backups of everything. The fact that they currently use s3 for storage is an implementation detail.


So basically it's the same as rsync and a little scripting, but without commands and scriptability? I don't use Dropbox so I'm curious. I'd like to know if they're offering something to paying customers that S3 does not, apart from their particular combination of python and rsync. If we just focus on storage is Dropbox more expensive? If yes, by how much? I think this is a valid question.


If you just focus on storage, yes, Dropbox is more expensive.

But this is kind of like saying iOS is just an expensive closed variant of FreeBSD.

Since I'm not drawing a salary from Dropbox's marketing division, I'm not going to go in depth here but I'll just say that Dropbox can be used easily and efficiently by normal people who have never seen a command line. Whereas your home brew python+rsync scripts can only be used by nerds like us.


It would be interesting to see how your homegrown sync solution works on various operating systems (desktop + mobile) and offers a web-based UI to do the same on the go.

Maybe you discover the sarcasm in my comment. ;)


my dad loves dropbox. he would be lost with s3. for most people it's not "arguably value added"; it's the difference between possible and not.

(another vote for a log scale (or something equivalent, like a separate "units" that sets the scale to 1s, 10s, 100s...). also, the tick marks should be on reasonable, round values)


Right. And the topic of this thread is a price matrix for S3. Presumably your Dad is not going to be looking at it.


then maybe you should have said something along those lines earlier, instead of repeatedly asserting that s3 and dropbox are equivalent (and then asking if you'd missed anything).


Do you read carefully? When I asked if I missed anything I was referring to anything besides the arguable "value add". My apologies if that was not clear. But the value add is precisely what you focused on, and argued (predictably): the python, rsync and the icon. I'm asking about the S3 component.


I know these folks are well-meaning but I find these constant "warnings" to be insulting. What people really need to be aware of is that the folks making decisions of how the internet should run, "the experts", are not always as smart as they think they are. They make mistakes. And it's hard to get a bunch of know-it-all's to agree.

It's also hard to get the entire `net to switch their behaviour, and adopt something that is incompatible with IPv4, without telling them what benefit they will gain by doing so. Can you blame them? But the "experts" and their zombie followers sure are trying.

IPv4 works. NAT works. NAT can be traversed. So what is the problem exactly?

As a home user, I can set up my own NAT'ing scheme with private IPv4 space far easier than I can learn to deal with the added complexity of IPv6.

OK, now I will get skewered by IPv6 fanatics. How many of them are getting paid to do IPv6 consulting work?

IPv4: It Just Works. "Experts": They make mistakes, just like everyone else.

Now, let's hear from the "experts".


What happens when your ISP has to NAT you?


I think MS will acquire FB.

The FB social network will die, in time, but it's still the world's largest email address list, plus all sorts of personal information that can be used to insidiously coax consumers.

Every FB user should gather up all the email addys of their friends and keep them in a safe place offline. This way you never lose contact.

FB allowed people to submit their email addresses to a central website and thereby connect/reconnect with friends, colleagues and so forth. This sharing of email addresses is not a new thing, but with FB it occurred on an unprecendented scale. Billions of email addresses (that work!). That is FB's contribution. Gather those email addresses and keep them offline. Soon you may be able to form your own social networks that are private, secure and more functional than FB. But you will need the email addresses of your friends to get it started. Don't believe that FB should be the safe keeper of your email address book. They will do what they have to in order to survive as their business winds down. Those email addresses are its most valuable asset.


I'm not making the MS connection - are you saying that Facebook will be eventually required solely for its email addresses?


While it's too late to edit, the typo is driving me insane:

required => acquired.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: