Journal BlackBolt's Journal: Slashcode 5
I don't mean to be a downer here, but Slashdot is really falling apart. What kind of "improvements" are these guys doing here? I'm finding it nearly unusable at least 85% of the time. I wouldn't mind so much except that this site is a cornerstone of the Open Source Community. I'm amazed Microsoft or someone hasn't mentioned, "By the way, I *tried* to get on Slashdot to learn about this pesky Gnu/Linux thing, but well, golly, if the site wasn't so badly coded it darn crashed my whole computer! So I went back to MSN and enjoyed the smooth fast and secure fun that is to be had there - hand coded by the best Microsoft Software Engineers money can buy. We give you our Microsoft Guarantee of quality. Unlike those dirty hacker guys who don't seem to care, but who am I to judge? Live and let live, I always say."
I hope not (Score:1)
Hmm... (Score:1)
I maintain several computers (RHlinux, winME, and MacOS9) with several different browsers (NS4.78, Mozilla, Opera7.11, IE5+) and they all seem to run fine. Have you ruled out your computer as the "culprit"? Usually, web sites dont crash things, except for broken JAVA or the typical windows+IE combination which has its own problems because MS likes to break standards. Could also be a p
Re:Hmm... (Score:1)
ok, I've run into these here occasionally too, and they are definitely NOT from your client-side. Sometimes refreshing the page makes em go away. They may or may not be specific to slashcode either, since they could also be Apache problems. Anyway, check the bug reports at sourceforge and submit a bug report.
And we've already known [slashdot.org] slashdot has been dying for a long time!
Re:Hmm... (Score:2)