Hacker News new | comments | show | ask | jobs | submit login

What's funny about this is that it's actually harder to write a program that only works between certain hours than it is to write one that works whenever it's available. As I posted in another thread: maybe there wouldn't be a programmer shortage if programmers actually worked on things that were valuable. A program to prevent someone from pasting in their password and a program to take a web service offline at a certain time involves a fair amount of engineering effort, but makes the world a worse, more disorganized place.

I always thought the role of humans was to try to stave off the effects of entropy. Work like this makes entropy do its business even faster. Think about that when you're sitting in your chair 10^100 years from now and the Universe's protons start decaying all around you: this is your fault for implementing a website that only works from nine to five.

In that case, they may as well take it a step further and have their employees "open" the website when they clock in when they arrive, and "close" the website when they leave at night.

Good idea! The system can even have a message that says, "Although we plan to open at 9am, nobody has arrived to turn me on yet."

It could have to deal with scarcity, as time that is scarce is perceived to be higher valued, as booking office hours with a professor, for example. But that's just my economics take on it.

Regardless of that, it still makes no sense to time-constrict a websites uptime. It's not as if websites run on manual labour! (well, it takes some to create one)

The irony is that a site that says "someone needs to come in and turn me on" must already be turned on. They've already written an app that has 100% uptime, they just use their uptime to claim the system is down.

Disabling a website during certain hours is not a massive feat of engineering.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact