carpal

...

I use hulu a lot too. A pretty good resource, all in all.

Not really. I cancelled cable about 6 months ago, and I haven't looked back. The writer's strike helped a bunch, though.

I'll tune in to broadcast TV to occasionally watch Jeopardy while eating dinner, or to catch a new episode of House (pretty much the only show I watch regularly).

P/E ignores a lot of things, too. Old-line manufacturing businesses usually have a ton of assets (machinery, land, etc) that boost their valuations.

I doubt HotOrNot has much more than the brand name and domain, as far as assets are concerned.

3x revenue is pretty standard for businesses that aren't really growing anymore. Seems like a pretty solid deal to me.

It is also one of the most common ideas proposed at Startup Weekend.

I did pretty well on a 256 meg slice. I outgrew it after awhile, and I'm currently running 8 mongrels on a 512 slice, and I'm pretty much hitting the top.

RAM is by far the biggest bottleneck for me.

Overall, Slicehost is great. I just wish they'd include more RAM in their plans.

His idea of a complex web application is completely misguided. He sees a "complex web application" as a "desktop application that runs in the browser." That's wrong, and it is no wonder why such "complex web applications" run better on the desktop.

My idea of a complex web application is one that simply cannot be done on the desktop. I'm making one and I don't even include any Javascript libraries. AJAX != Complexity.

It depends on what your bottleneck is. RAM? Processor? Bandwidth?

If it is RAM, you'd be better off getting fewer servers with more RAM on each.

If it is CPU, you'd be better off trying some software configuration options before scaling horizontally.

If it is bandwidth, you'd be better off getting a server with a fatter pipe.

BBA in CIS from Georgia State University

Good god. Pizdaus links on yc news? Say it ain't so.

Yes, it is. Browser-based, so that you don't run into sharing issues (common in small companies), or platform issues (common with cutting-edge companies).

That's exactly the problem I'm solving.

Glad to hear there's a market for it.

That's a silly reason for a startup to die. Design is rather unimportant to the success of a site. Heck, look at Craigslist, or News.yc.

Slowly whittling away at an online accounting suite for small businesses. Stubbed out the underpinnings, and just did the first major design iteration. Should show it to the first potential users in a month or two.

"Jan 22, 2005 12:47:00 AM"

I think you might be confused between Ruby and Rails.

Ruby's current version is 1.8.6, while 1.9 is nearing an official release and 2.0 is still very experimental at this point.

Rails' current version is 2.0.2, but the last release on the 1.x branch was 1.2.6.

I'm going to assume that you meant Rails 1.2.x versus Rails 2.x. Yes, there are a lot of advantages. Mainly though, there aren't really any disadvantages- there's no reason not to use Rails 2.0.

The requirement of an email address makes this a non-starter for me. I think you should be able to search and add without an email address. The reminder feature should be optional.

An OS X dashboard widget would be very useful, as well.

I really doubt this will have much of an impact on domain tasting at all. At worst, they will make slightly less money because they'll have to use an ad service that won't target ads as well as Google.

Domain tasting will be alive and well until ICANN puts a stop to it.

<80k household income as lower class? That's insane. Maybe in the upscale districts of the biggest cities, but everywhere else 60k/year is solidly middle class. In the rural areas of Florida, 60k/year might even be considered Upper Class.

This is mostly bullshit. The guy is trying to do things in Rails the wrong way and complaining about it failing. He does have a few legitimate points, but I guess I'll go at it point by point, because it is fucking long:

-AR find works fine for me, in most cases, in those cases you can always fall back directly to SQL (has happened a total of two times for me). The guy very incorrectly states that the :group stuff will choke in Postgres. It does not. There is a separate driver for each database that will make the queries compliant with the specific DB.

-When using joins, you're supposed to use :include, or has_and_belongs_to_many. These are NOT read only, and work very very well. He's complaining that something he is doing the wrong way does not work. That is because he is doing it wrong, and it isn't SUPPOSED to work.

-I agree with his point about understanding Rails and the options hashes. At this point, I really wish that Ruby had named arguments, as the options workaround gets really annoying.

-I don't understand what he means by quality assurance. Rails has an incredibly large automated testing suite. I've been using Rails for two years and I've found one bug. I really just have no idea what he's trying to get at.

-On the last point, about the "big-picture", he is provably false. If you've written a Rails app and there is even ONE XSS injection opportunity, you've done it wrong. Spend two seconds in the API docs and you will find this function called "sanitize":: http://api.rubyonrails.org/classes/ActionView/Helpers/Saniti...

It helps if you read the fucking documentation before you criticize something.

I don't mean to be an ass, but you are not going to have 1k simultaneous users. If you did, you would be able to pay someone who had a better understanding of how webservers work.

One decent machine running 10 mongrels on a reasonably well-designed Rails app will easily be able to handle 100 requests per second. That is more traffic than you will ever get, I guarantee you.

1) I've never gotten much utility out of Rails books. I've generally gotten much more use out of the API docs and blogs. That said, the Agile Web Development with Rails book is pretty much standard, and Rails Recipes is good for code examples. However, if you're doing something in Rails Recipes, there's probably a plugin for it by now.

2) Because it is very easy to implement an idea in a day and see if it sticks. More than that, when you're faced with a task that might not have much reward, it is easier to do if it doesn't feel like work. Programming in PHP/Java/C#/etc generally feels like work. Programming in Ruby generally feels like fun.

Eating my own dog food.

Sitting in the San Francisco airport because it is snowing in Atlanta.

I've scientifically confirmed that The Talking Heads made the best hacking music known to man.

Aside from that, I listen to a lot of Of Montreal, other indie pop, some electronic and movie soundtracks (There Will Be Blood and The Fountain OSTs are both great).

I find it funny that the 31 lines of code in the example can be easily reduced to 8:

  def merge(a, b)
    c = []
    c << (a[0] > b[0] ? b.shift : a.shift) until a.empty? || b.empty?
    return c+a+b
  end

  def mergesort(a)
    a.size <= 1 ? a : merge(mergesort(a.slice!(0,a.size/2)),mergesort(a))
  end

Language Power > Language Speed

Excellent. Thank you!

Awesome. Can you add the same thing to each user's comments page, too?

I've been using git for backups the past few weeks. Works incredibly well.

I only backup code and documents though. For other things it might not be such a great solution.