Most importantly, we want you to know that Classic Slashdot isn't going away until we're confident that the new site is ready. And — okay, we've got it — it's not ready.
Why are you so inflexible on the idea of keeping classic slashdot *forever*. Think of it as a protected historical landmark in the internet space. To help future generations understand where this 'blogging' thing really came from? Computers are good like that, keep classic.slashdot.org FOREVER and your audience^H^H^H CONTRIBUTORS might stop rallying against you.
Probably becasue it costs a lot of moeny to maintain the old crappy site and the new modern awesome site.
Work isn't free, the site isn't free, servers aren't free. Got it?
I get it. But I don't think you've seriously considered it. You have to weigh the benefits of the work vs the cost. The comments all day today, should illustrate an estimate of the value gained by that maintenance cost. Likewise, you aren't honestly suggesting that server cost is a real issue are you? One server can serve multiple code paths. And the bandwidth and server resources are proportional to the number of visitors accessing that service. And by the time you imagine that many people would cho
The only way to learn a new programming language is by writing programs in it.
- Brian Kernighan
Why not keep classic forever? (Score:5, Insightful)
Most importantly, we want you to know that Classic Slashdot isn't going away until we're confident that the new site is ready. And — okay, we've got it — it's not ready.
Why are you so inflexible on the idea of keeping classic slashdot *forever*. Think of it as a protected historical landmark in the internet space. To help future generations understand where this 'blogging' thing really came from? Computers are good like that, keep classic.slashdot.org FOREVER and your audience^H^H^H CONTRIBUTORS might stop rallying against you.
Probably becasue it costs a lot of moeny (Score:1)
to maintain the old crappy site and the new modern awesome site.
Work isn't free, the site isn't free, servers aren't free.
Got it?
Re: (Score:2)
Probably becasue it costs a lot of moeny to maintain the old crappy site and the new modern awesome site.
Work isn't free, the site isn't free, servers aren't free.
Got it?
I get it. But I don't think you've seriously considered it. You have to weigh the benefits of the work vs the cost. The comments all day today, should illustrate an estimate of the value gained by that maintenance cost. Likewise, you aren't honestly suggesting that server cost is a real issue are you? One server can serve multiple code paths. And the bandwidth and server resources are proportional to the number of visitors accessing that service. And by the time you imagine that many people would cho