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

My college used DC++ to internally share music, movies, tv shows, and porn. You could browse someones entire media collection. It gave you an overall sense for their taste in music and was a great way to find new bands. Reading about Napster reminded me how much I miss this feature.

The article glosses over how slow Napster '99 was. I remember waiting a couple hours to download an album. Fast downloads are more important than social features. I do not miss Napster.


RE: slow downloads thru Napster

Of course, high speed internet is much more prevalent now in 2012 than it was in '99. Downloading an album in '99 sometimes meant you were downloading from PC's with only a 56k modem for connectivity.


Good point. It's not fair to associate Napster with slow download speeds. I would have loved to see how Napster evolved with broadband. Tragic they were shutdown.


In countries such as Sweden that was already the case. I never downloaded anything on napster in 56k-speed unless I was really desperate. Broadband was common enough that limiting yourself to high-speed downloads didn't limit the supply, which was kind of obvious considering that those with broadband typically had many orders of magnitude larger libraries :p


To be fair, this was the age of dial-up, not broadband.


I disagree. 97-99 were the years of massive broadband cable rollout to suburban America. This was the time that broadband arrived, and you see it reflected in the software of that era particularly video games for example Quake, Half-Life, Counter-Strike, Ultima Online, Everquest. It was the boom of real time multiplayer, which required a broadband connection.


It was broadband (well, high speed LAN) on college campuses.


And now, my university uses Mojo to browse and download an entire users collection. It works incredibly well, and you really do get to know people. I remember meeting someone a year after downloading almost a 1/3rd of their library, and being able to talk right away.


Demoralizing indeed.

Google's acquisition of Slide for $100m crushed me. Myself and several others built more successful companies. We had 10x the userbase, larger profits (assuming this based on userbase), and fewer employees (team of 3 here). The difference was I was bootstrapped and working in stealth.

Lesson's learned: avoid bootstrapping. Raise venture capital from well networked investors. Do not work in stealth mode. Do a lot of PR. Be loud!

This ensures that the failure of your company will be an embarrassment for your investors. The louder the better. They will be inclined to have a friend buy you out to save face.

Disclaimer. I'm not saying that should be your primary goal. Goal number one should be passionately building a product you love. A buddy exit is simply a safety net.


don't be demoralized, and don't let others decide how you should run your business or what you should value. if you have a profitable business be happy with your success and build on it. lottery winners happen every day, don't let that ruin building great products and businesses for you. the problem with outside investors (any investors, VCs, angels etc.) is that your business automatically inherits their values, and if their values are different enough from yours the friction could destroy your business and/or destroy your values.


At some point, depending upon why they're buying, I think having fewer employees is a bad thing. It means whoever is acquiring you has to do more work to turn it into a fully fledged business. At least that's the sentiment I heard when our startup sold (4 employees total).


It's no secret that the "going rate" for startups that are successful and get acqui-hired is $1-2M per engineer.

It's hard for big companies to find talented engineers, and so when they acqui-hire, they can just instantly shuffle those smart people out of the project they're working on and onto something else.

The bet is that each smart engineer will provide at least $1-2M of value to the company in the long-run.


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

Search: