Showing posts with label Digg. Show all posts
Showing posts with label Digg. Show all posts

Tuesday, January 23, 2007

The operating system holy wars are getting ridiculous

Why does there have to be mudslinging in the world of computers? I mean, computers are basically tools. Your hammer and nails don't determine your identity, so why should your computer? Your brand of hammer in the long run is irrelevant. But when you get into operating systems, it's off to the world of religious wars!

"You use Windows? You're dumb/unenlightened/very patient."

"You use a Macintosh? You're a simpleton/enlightened/snobby."

"You use Linux? You're a genius/square/weirdo."

Seriously, am I the only one that believes that an argument like that is reserved for elementary school kids or children under ten? You are not your computer. You know why tech evangelists get on my nerves? Because the underlying message subtly says that the evangelist is right, and if you don't agree, you're not. Never mind if you have chosen your computer platform based on merit - such as usability and features. To the evangelist, it all comes down to whether or not you agree.

It goes back and forth on Digg. One day is ruled by the Linux evangelists, the next the Mac people, and the day after that the Windows disciples. Obviously the evangelists don't represent the majority of each user group. If that were true, I would opt not to read the Apple and Linux sections.

It boggles my mind how people can stay obsessed about this stuff. Each OS has its own advantages. Can't we at least establish that? You know what? I'm rambling. I have no idea where I'm going. But let me leave you with this: If you can't accept other people's opinions, get off the Internet.

Tuesday, January 02, 2007

Digg needs a section for blogs


Digg is, of course, the popular news site - stories chosen by the masses ad promoted by the masses. The site has been lauded and hated alike, and Diggers are vocal participants in the phenomena known as Web 2.0. Digg is the most democratic of news aggregators, and Keven Rose and company have been covered by periodicals such as Time and The New York Times. The most important news is daily brought to the front page by the people who matter the most: The users.

But increasingly, Digg's democracy has discovered entropy: Bugs in the system, glitches in reality. Occasionally, Digg doesn't work the way it's supposed to. More and more, people are submitting stories about blog entries - Gasp! The horror! Digg is being invaded by blogs!

Seriously, many blogs don't constitute news. The problem with the Digg website is that there's no section for blogs: News blogs have to go in the Political Opinion section, and Linux blogs have to go in the Linux section - even though neither are categorically newsworthy. Then there are the rumor blogs - you know, the ones that say, "G.W.Bush executed Saddam Hussein so Hussein couldn't testify to Bush's plot to take revenge for his father," or, "The Linux kernel was written by Steve Wozniak, not Linus Torvalds!"

The Digg team has recently introduced new categories to the website: Podcasts and Videos. Wouldn't it make sense to then add a Blogs section, as well? Many blogs simply aren't about news, as the News category might suggest. Separate the wheat from the chaff, and everyone will be happy; the blogosphere won't bother the news junkies, and vice versa. The Blogs section could even mirror the News section and all its categories, to satisfy the news blog junkies.

This would eliminate complaints about the presences of blogs on the front page of the News section. The new Videos section has worked very well thus far: There have been virtually no videos submitted to the News section since, and everyone is satisfied. Why can't the same be done for blogs?

Monday, January 01, 2007

One Apple fanboy in particular

As a devoted Digger through and through, as I have been for some time now, I am fascinated by one particular character from a cast crazier than Gene Wilder, Zero Mostel, and Richard Pryor all put together: Daniel Eran Dilger. The man seems to hate Microsoft for no apparent reason, other than that it's more successful than Apple - the jewel in Dilger's eye.

I first heard of Dilger when hundreds of Diggers in September Dugg a story about how recently announced iTV would change television. My first reaction was, Huh? Would a box with mysterious features really conquer the tube, which we all know to be the gospel? I wasn't very impressed by his article - no more so than I was with Mr. Dilger, who goes by Daniel Eran on his blog. (Eran is his middle name.) For some reason, one guy was calling himself a magazine. (Does that mean I'm a magazine, too? I have a blog!)

What astounded me was Dilger's absolute awe in able Apple's apposition. To Mr. Dilger, Apple is the gospel, the ultimate revelation. Dilger's series of essays on the iTV were speculative at best and unfounded at worst. To be fair, plenty of his other essays have some semblance of fact or solid base, but I did not see anything decent in my first impression. Practically every one of his entries mentions Microsoft - usually in ridicule. While the company undoubtedly deserves a number of lashes, Mr. Dilger seems to attack Microsoft for doing anything at all. It's sort of like beating a dead cow. He's even criticized Microsoft for building the Zune with a screen bigger than the iPod's. Mr. Dilger is at war with Microsoft, or so it seems.

One of his more questionable claims is that success of the Xbox 360 is a myth - an illusion of football players, guns, magic, and sorcery. Apparently selling 8 million units in one year is disappointing. The PS2 sold more units: Three million more! But Dilger doesn't quite seem to understand the console market: Note that last year, Sony sold 20 million PS2 units worldwide. (I'm using his source, from PC vs. Console.) With the arrival of the PS3, is has all but looked like the end of the PS2's life cycle: The Xbox 360 has been on the market for one year, and the PS2 six. The PS2 is an established brand with tons of games. The Xbox 360? One year, definitely not as many games. The reputation of a six-year-old console will bulldoze a newbie. In 2007, we'll see a lot more sales of the Xbox 360, with the arrival of Xbox 360 exclusives and other big wig games. Year two will be big for the Xbox 360, and the next three years will see plenty of Xbox 360 sales. Video game consoles have life cycles of five to six years: The PS2 came out in 2000, and the PS3 2006; the Xbox came out in 2001, and the Xbox 360 2005 (an unusually short lifespan of four years). Also, is it just me, or did Dilger compare a game console to a portable music player? That really doesn't make much sense at all.

But aside from the content, I tend to view Dilger negatively, because it seems someone has been gaming Digg. A Digger even compiled a list of likely fake users, controlled by a real person to artificially inflate the Digg count for Dilger articles. Furthermore, at some point in late November or early December, the Digg team blocked stories originating from RouglyDrafted.com. Dilger cried foul and for a short time appended each of his blog entries with a short, sordid tale of special interest groups like Microsoft paying Digg to censor Mr. Dilger. Excuse me if a claim like that doesn't raise his credibility. (All those appendices are gone, but they were amusing for a week or two.) Daniel Eran then moved to NewsTrust.net. He subsequently started reviewing his own essays, giving them favorable ratings without fail. Integrity, shmegrity. That sure puts to rest any doubts that at one point or another, Dilger was indeed Digging his own stories under different pseudonyms.

I don't like Daniel Dilger. I'm not fond of any fanboys, but Dilger takes the cake as the biggest Apple fanboy with the least amount of integrity. To my knowledge, Dilger has never admitted to Digging his own stories, but it seems pretty certain that he did it.

Friday, December 22, 2006

Some Linux users are just too good for me, I suppose

Thanks to Digg, I happened to stumble across this analysis of why Linux is not Windows, at the blog OneAndOneIs2, by Dominic Humphries. By all means, "Linux != Windows", the blog entry I am trying to dispel, is quite long. I didn't attempt this task on a whim, but I believe that "Linux != Windows" was very wrong for several different reasons, and as such I decided that I would use my blog to do what I like to do most when it comes to blogging, speak my mind. This blog entry is divided into sections, according to each "problem" that divides each component of the opinion I am refuting. This essay relies heavily on the original article, so I suggest you read that first. At any rate, I shall proceed.

Point 1. How is it impossible to expect Linux to be better than Windows and have the same features? Isn't that called an upgrade? Doesn't that imply that improvements have been made upon central concepts? Claiming that Linux cannot be like Windows and better than it is like claiming that Windows Vista could not possibly exist, because it's Windows XP, but better. Mr. Humphries is missing the point of Windows users who try Linux. Those users want an upgraded Windows; they're not looking for something exactly the same. If those users wanted an operating system that's exactly the same and Windows, why not choose Windows in the first place?

Firefox succeeded not because it was different, but because Firefox built off of IE and had better, upgraded features. Just look at FF2 and IE7: For the most part, the GUI is the same! You navigate to different websites by typing the URL into the navigation bar and press Enter or click Go; you navigate through your window/tab history by using the Backward and Forward tabs; you save websites by putting their paths in bookmarks. Is the Find function an ability that Firefox devs invented? Of course not! Its presence in the bottom of the browser is (you may disagree) and improvement, an upgrade! It's not superior because it's different; it's superior because it has better functionality! Better != different! Sites like OldVersion.com exist because changes to software made the new versions worse! Firefox's features, when IE6 was competing with Firefox, were better than those in IE because they were easier to use and faster to use! If Firefox changed the default language to Swahili, would that make it better than IE? But Mr. Humphries' reason, yes, because it's different. Again, if users were looking for a copy of IE, they would just use IE! I myself switched to Firefox, because I heard that Firefox had better features, not because it was different. Firefox was similar enough in use to IE that I had no trouble adapting to it.

Point 2. This section is quite misleading. It asks whether or not there's really any big difference in the differences in Linux distributions and then compares Linux to a car: If you can drive one car, you can drive them all!

But you see, the difference in choices is more complicated than that. When you want airbags in your car, you don't choose between "Baag," "Baglite," "Big Bag," or "Sfebag" type airbags, all of which do the same thing but conform to standards that ordinary (most) people won't understand. When you have lots of choices in interfaces, file managers, desktops, and even window managers, people who just want to use a computer will be confused when presented with a choice. If you have to explain all of the intricacies of an operating system to someone who just wants to get work done, chances are that person will give up and move to what he or she is used to - Windows XP, which comes in the consumer-friendly name differentiations of "Home" and "Professional." When your operating system has dozens, if not hundreds, of minute differentiations without any clear advantage in any, that is one example of too many choices. When you have so many choices for both underlying and trivial options, you have to do one of two things, or a combination: Differentiate, or consolidate. Give the user reasons to choose, not options; most people just want to get their work done! Give the people the means to the ends, not the means to the endless! The problem is that there are too many choices there they don't need to be.

Ah, and here we come to desktop Linux. Let me admit that I am an experienced Windows user, and I believe that Linux is not ready for the desktop. But remember, correlation does not equal causation. I have considered switching to Linux, as I've mentioned in my last blog entry. (I'm not going to rehash it, for the most part.) Mr. Humphries is ignoring the big reason that Linux is not ready for Dell and blaming the whole thing on Windows junkies. Honestly, if it was only our fault, why is Linux so slow in moving onto the computers of the masses? We're not getting in your way!

Or is it because of the work ethic involved: You might have to adjust Linux to get it working, and if you need help you have to go to some forum. That's just the problem: The masses want to use their computers, not work with them. I worked with MS-DOS and had no trouble using at after I learned the commands. I'm not rigid to one set of controls, and I have no doubt that a beginning computer user who works with Linux will have little trouble learning what buttons to press. But what if something isn't working? What if you can't find something? The average person doesn't even care about what the problem is! People just want to fix it and go - wham bam, thank you, ma'am. That leads me to...

Point 3a. I'm not panning forums. Forums are great. I've used a great many forums!

You're not going to endear many Linux switchers by telling them that they have to get used to tech support from a loose organization of volunteers. When I search 'Windows help' in Google, I get Microsoft's support site; when I search 'Linux help,' I not only get Linux Questions, but LinuxSelfHelp, Linux Online, linuxhelp.blogspot.com, linuxhelp.co.za, and JustLinux, just to name a few. These websites may be comprised of fine, fine people; I don't know. But what I do know is that with Windows, you know who to ask: The guys that make it. Coincidentally, the guys that made it also have a website for it! Linux is like Windows in that regard, ironically: The guys that made it also have a website for it - and thousands of people made it! The problem is that there is too much choice where there shouldn't be.

And is it just me, or is Mr. Humphries criticizing Windows users because most users only use software after it's stable? Sorry to rain on your parade, but that simply is not going to fly for most people, except for the most hardened Linux veterans or the peopel actually working on the program. Let me give you an example: Songbird. Songbird is at release version 0.2.1. It's barely usable. (I've tried it myself.) But when the media library fails to comprehend my Weird Al library because the metadata has quotation marks (among other random quirks), it's NOT ready for use. Should I apologize for expecting my programs to work when I run them? I run my programs to get something done, and I'm not about to compromise my productivity for "new" software. I have standards: I shouldn't need to fool around with software to get it to work. Only in the world of Linux is that expected!

Furthermore, Mr. Humphries criticizes Linux switchers for expecting their software to be polished to a grade as high as Windows. Remember that they "don't owe you anything?" For God's sake, Linux is competing against Windows! Like it or not, Linux is trying to compete in the same market in which Windows operates. They're trying to convert people to this OS, and they're complaining that people expect it to be good? That's their own damn fault! They shouldn't cry that it's impossible them you to deal with, because those Linux heads got themselves into it! They're trying to compete against an OS with 95% of the market share, and they expect to wow people by not providing comprehensive, easy service and telling users to find the answers for themselves? Some call me a waaaaaaaaaaaaaaaaaaaaahmbulance! I'm crying my eyes out that those poor Linux devs are overworked and paid nothing. Hey, they chose to do what they do; programming is not a task that can be performed by the unskilled, and managing programmers isn't, either. If you have a product to sell, the free market doesn't care about how much work you put into it: Only the quality of its mettle. Root, hog, or die.

Point 3b. It is in fact more elitist to say, "Everybody knows this," than, "Everybody ought to know this." According to Mr. Humphries, everyone who has never used Linux before is a novice. Let me build on that an offer a parable:

Imagine, if you will, a Beginning French class. None of the students before have ever taken French in their lives; they don't even know the alphabet or the diacritic marks. So one of the students raises his hand and asks about the alphabet. The teacher shrugs it off, replies that the alphabet is something everyone knows, and goes on.

In that example, it sure sounds like the teacher telling the student that he ought to know that would be the same thing as saying everybody knows that.

The difference is that telling someone that they ought to know something places emphasis on what is not learned and that it is in fact crucial. That phrases places emphasis on the fact, not the person. Would it be elitist for a French teacher to tell the students what they ought to know in order to prepare for the test?

By contrast, telling someone, "Everybody knows that!" puts the emphasis on the person. Saying that assumes that the person who is hearing it is a Have Not in a world of Haves. Claiming that everybody knows something - and you don't - puts you at a lower level. There's no emphasis on even learning what is unknown. If you don't know it, then you're sunk.

And now I get to talk about the Lego metaphor. It's completely wrong. When you download a distribution of Linux (especially a desktop distribution), you get an environment that is set up for you - just like a Windows installation. That's not like getting a Lego set at all! I honestly don't know of a right metaphor, but this one is completely irrational. If you're comparing Linux to Windows, then the only difference is that the Linux toy car comes with the tools to take it apart, build, find, or purchase extensions, and customize it how you like, while the Windows care comes with a paint set. I absolutely hated this section of "Linux != Windows". Linux doesn't come broken up into many different pieces. Would you really compare downloading programs to a Lego car? If so, then Windows would also be a Lego car! Besides, the focus of Linux should be the focus of any other operating system - providing a platform for getting things done. Emphasizing how much you can take apart only skims the purpose of an operating system's usefulness. What is the worth of Linux if its only purpose is to be taken apart and put back together again?

Just because you use open source software doesn't mean you want to open up the code and spill its guts. Though I may use Mozzila Thunderird, Mozilla Firefox, StepMania, and Foobar2000, I really don't care about how they work. Generally, software being open source is just an added bonus, not an important feature.

Point 4. This is just another attempt to brush off the users who simply want to get things done, by claiming that the software was created for a difference target audience.

Now, obviously there is nothing wrong with designing tools for programmers; I find no faults with developing an efficient IDE, for instance.

But when you don't tell the beginning users what is most efficient for them, that's your fault. Face it; people who just want to get work done just want to know how to do it in the quickest way possible. Even if you have just developed the most powerful text editor on Earth, there's no way you should advertise it to a person with the goal of expediency if it takes a few hours to learn. Chances are, Vi is one of those programs. It may certainly be an excellent program, but give the novices something like OpenOffice if they just want to type a list or two! Don't you think you're missing the mark if you're trying to sell a newbie on a program so complex that it requires special effort to close it?

Point 5. Look, is it too hard to write a program that has both keyboard shortcuts and menus? I definitely see the point here: Different users have different needs. Once you know the shortcuts, any other way is painfully long. So, I have to disagree on this point, but I totally respect where the opinion is coming from. My version of "user-friendly" says, "Programmed to be usable by those familiar with simple commands and by others who can understand non-obvious shortcuts."

Point 5a. While Point 5 is respectable, its folow-up is less so. While Ctrl-X and Ctrl-V are non-intuitive, they are very efficient. All you need to cut and paste are only but a couple keystrokes away, and the only finger you need to shift is your index finger.

So what does d5w offer? That's just as non-intuitive as Ctrl-X or Ctrl-V to the uninformed. But when you get to know either keystroke combination, that combination becomes familiar and efficient. To the uninformed, d5w doesn't look like much at all. But if you've worked with it before, of course you'll know what it is!

Point 5b. I liked reading the first half of this section, and it all goes downhill from there.

Dominic Humphries is complaining that coding menus takes time. Well of course it does. But if you can't compete with the market, that's your own problem.

Secondly, how is MS Word inferior to Vi and Emacs, because the latter are used for coding? Here's a reality check: MS Word wasn't designed for programming. It was designed for word processing! If you want programming, use an IDE! For God's sake, MS Word is not inferior to Vi or Emacs because they're aimed at different audiences! Is there a joke that I missed, due to lacking a sense of humor? If not, then I can hardly believe the nonsense that I just read.

And again comes up the issue of appealing to the masses. Believe it or not, it's more efficient for some people to just click on what they want instead of learning commands. If you're not going to develop frontends for the programs you're putting into Linux, you're going to have lots of users who will find Linux to be a complete waste of time.

Point 6. This whole portion of the article is one great straw man argument. I don't know how anyone in their right mind would believe that Linux is copying Windows for developing a GUI. What is Point 6 trying to prove?

Point 7. It's this last category that makes this article worth debunking. This "problem" demonstrates arrogance to the highest degree possible. To the common user, it's the middle finger. it's like saying, "Screw you and your little dog, too," to everyone not fortune enough to be in the know. Here, let me sum up "problem 7":

We don't care about you or your needs, and if you don't know what we know, then you're not worth our time.

What a callous choice of words for a community so intent on convincing people that Linux is better. I suppose all those people on Digg who relate tales of switching and never looking back are fringe radicals, hm?

What is so supremely ironic is that Humphries claims that the goal of Linux is to create the best operating system ever. But if you don't accept feedback, how is it going to be usable?

This point is the gotcha clause. The excuse clause. It makes Linux sound like a colossal waste of time to the whole world except for a few people. But the truth is that Linux is usable, and if you're listening to Mr. Humphries, then asking whether or not you are good enough for Linux is an excuse for not supporting you.

Asking the users to do everything for themselves will not only frustrate good people but convince the smart but unexposed people that they'd be wasting their effort on such callous people. Let me ask you something, Mr. Humphries: Are you saying that you're developing an operating system and then not expecting people to use it? That proposition is so laughable that it's hard for me to even refute it. It's ridiculous. It doesn't make sense at all. I'm finding difficulty finding the sense in it. You're developing a usable operating system, not expecting anyone to use it, and criticizing people who expect it to work but have trouble? Doesn't that violate the philosophies of the desktop Linux distros, who are trying to convert the common people? Doesn't that even contradict the goals of Firefox, since Firefox is built from user input?

Mr. Humphries, I really hope that you're not naive enough to believe what you're saying. I sincerely hope that you do not reflect a majority of the Linux community, because "problem 7" is your problem. I sincerely believe that Linux is about the people, not the machines, and if you're crazy enough to insist that the computers matter more than the people, you're not doing anything for Linux. The last category in your article will do nothing to advance your cause.

Monday, December 18, 2006

Don't switch to Linux just because you can

Let me sum up the situation: Yes, it's Linux. But there's no reason for me to use it. Yes, it's free, and yes, it's secure, but I don't need it.

I'm not against Linux: I think it's a great OS, certainly, but I'm not going to switch to it. Reading Digg every day exposes me to a slew of articles about why now is the right time to switch to Linux and how "So-And-So moved from Windows to Linux and never looked back!" but I really see no incentive to move to Linux.

You how everyone knows that Microsoft is copying Apple, and everyone is pretty vocal about it? Well, if you think about it, Linux is copying Microsoft, but no one seems to be talking about it. Admit it, Linux developers are trying to copy Microsoft, even going so far as to emulate it (a.k.a. WINE). Why should I switch to Linux when there's still a desire in the community to run Windows programs? Isn't Linux supposed to replace Windows? It would be like switching to a Mac and claiming that OSX is superior to XP, but then installing Parallels and XP on the Mac. If Linux is really so great, why does it need offerings compatible with another operating system? I know it looks like I'm saying that a smaller software library for Linux makes it inferior, but it is inferior to me.

I have considered switching. But every time I've considered it, I've found a reason to not do it. The big reason is that Windows is easy to use. Ignore the stigma that Windows always crashes; I seemly suffer it naught. Windows recognizes any worthwhile device I can throw at it (not advisable), and it's simple. The Linux community as a whole believes that you should only bother with Linux if you're willing to make it work. This attitude even prevails among the community of desktop Linux users. Lost is my ability to count the numerations of the aforementioned comments on Digg stories. Few Linux supporters that I have witnessed actively believe that Linux should be so easy to use that you don't have to tinker it; that for me is enough to drive me away. I have installed MS-DOS, Windows 95, Windows 98, Windows 2000, and Windows XP on various computers. (I love how you need to install DOS on your computer before you can install Windows 95 on it!) Windows XP is such a cinch to install and use that there's no reason to switch. I'm happy that my computer works just like that. I don't want to use an operating system that needs tinkering to work. You know what I call that? Beta software.

I know I haven't covered security. One word: Router. Now, I'll not be disingenuous. Symantec Antivirus 9 is installed on my computer, although I've never had any viruses on my computer. Simply put, I've never had a security crisis on my computer. If you're smart enough, it won't happen. I'm not advocating Windows to the general public based on my experience, because generally people don't have common sense. (Why on Earth would you click on a pop-up that says, "Click me!"?) Even if Linux does have better security, I don't need it.

Yes, yes, Linux is not all that shabby. But I'm not about to switch to Linux just because it's Linux/it's not Windows. Look, Linux people. You want to hook me in? Here's what I want: Your operating system has to be so easy to use that it will work right out of the box, no tinkering whatsoever; it has to have support from developers that will port all of their Windows software to Linux; it has to have compatibility with every driver Windows can handle; and it must do everything Windows can do, and more. Until then, I'm happy where I am.

Monday, November 27, 2006

Digg: Four things you can put in story descriptions besides, "Title says it all."

When I visit news aggregator Digg, there is a multitude of stories that have titles but no descriptions. Increasingly, users are submiting stories with nothing in the description field but, "Title says it all."

No. Really, no, the title doesn't say it all. Here are eight kinds of descriptinos you could add to give your story depth and a reason for visitors to actualy read your stories:

  1. Personal insight. How does the story relate to your life? What does the story mean to you? Have you had an experience that relates to what you're submitting? Does the link talk about an ordeal that everyone can relate to? If you're truly a human, surely you have an opinion about what you're submitting and a reason for why you're submitting it. God forbid you're linking to your blog and can't be bothered to say why your blog entry deserves to be Dugg. While there's nothing wrong with submitting one of your blog entries, you shouldn't expect to draw traffic to your unknown corner of the woods if the traffic has no incentive to come.

  2. A witty comment. Are you good at telling jokes? Do any obvious puns come to mind? Perhaps you can think of a play on words. Even if it's just a one-liner, readers will appreciate a good laugh. Remember to use humor for stories that are light-hearted or oddball or YouTube links. You wouldn't laugh at a funeral, would you?

  3. Summary of the story. What's the gist of the story? Think back to the fundamentals of writing essays in high school: Who, what, when, where, why, and possibly how. People will want to know the specifics once they know what's happening. Why is the story relevant to anyone? How does the story relate to other stories? What's the backstory? All or some of these can be answered by a concise summary.

  4. Highlights. What if you don't want to write a summary? What if you don't like summaries? If you're linking to an article or thesis, nobody will mind if you cut and paste a section of text from the source that best exemplifies what the story is about.

Let's sum up:You get 75 characters in the title and 350 in the description. You have over quadruple the room for a reason for people to click the link. Why are you submitting to Digg if you don't really have much to say about the story? People will - possibly justifiably - think your story is spam or the dreaded blogspam. The people who read Digg regularly aren't idiots. Write a description that says you aren't one. People's brains won't break if they read a few more words.