Domain: schend.net
Stories and comments across the archive that link to schend.net.
Comments · 65
-
Re:Java Not Required
Hah. A year ago I tried it, after all these re-assurances that it doesn't require Java. What's the absolute first thing it pops up after being installed?
"OpenOffice requires a Java Runtime to perform this task"
If it actually doesn't require Java, like you and so many others claim, it's doing a piss-poor job of working without it. Me? I'll believe my own eyeballs: OpenOffice requires Java.
-
Re:Less is romantic, it isn't more
You can put Word 2007 into an extremely minimal writing mode in 2 clicks:
http://schend.net/images/screenshots/minimal_word.png
(Using Word here, because it's most people's example of a "bloated" writing tool. I wager every word processor has a similarly-minimal fullscreen mode.)
-
Re:Gee, what does that tell you?
Adding a rich text command field is useless for the half dozen of HTML tags you can insert. Adding more tags would be counter-productive - the existing ones already let you structure your post, which is the important part; enabling style changes for each comment would make the site unreadable.
Of course I should have expected the grumpy "we hate technology even though we visit a tech site" and "we absolutely hate anything that makes software more usable" crowd to support that idea, so big mistake on my part. At the very least, they could get rid of the "HTML" comment formatting mode, which is not only completely useless, but frequently results in "giant paragraph of death" posts because new users think it's required to add HTML tags to the post.
But seriously, this site *badly* needs a usability review and revision. Other than SourceForge itself, this is by far the least usable website I've visited in the last 5 years.
So that's not really important. I would prefer if they fixed the CSS for Idle - the comment textarea still doesn't use the whole width.
That idle bug is in their bugtracker, but since they never actually *read* their own bugtracker, it's still not fixed. If you care, here's a bunch of screenshots I made for bugs I entered about Slashdot-- of those 10-12 bugs, I think maybe 4-5 are fixed, and they were fixed by accident. (That is, they were fixed as a side-effect of another change, not because any Slashdot devs actually read the bugtracker.) If you really care, I could dig up the SourceForge bug links, too.
The sad fact is that nobody at Slashdot really cares at all. The people writing the code don't care to fix bugs or increase usability. The editors don't care enough to actually edit. And most of the submissions are nothing but people promoting their own projects, and also they don't care enough to actually edit. They just don't care.
-
Re:Why Slashdot generally avoids this
Yeah, but Slashdot's system has a lot of stupidities and quirks (probably bugs) in it as well. For instance, stick around long enough and you'll:
1) Never be asked to meta-mod again
2) Never be given mod pointsWhen I was new here, I got mod points and was asked to meta-mod pretty frequently. Now, neither happens-- for about the last 2-3 years. I'm assuming that getting mod points has something to do with participating in meta-mod, but that's kind of hard when the site doesn't let me meta-mod either.
:) Maybe this is supposed to be a "reward"? (Like the ability to turn off ads?)There's also the awful "overrated" and "underrated" mods, which I don't think should exist. Then of course, there's the modders, who will gladly assign "informative" to a post which is only a single sentence, or "insightful" to the same argument we've heard 50,000 different times-- but I guess there's nothing the code can do about that. And Flamebait is applied to everything.
Here are some ideas I have:
1) Fix the bug where longstanding users aren't involved in the mod system at all. Or, if that's done intentionally, give them the option to participate in modding again.2) Negative mods should be harder to use than positive ones. I think a +1 should cost 1 mod point, and a -1 should cost 2 mod points. To prevent confusion, display a confirmation before a negative mod is made: "Moderating this post as -1 Flamebait will cost 2 mod points, continue? Yes/No"
3) Unrelated to modding, but please, please make Slashcode at least a *tiny* bit smarter. How about an integrated Preview tab, so we can preview our posts without having to reload a couple times? How about fixing the obvious bugs in the parser, like how it won't display a less-than even if typed in "Plain Old Text" mode? How about fixing the broken layout when submitting comments in Idle? How about fixing ANY of the bugs I put in your database 2-3 years ago now? (See: http://schend.net/images/index.php?path=screenshots/slashdot/ )
-
Re:My apologies for a threadjack.
Just so you know, the weird oval depicted here: http://schend.net/images/screenshots/slashdot/weird_blue_oval.png
That oval is supposed to hold a '!', enabling you to tag it as "not this" basically. I believe this one has been corrected recently, or at least has in my browser.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:My apologies for a threadjack.
The classic discussion interface has changed too, it's actually more buggy than the 2.0 one at this point since apparently Slashdot hasn't heard of "regression testing".
All of the following buggy screenshots were taken with discussion 1.0 turned on:
http://schend.net/images/screenshots/slashdot/cant_save_prefs.png
http://schend.net/images/screenshots/slashdot/email_options.png
http://schend.net/images/screenshots/slashdot/floating_div_corrupted.png
http://schend.net/images/screenshots/slashdot/floating_div_font_size.png
http://schend.net/images/screenshots/slashdot/people_modifiers_cutoff.png
http://schend.net/images/screenshots/slashdot/post_headers.png
http://schend.net/images/screenshots/slashdot/post_reply_buttons.png
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.png (My particular favorite, still unfixed-- looking at it right now as I post!)
http://schend.net/images/screenshots/slashdot/sectional_options.png
http://schend.net/images/screenshots/slashdot/section_collapsed.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_comments.png
http://schend.net/images/screenshots/slashdot/slashdot_idle_template.png
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
http://schend.net/images/screenshots/slashdot/thread_outline.png
http://schend.net/images/screenshots/slashdot/weird_blue_oval.pngAnyway, the lesson learned here is that Slashdot is extremely buggy. All those images come from bug reports I've entered against it... very, very few of them have been fixed. (Maybe 2 or 3 of the entire lot? I'm too lazy to log into SourceForce, the worst bug tracking tool in the universe, to check.)
I submitted all those bugs in response to an editor who complained that I was griping about Slashdot without helping the project in any way. So I put in the bugs to help the project, and gasp shock amaze, Slashdot still sucks ass. Consider that a win for my side.
The other lesson learned here is don't bother to submit bug reports against Slashdot, like most open source projects they simply do not give a fuck about user-submitted bugs. Your time would be more productively spent smashing your forehead into a wall.
-
Re:Other performance gains
You should pop me off an email or blog comment, so we could hash through this.
Now that I'm trying it on my work machine, it's actually behaving closer to what you describe. (At least if I'm reading you right, I've never used Eclipse, so I really have no clue at all what a "perspective" is. And VS certainly doesn't seem to have anything that tries to explain that metaphor.)
In any case, starting with a computer with no VS running, here's what VS looks like when I open it by double-clicking a
.js file:
http://schend.net/images/screenshots/vs_opened_js_file.pngContrary to what happens on my home computer (where I wrote the last post), if I then double-click a Solution, the Solution will get its own window completely separate from the
.js window and with the correct UI elements visible. That's good-- just give the JS window a different icon, so I can tell it apart easier, and I'd be happy.TFS, however, doens't behave the same way. Here's what VS looks like if I just open it using the Start menu icon:
http://schend.net/images/screenshots/vs_source_control_explorer.pngNote that it opens up the Source Control Explorer by default, with the appropriate UI elements. (BTW, what's an "Explorer?" It the little pane to the right is an "Explorer", but the main content of the window is also an "Explorer", WTF does that term even mean?)
Here's the same window after I open a Solution that just happens to have no saved open tabs:
http://schend.net/images/screenshots/vs_opened_solution_from_source_control.pngCan you tell the difference? Other than the Source Control Explorer window flashing, there's *nothing* in the UI to indicate that I now have an open Solution. The Solution Explorer didn't appear, nor did the Toolbox or Properties Explorer. The only difference, as far as I can work out, is that the File menu activated Close Project.
Now if I manually go and show the Solution Explorer, then it'll have all the Solution files in it and all will be well. But why should I have to manually show it even single time?
This might be a bug, but VS is working off such a complicated UI metaphor that I have no way of telling what's a bug or not. What your team really needs to do is simplify the metaphor to something you can explain in less than a paragraph without referring to a competing project
:) -
Re:Other performance gains
You should pop me off an email or blog comment, so we could hash through this.
Now that I'm trying it on my work machine, it's actually behaving closer to what you describe. (At least if I'm reading you right, I've never used Eclipse, so I really have no clue at all what a "perspective" is. And VS certainly doesn't seem to have anything that tries to explain that metaphor.)
In any case, starting with a computer with no VS running, here's what VS looks like when I open it by double-clicking a
.js file:
http://schend.net/images/screenshots/vs_opened_js_file.pngContrary to what happens on my home computer (where I wrote the last post), if I then double-click a Solution, the Solution will get its own window completely separate from the
.js window and with the correct UI elements visible. That's good-- just give the JS window a different icon, so I can tell it apart easier, and I'd be happy.TFS, however, doens't behave the same way. Here's what VS looks like if I just open it using the Start menu icon:
http://schend.net/images/screenshots/vs_source_control_explorer.pngNote that it opens up the Source Control Explorer by default, with the appropriate UI elements. (BTW, what's an "Explorer?" It the little pane to the right is an "Explorer", but the main content of the window is also an "Explorer", WTF does that term even mean?)
Here's the same window after I open a Solution that just happens to have no saved open tabs:
http://schend.net/images/screenshots/vs_opened_solution_from_source_control.pngCan you tell the difference? Other than the Source Control Explorer window flashing, there's *nothing* in the UI to indicate that I now have an open Solution. The Solution Explorer didn't appear, nor did the Toolbox or Properties Explorer. The only difference, as far as I can work out, is that the File menu activated Close Project.
Now if I manually go and show the Solution Explorer, then it'll have all the Solution files in it and all will be well. But why should I have to manually show it even single time?
This might be a bug, but VS is working off such a complicated UI metaphor that I have no way of telling what's a bug or not. What your team really needs to do is simplify the metaphor to something you can explain in less than a paragraph without referring to a competing project
:) -
Re:Other performance gains
You should pop me off an email or blog comment, so we could hash through this.
Now that I'm trying it on my work machine, it's actually behaving closer to what you describe. (At least if I'm reading you right, I've never used Eclipse, so I really have no clue at all what a "perspective" is. And VS certainly doesn't seem to have anything that tries to explain that metaphor.)
In any case, starting with a computer with no VS running, here's what VS looks like when I open it by double-clicking a
.js file:
http://schend.net/images/screenshots/vs_opened_js_file.pngContrary to what happens on my home computer (where I wrote the last post), if I then double-click a Solution, the Solution will get its own window completely separate from the
.js window and with the correct UI elements visible. That's good-- just give the JS window a different icon, so I can tell it apart easier, and I'd be happy.TFS, however, doens't behave the same way. Here's what VS looks like if I just open it using the Start menu icon:
http://schend.net/images/screenshots/vs_source_control_explorer.pngNote that it opens up the Source Control Explorer by default, with the appropriate UI elements. (BTW, what's an "Explorer?" It the little pane to the right is an "Explorer", but the main content of the window is also an "Explorer", WTF does that term even mean?)
Here's the same window after I open a Solution that just happens to have no saved open tabs:
http://schend.net/images/screenshots/vs_opened_solution_from_source_control.pngCan you tell the difference? Other than the Source Control Explorer window flashing, there's *nothing* in the UI to indicate that I now have an open Solution. The Solution Explorer didn't appear, nor did the Toolbox or Properties Explorer. The only difference, as far as I can work out, is that the File menu activated Close Project.
Now if I manually go and show the Solution Explorer, then it'll have all the Solution files in it and all will be well. But why should I have to manually show it even single time?
This might be a bug, but VS is working off such a complicated UI metaphor that I have no way of telling what's a bug or not. What your team really needs to do is simplify the metaphor to something you can explain in less than a paragraph without referring to a competing project
:) -
Re:Other performance gains
By "bug" do you mean any inconsistency with stock UI controls?
An inconsistency is otherwise known as a "bug," yes.
I really wouldn't go so far as to call it that, because it really is the norm on Windows.
Yes, there are many buggy apps on Windows. Nobody ever claimed Windows apps were bug-free.
In fact, many Microsoft applications don't use stock controls themselves - Office doesn't, for example.
Office writes their own widgets, but (as far as I can work out) they behave 100% identically to the OS-standard widgets. Therefore, they aren't buggy. (Usually, the only difference is that Office adds their own theming.) Now, that said, there very could well be a case where the Office widget works differently, and then, yes, it would be a bug. Nobody ever claimed Office was bug-free.
Huge parts of VS2010 were rewritten in WPF, too (and it doesn't even try to look native anymore, even though it could - rather, it has its own distinct theme).
Yeah, and I think that's a huge mistake. When a programmer who is a bad UI designer doesn't know how to implement something, what's he going to do? Find a similar problem and see how VS solved it... and most of the time, VS gets it wrong. This is a huge problem, and leads to what you pointed out previously, about buggy Windows apps. (Oh, and same applies to Office.)
It's obvious if you work with Microsoft products that VS and SQL Server, for some reason, get little-to-none usability testing, as opposed to virtually everything else Microsoft creates. Why is this? Maybe Microsoft perceives that it's not a problem if "pro" apps are hard-to-use? I dunno. Like I said, I think it's a huge mistake.
SQL Server is actually even worse than VS. Even it's installer is basically equal parts confusion, meaningless buzzwords, and bugs. There's no reason a database package should be hard-to-use.
In any case, try Psi - that one is a Qt4 application that tries to look native. I'm curious as to what abnormalities you can quickly find in that.
The *screenshot* on the webpage has a wrong down-arrow control. I didn't even need to download the program.
It looks like they hacked off the end of a scrollbar and tinted it blue. Hell, I can't even really tell what widget it's supposed to be... is that a combo box arrow that somehow got detached from the rest of the box? The combo box arrow would at least look correct: http://schend.net/images/screenshots/combo_box_arrow.png
With something like that, I have absolutely no clue how to interact with it. I can assume that clicking it causes something to appear below it, but what is that something? A menu? A combo box? Who knows!
Is that seriously the best example you have? I'm starting to form a theory that most programmers have no eye whatsoever for detail... you're kind of confirming my suspicions.
-
Re:SixthSense
In the Sean Connery "classic" Zardoz, the far-future computer "Tabernacle" communicated with people via projectors from crystal rings: http://schend.net/images/movies/zardoz_tabernacle.png
I always thought that was a pretty damned nifty interface to a computer.
-
Re:Some good points in there
Random examples:
Just recently Slashdot covered a new open source FPS game. It's main window looks like this: http://schend.net/images/screenshots/alien_arena.png I can't even enumerate the hundreds of things wrong with just that one window.
Poor example. The game itself is not open source; the engine is. The engine is open source because it's based on Quake II's source code, which is where that menu comes from. Alien Arena, as a game, is freeware.
Look at Nexuiz (which IS OS) and its menu for an easy counter-example. Very streamlined and efficient. -
Re:Some good points in there
There's a little more to it than that.
It's not just that the projects are started and nursed along by people who can code, but they're started and nursed along by people who can code and also:
1) Don't know the purpose of a GUI
2) Don't understand the value of a GUIThere are tons of techniques that can be used, even by a programmer, to ensure that their program is more usable than the competition.
At the most basic level, they can follow all the UI standards of the OS/DE in which they're planning to run-- that one's simple, but it's completely missed by a lot of projects. If your program is running in Windows, and your font isn't rendered with ClearType-- it's a usability bug! Fix it! If you're running in OS X and pressing the down arrow on the bottommost line of text results in a beep instead of moving the insertion point to the end of the line-- it's a usability bug! Fix it! (And a very frequent one, since a lot of OS X programmers come from the Windows world now.) If you're not following all the standards of the OS you're running in, there's your starting point.
Secondly, every time you code something with a GUI, do a hallway usability test. This consists of grabbing someone walking by in the hall, and asking them to perform whatever task your application is designed to do using the new GUI you just wrote. The less that person knows about programming, the better-- you want normal users, not power users. The point isn't to assign a simple "pass/fail" to the UI, but to get their comments and feedback. Do one of those a day, and you'll hammer out 80% of the usability flaws before the product is even released. (Of course, this involves talking to other human beings, sometimes even *gasp* girls!, so I guess that's why it doesn't get done.)
Thirdly, understand the GUI. Discoverability, most importantly. Emphasizing the use of spatial memory, which the vast majority of non-geeks are better at than rote memorization. Understand how the basic widgets work, and why they work that way. (When you understand why widgets work the way they do, you'll hopefully have talked yourself out of "just write your own!" Writing a menu or listbox is *hard*. Writing an open dialog is *incredibly hard*.) Be able to answer the counter-intuitive question: "what five places on the screen can the user put the cursor on the quickest?" and learn why Macintosh menus are stuck to the top of the screen. Understand Mac Classic, which got closer than any other GUI to perfection. (IMO, of course.
;)There's no reason any programmer can't do these things. They just don't want to. That's a whole different article, though, going way back to the woefully-obsolete "high priesthood of technology" attitude.
Random examples:
Just recently Slashdot covered a new open source FPS game. It's main window looks like this: http://schend.net/images/screenshots/alien_arena.png I can't even enumerate the hundreds of things wrong with just that one window. That the developers thought that UI was "good enough" to craft a *release* around... I don't even know how to reply to that.
Awhile back, I filed a bug against Notepad++ (a highly recommended-to-me text editor for Windows) because their menus didn't work. Their DROP DOWN MENUS. The ones attached to the top of the window. One of the most basic elements of a GUI, one that's been perfected for 20 years, and they don't work!! Again, I have absolutely no words for that.
-
Re:Anti-trust?
The great part was the first Microsoft engineer who saw it, and declared that it was impossible for SSMS to open windows off-screen. He didn't even try it!
http://schend.net/images/screenshots/offscreen_ssms_window.png (the image I submitted after the bug was declared "impossible")
-
Re:Just block IE from your site.
Your site doesn't work in Firefox, either: http://schend.net/images/screenshots/treatvist_com.png You're probably in violation of Google's terms of use by obscuring their ad block, although I'm not 100% certain on that.
And the usability of it is GODAWFUL. Who decided it was a good idea to randomly swap copy on your homepage, thus moving its links all over the fucking place? "Oh that article looks interesting, let's click!
... Missed. Try again, click! ... Missed."In short, maybe you shouldn't be such a snob about IE until you get your site working on at least *one* browser.
-
Re:First Post!
Yeah, but wouldn't it be nice if we didn't *have* to go to the comments for the (almost inevitable) corrections to the story? Wouldn't it be great if the Slashdot editors would actually, you know, update the articles based on the corrections provided by the first few commentators? Or even pull ridiculous stories the instant they realized how ridiculous they were?
Wouldn't it be great if the editors of this site were tech-savvy enough to reject stories like this one: http://tech.slashdot.org/article.pl?sid=09/02/16/2259257 out-of-hand?
I know, I'm living in a fantasy world. They can't even fix the "Reply" button when posting a comment. In 6 months:
http://sourceforge.net/tracker/?func=detail&aid=2159787&group_id=4421&atid=104421
http://schend.net/images/screenshots/slashdot/reply_button_with_growths.pngBut it would be nice.
-
Re:Suggestion for preservation of info on that MUD
I don't want to support sites that have horrible usability and haven't improved in 15 years. I hate web developers getting support for having a shitty product doing NOTHING to improve, which is exactly what SourceForge has been doing in all that time. (Compare the typical SF project page with a typical Trax project page, and you'll realize just how shitty it is.)
Of course, I'm a hypocrite, because I post to Slashdot. But at least Slashdot is *trying* to improve in a completely half-assed and wrong way. Half the time I go to SF, all I see is this:
http://schend.net/images/screenshots/slashdot/sourceforge_blank_window.png
http://schend.net/images/screenshots/slashdot/sourceforge_wish_it_was_a_blank_window.pngThe fucking site doesn't even WORK.
-
Re:Suggestion for preservation of info on that MUD
I don't want to support sites that have horrible usability and haven't improved in 15 years. I hate web developers getting support for having a shitty product doing NOTHING to improve, which is exactly what SourceForge has been doing in all that time. (Compare the typical SF project page with a typical Trax project page, and you'll realize just how shitty it is.)
Of course, I'm a hypocrite, because I post to Slashdot. But at least Slashdot is *trying* to improve in a completely half-assed and wrong way. Half the time I go to SF, all I see is this:
http://schend.net/images/screenshots/slashdot/sourceforge_blank_window.png
http://schend.net/images/screenshots/slashdot/sourceforge_wish_it_was_a_blank_window.pngThe fucking site doesn't even WORK.
-
Re:Red header
A changelog would imply they're following some kind of "design" or "plan" when they're clearly not. They make changes to people using the "version 1 discussion system" obviously intended for users of the "version 2 discussion system", like the Users page. They randomly break things, then half-repair them. i.e. listing the wrong content (submitted articles), then 'fixing' it by showing the intended content (recently posted comments) wrongly (incorrect scores).
Oh, and they're owned by the company that runs SourceForge, the site that frequently looks like this: http://schend.net/images/screenshots/slashdot/sourceforge_blank_window.png or this: http://schend.net/images/screenshots/slashdot/sourceforge_wish_it_was_a_blank_window.png
Slashdot seems to be a classic DailyWTF-esque "Developmestuction" environment: http://thedailywtf.com/Articles/The_Developmestuction_Environment.aspx
There isn't anybody at the entire Sourceforge/Slashdot corporate entity I'd call a "web developer".
-
Re:Red header
A changelog would imply they're following some kind of "design" or "plan" when they're clearly not. They make changes to people using the "version 1 discussion system" obviously intended for users of the "version 2 discussion system", like the Users page. They randomly break things, then half-repair them. i.e. listing the wrong content (submitted articles), then 'fixing' it by showing the intended content (recently posted comments) wrongly (incorrect scores).
Oh, and they're owned by the company that runs SourceForge, the site that frequently looks like this: http://schend.net/images/screenshots/slashdot/sourceforge_blank_window.png or this: http://schend.net/images/screenshots/slashdot/sourceforge_wish_it_was_a_blank_window.png
Slashdot seems to be a classic DailyWTF-esque "Developmestuction" environment: http://thedailywtf.com/Articles/The_Developmestuction_Environment.aspx
There isn't anybody at the entire Sourceforge/Slashdot corporate entity I'd call a "web developer".
-
Re:STOP MESSING WITH SLASHDOT
The User page is still bad, and it still makes the simple task of "hey, have my recent posts been moderated?" about 20 times more ugly and annoying than before.
http://schend.net/images/screenshots/slashdot/slashdot_user_template.png
There's the screenshot I put in with the SourceForge bug report related to the user template change. They never read or fix any of the bugs I submit, but there you go if you're interested.
-
Re:No, Slashdot, No!!!
Take a look at all the screenshots I've submitted as Slashdot bugs over the last year or so:
http://schend.net/images/index.php?path=screenshots%2Fslashdot/
(Here's the current one for the User page: http://schend.net/images/screenshots/slashdot/slashdot_user_template.png )
Needless-to-say, none of my bugs have ever been resolved. In fact, most of the time they're not even read. Think about it: someone actually received cash-money in exchange for making that horrible template. It makes you want to weep.
-
Re:No, Slashdot, No!!!
Take a look at all the screenshots I've submitted as Slashdot bugs over the last year or so:
http://schend.net/images/index.php?path=screenshots%2Fslashdot/
(Here's the current one for the User page: http://schend.net/images/screenshots/slashdot/slashdot_user_template.png )
Needless-to-say, none of my bugs have ever been resolved. In fact, most of the time they're not even read. Think about it: someone actually received cash-money in exchange for making that horrible template. It makes you want to weep.
-
Re:Let's look at Inkscape:
A couple things:
1) If Inkscape is so good, it's version number should at least be 1.0. You can't convince people to download and use pre-alpha software on a daily basis, no matter how 'great' it is. If 0.46 is an accurate description of its version, then it shouldn't be getting press. (It'll get press, people will download it, it'll be a buggy POS, they'll hate the name "Inkscape" for the rest of their days-- bad idea!)
Inkscape, as a vector application, is simply a better choice for a lot of graphic tasks for which clueless people still try to use GIMP or Photoshop. Just look at the "can it draw circles" thread in this discussion!
2) Inkscape is a better choice for graphic tasks that involve vectors. It's not for other graphic tasks. Vector tasks (like making company logos, for example, or program icons) are simply not as common a use-case as bitmap manipulation (photo cleaning.) Yes, I agree that anybody using GIMP or Photoshop for a flow-chart is using the wrong tool. Then again, Inkscape isn't the right tool for that, either-- they'd be better served by something like Visio.
In short, don't assume people are idiots because they talk about GIMP/Photoshop more than vector programs. It's more likely they just use bitmap tools more than they use vector tools.
P.S. Last time I used Inkscape, on X11 on Macintosh, it wasn't even capable of sorting the File->Open dialog in alphabetical order. I reported the bug, and I'd link to it-- except it appears they deleted it from their bug tracker. Classy. Here's a screenshot:
http://schend.net/images/screenshots/alphabetical_disorder.png -
Re:small dual screens is kind of a dumb idea
Zardoz!
http://schend.net/images/movies/zardoz_tabernacle.png
In the (terrible) movie, the mainframe computer that ran the "vortex" was named The Tabernacle, and its interface was small crystaline rings incorporating a projector. To see Tabernacle's output, you just aimed your ring at a nearby flat surface. (Or someone's forehead in a couple scenes.)
Terrible movie, but decent sci-fi prediction. -
Re:Macs are Over-rated
What do you mean a network that doesn't exist? An NFS or CIFS mount? I've never had these problems, but I don't have any remote file shares mounted at home either.
I worded it poorly. What I mean is that my laptop was connected to a share at work, available on that particular network but on no others. I sleep the laptop, then take it onto my commuter train with the sometimes-unreliable network connection. The first time Finder tries to do anything with the fileshare, it freezes solid for several minutes.
I don't know or care what acronym the network drive was using. I just want my computer to work, and Apple's software foiled that.
The only problems I've had with .Mac are related to syncing, but I can imagine how a slow link could possibly lead to UI delays.
It freezes the Finder the first time you touch a .Mac volume on an unreliable network connection. I think it's trying to retrieve a catalog of what icons it should be showing, but I don't know for sure. All I know is, it's doesn't fucking work. It also has huge, glaring syncing errors... like the time it decreed that all 10,000+ files on my .Mac volume had "changed" because either their server's clock, or my desktop clock, had gotten off for a minute, then asked me to resync Every Goddamned File individually.
Here's a few screenshots I took:
http://schend.net/images/blog_materials/iDisk%20Sucks%20-%20deleting%20for%2012%20solid%20hours%20only%20half%20done.png
This screenshot was taken AFTER the delete operation had been run for a solid 12 hours and hadn't yet finished
http://schend.net/images/blog_materials/iDisk%20sucks%20-%20deleting%20negative%20files.png
The lovely "-133 files remaining" dialog
http://schend.net/images/blog_materials/idisk%20sucks%20-%20sync%20error.png .Mac stopping my system from logging out by freezing. Typically, I'd wake up to find out that, because of this error, my computer had spent the entire night turned on when I was trying to turn it off.
And, of course, there was the whole ".Mac will be free forever! Now that all your data's on it, we're charging $100 for it, suckers" thing.
Out of curiosity, what have you tried to troubleshoot these issues?
Nothing. Debugging Apple's issues is their problem, not mine. I just moved to Windows, which can cope with fileshares in a sane manner.
And from my experience, as well, they're both about equally common on both OSes.
"Yah, that was sarcasm." Is it really necessary for me to say I was being sarcastic? Of course they are nearly the same thing, what's the point? When someone's computer locks up, it's locked up. BSODs aren't the butt of so many jokes because they are BLUE, but because they were so common, particularly in Win95-98. No one needs to be told a kernel panic is the same as a BSOD to understand how frustrating it is.
Look, if you want to communicate clearly, don't type something obviously sarcastic then say it's sarcastic. Since sarcasm cancels out sarcasm, that's confusing as hell.
What are you talking about? The Dock works FINE for me! I'm really having a hard time understanding your frustration here. I really like my dock, and I have quite a bit of experience with many different OS interfaces. I don't know what to say to you. It's not the end-all-be-all UI, but what the heck is so wrong with it?
I told you to Google for it, but you didn't. Here's Tog's take:
http://www.asktog.com/columns/044top10docksucks.html
Ars Technica has had great coverage of this issue since OS -
Re:Macs are Over-rated
What do you mean a network that doesn't exist? An NFS or CIFS mount? I've never had these problems, but I don't have any remote file shares mounted at home either.
I worded it poorly. What I mean is that my laptop was connected to a share at work, available on that particular network but on no others. I sleep the laptop, then take it onto my commuter train with the sometimes-unreliable network connection. The first time Finder tries to do anything with the fileshare, it freezes solid for several minutes.
I don't know or care what acronym the network drive was using. I just want my computer to work, and Apple's software foiled that.
The only problems I've had with .Mac are related to syncing, but I can imagine how a slow link could possibly lead to UI delays.
It freezes the Finder the first time you touch a .Mac volume on an unreliable network connection. I think it's trying to retrieve a catalog of what icons it should be showing, but I don't know for sure. All I know is, it's doesn't fucking work. It also has huge, glaring syncing errors... like the time it decreed that all 10,000+ files on my .Mac volume had "changed" because either their server's clock, or my desktop clock, had gotten off for a minute, then asked me to resync Every Goddamned File individually.
Here's a few screenshots I took:
http://schend.net/images/blog_materials/iDisk%20Sucks%20-%20deleting%20for%2012%20solid%20hours%20only%20half%20done.png
This screenshot was taken AFTER the delete operation had been run for a solid 12 hours and hadn't yet finished
http://schend.net/images/blog_materials/iDisk%20sucks%20-%20deleting%20negative%20files.png
The lovely "-133 files remaining" dialog
http://schend.net/images/blog_materials/idisk%20sucks%20-%20sync%20error.png .Mac stopping my system from logging out by freezing. Typically, I'd wake up to find out that, because of this error, my computer had spent the entire night turned on when I was trying to turn it off.
And, of course, there was the whole ".Mac will be free forever! Now that all your data's on it, we're charging $100 for it, suckers" thing.
Out of curiosity, what have you tried to troubleshoot these issues?
Nothing. Debugging Apple's issues is their problem, not mine. I just moved to Windows, which can cope with fileshares in a sane manner.
And from my experience, as well, they're both about equally common on both OSes.
"Yah, that was sarcasm." Is it really necessary for me to say I was being sarcastic? Of course they are nearly the same thing, what's the point? When someone's computer locks up, it's locked up. BSODs aren't the butt of so many jokes because they are BLUE, but because they were so common, particularly in Win95-98. No one needs to be told a kernel panic is the same as a BSOD to understand how frustrating it is.
Look, if you want to communicate clearly, don't type something obviously sarcastic then say it's sarcastic. Since sarcasm cancels out sarcasm, that's confusing as hell.
What are you talking about? The Dock works FINE for me! I'm really having a hard time understanding your frustration here. I really like my dock, and I have quite a bit of experience with many different OS interfaces. I don't know what to say to you. It's not the end-all-be-all UI, but what the heck is so wrong with it?
I told you to Google for it, but you didn't. Here's Tog's take:
http://www.asktog.com/columns/044top10docksucks.html
Ars Technica has had great coverage of this issue since OS -
Re:Macs are Over-rated
What do you mean a network that doesn't exist? An NFS or CIFS mount? I've never had these problems, but I don't have any remote file shares mounted at home either.
I worded it poorly. What I mean is that my laptop was connected to a share at work, available on that particular network but on no others. I sleep the laptop, then take it onto my commuter train with the sometimes-unreliable network connection. The first time Finder tries to do anything with the fileshare, it freezes solid for several minutes.
I don't know or care what acronym the network drive was using. I just want my computer to work, and Apple's software foiled that.
The only problems I've had with .Mac are related to syncing, but I can imagine how a slow link could possibly lead to UI delays.
It freezes the Finder the first time you touch a .Mac volume on an unreliable network connection. I think it's trying to retrieve a catalog of what icons it should be showing, but I don't know for sure. All I know is, it's doesn't fucking work. It also has huge, glaring syncing errors... like the time it decreed that all 10,000+ files on my .Mac volume had "changed" because either their server's clock, or my desktop clock, had gotten off for a minute, then asked me to resync Every Goddamned File individually.
Here's a few screenshots I took:
http://schend.net/images/blog_materials/iDisk%20Sucks%20-%20deleting%20for%2012%20solid%20hours%20only%20half%20done.png
This screenshot was taken AFTER the delete operation had been run for a solid 12 hours and hadn't yet finished
http://schend.net/images/blog_materials/iDisk%20sucks%20-%20deleting%20negative%20files.png
The lovely "-133 files remaining" dialog
http://schend.net/images/blog_materials/idisk%20sucks%20-%20sync%20error.png .Mac stopping my system from logging out by freezing. Typically, I'd wake up to find out that, because of this error, my computer had spent the entire night turned on when I was trying to turn it off.
And, of course, there was the whole ".Mac will be free forever! Now that all your data's on it, we're charging $100 for it, suckers" thing.
Out of curiosity, what have you tried to troubleshoot these issues?
Nothing. Debugging Apple's issues is their problem, not mine. I just moved to Windows, which can cope with fileshares in a sane manner.
And from my experience, as well, they're both about equally common on both OSes.
"Yah, that was sarcasm." Is it really necessary for me to say I was being sarcastic? Of course they are nearly the same thing, what's the point? When someone's computer locks up, it's locked up. BSODs aren't the butt of so many jokes because they are BLUE, but because they were so common, particularly in Win95-98. No one needs to be told a kernel panic is the same as a BSOD to understand how frustrating it is.
Look, if you want to communicate clearly, don't type something obviously sarcastic then say it's sarcastic. Since sarcasm cancels out sarcasm, that's confusing as hell.
What are you talking about? The Dock works FINE for me! I'm really having a hard time understanding your frustration here. I really like my dock, and I have quite a bit of experience with many different OS interfaces. I don't know what to say to you. It's not the end-all-be-all UI, but what the heck is so wrong with it?
I told you to Google for it, but you didn't. Here's Tog's take:
http://www.asktog.com/columns/044top10docksucks.html
Ars Technica has had great coverage of this issue since OS -
Nope, right.
No, you can't change people with software.
Do you know why Lotus 1-2-3 lost out to Excel? Because while Lotus was busy adding in all kinds of advanced mathematical and financial functions, alternate layouts, and basically tons of things for the super-advanced Lotus user, Microsoft decided to go a different route and actually ask people what they used Excel for.
The answer? People used Excel for making lists. So instead of adding all the difficult, prone to bugginess, and hard-to-user features that Lotus was working on, Excel added features to make creating lists easier. Autofill, for instance, and Auto-Format.
Because Microsoft learned this lesson, people use Excel every day (both for lists, and the advanced stuff 1-2-3 was doing), and Lotus 1-2-3 is in the history books.
The instant the open source community figures out that THE USER IS KING, the sooner open source will become popular with the general public.
1) A usability problem is a bug. Period.
2) It doesn't matter whether a user is using your program for the "right" purpose (doing large complex spreadsheet), or for the "wrong" purpose (creating lists, as a mini-database), it should work for them. I can't tell you how many times I've asked "what's why can't open source product A do X?" only to get the reply "you shouldn't be doing X." (Most recently, when I asked about a open source alternative to Microsoft Project.)
Since I'm on the topic, here are some recent usability bugs I've entered for a couple open source projects, all of which have been completely ignored:
http://sourceforge.net/tracker/index.php?func=detail&aid=1865630&group_id=95717&atid=612382
http://sourceforge.net/tracker/index.php?func=detail&aid=1865624&group_id=95717&atid=612382
http://bugzilla.gnome.org/show_bug.cgi?id=391461
There's a long way to go. That Inkscape bug (the SourceForge "artifact" has been made private, whatever the fuck an "artifact" is) is a good example of a huge "wow this computer's stupid" bug that has been around for ages.
http://schend.net/images/screenshots/alphabetical_disorder.png
Cheers. -
Panzer Dragoon Orta
Admittedly, I haven't played any of the games in this series except the Xbox version, Panzer Dragoon Orta. Despite being too short, it's a great, great, tremendously good game. Best graphics of any Xbox launch title, ingenious, easy-to-learn gameplay, interesting sci-fi setting. I admit it, I cried at the end. Plus it starred the craziest insect-dragon-bone-thing ever:
http://schend.net/images/games/dragon.jpg -
Re:Maybe KDE & Gnome Folk Will Read...
On my Mac, Finder, Address Book, and iCal are brushed metal, whereas Mail and iTunes are uniform grey. Preview is different again. What the hell?!? Over the last 3 years, MacOS has become _less_ consistent, whereas Gnome has become much more so.
Duh. That's the entire point of this story... independent Apple fans are attempting to document Apple's horrible slide into UI mediocrity so third-party apps can at least be consistent with the system, since Apple doesn't feel the need to actually document any of these stupid themes on their own. This is the kind of thing that makes people remember the unstable, quirky Mac OS 7 with tears forming in their eyes... Apple used to give half-a-shit, they don't anymore.
I'm not saying Gnome is perfect (I haven't used KDE much for a while) - I doubt anyone would say that - but it's certainly not as inferior as you're making out.
Welcome to my favorite screenshots:
http://schend.net/images/screenshots/gaim_2_is_ugl y.png
http://schend.net/images/screenshots/gaim_2_is_bug gy.png
GAIM is a GNOME app, is it not? It's so hideous, it makes Microsoft's Luna theme look beautiful by comparison. You seriously think that competes even slightly with what Apple's putting out? Even the crummy stuff Apple's put out recently?
(BTW, your example about changing colors is particularly apt, since you can see that GNOME apps on Windows completely and utterly ignore the Windows theme and do their own thing.) -
Re:Maybe KDE & Gnome Folk Will Read...
On my Mac, Finder, Address Book, and iCal are brushed metal, whereas Mail and iTunes are uniform grey. Preview is different again. What the hell?!? Over the last 3 years, MacOS has become _less_ consistent, whereas Gnome has become much more so.
Duh. That's the entire point of this story... independent Apple fans are attempting to document Apple's horrible slide into UI mediocrity so third-party apps can at least be consistent with the system, since Apple doesn't feel the need to actually document any of these stupid themes on their own. This is the kind of thing that makes people remember the unstable, quirky Mac OS 7 with tears forming in their eyes... Apple used to give half-a-shit, they don't anymore.
I'm not saying Gnome is perfect (I haven't used KDE much for a while) - I doubt anyone would say that - but it's certainly not as inferior as you're making out.
Welcome to my favorite screenshots:
http://schend.net/images/screenshots/gaim_2_is_ugl y.png
http://schend.net/images/screenshots/gaim_2_is_bug gy.png
GAIM is a GNOME app, is it not? It's so hideous, it makes Microsoft's Luna theme look beautiful by comparison. You seriously think that competes even slightly with what Apple's putting out? Even the crummy stuff Apple's put out recently?
(BTW, your example about changing colors is particularly apt, since you can see that GNOME apps on Windows completely and utterly ignore the Windows theme and do their own thing.) -
Re:Popularization
If it looks anything like what the beta looked like, then yes I agree whole-heartedly.
http://schend.net/images/screenshots/gaim_2_is_ugl y.png
http://schend.net/images/screenshots/gaim_2_is_bug gy.png
I had a terrible experience with it. -
Re:Popularization
If it looks anything like what the beta looked like, then yes I agree whole-heartedly.
http://schend.net/images/screenshots/gaim_2_is_ugl y.png
http://schend.net/images/screenshots/gaim_2_is_bug gy.png
I had a terrible experience with it. -
Constantly Surprised at the Quality of Slashdot
I've been reading this site for years, and yet I'm constantly impressed by the quality exhibited.
For instance, in a story about how resistant the Internet is to attack, the editors apparently decided to demonstrate what a possible attack might look like.
Take a look!
Bravo! -
Re:Can't wait to see 2.0.0
It couldn't be any worse than the current version: ugly and buggy.
I'd give my right ankle for a port of Adium to Windows, or any other platform than OS X for that matter. It's the only multi-protocol IM client that doesn't suck. (Well, it still sucks for file transfers... but it doesn't suck nearly as much as the others.)