Too bad you don't love humans half as much as you love dogs. Perhaps when our alien overlords stop by looking for food, you can offer yourself up as a tasty treat. Damn humanity and all those evil things we've done to dogs. . . like CREATE THEM. What could be more evil and sadistic than hurting a dog? Gee, it couldn't be genocide or torture or rape or dumping millions of gallons of oil into the Gulf of Mexico. . .

I think you've just provided ample evidence of why someone might love dogs more than humans.

I don't see where hesaigo is claiming no act is more evil than hurting a dog. It seems you filled that part in, in order to attack this pet issue (no pun intended) you're carrying around. I think that is what is commonly termed a "strawman."

But, since you mention it: yes, genocide and torture of humans is worse, because humans are capable of distrust and are capable of fighting back, while most dogs will do neither.

The greatest moral perversion of this age, aside from egoism, is the "animal rights" whackos who prioritize the wellbeing of animals over that of human beings. Those who equate the value of life with the ability to suffer, such as Peter Singer. Dogs are dumb, the fact that they have a broad range of emotions doesn't change that. They're our slaves, both physically and mentally bread to be so. A dog not enslaved to humanity is a wolf, hyena, or fox.

If both you and a dog were in a burning building, I'm one of many people who would save the dog first, and depending on my mood, I might or might not go back to rescue you and your bible. People like Singer aren't just valuing life based on whether it can suffer, but rather on all the same criteria used to judge human life except species itself.

No one is putting human life above nonhuman life. Some people are simply suggesting they're equal, that a life should be valued based on the merits of its personality and contributions. If your objection is that some parts of your bible claim otherwise, you probably already realize that it had a lot of claims of inequality which have mostly been dismantled in modern society.

P.S. Hyenas are not canines.

More people are killed by dogs then wild animals AROUND the ENTIRE world.

Your kitten? Wouldn't hurt a fly... oh okay, maybe a fly but nothing else... except mice... and spiders... but you are perfectly safe... unless it can find a way to kill you without leaving a trace.

That is some serious FUD.

First of all, there is not a single puppy on earth who will hurt a human being. Not one.

Second of all, take just ten seconds to think about it and you will realize that dog attacks are more common than wild animal attacks because people are in the company of dogs far more than they are in the company of wild animals. And it doesn't help that many people train dogs to be weapons.

Further, it's actually fairly difficult to get attacked by a wild animal. Most of them want to be left alone and will flee from humans.

I'm not claiming dogs are more intelligent (or less intelligent) than cats; I'm just correcting your misinformation. I actually like the company of both.

Or were you toilet trained by your mom rubbing your nose in it?

I hope that's hypothetical. If you think that's a real, legitimate method of training dogs, you have no business being around them.

Says Mr. Lee:

The Web should be usable by people with disabilities.

If Slashdot is any indication, 95% of web developers will assume they are expected to write multiple versions of each HTML page and will practically riot in the streets before honoring accessibility.

The only solution I can offer is to create some sort of Web author certification. Nothing grand, just something that at least indicates the holder has retained the salient parts of the HTML 4.01 and CSS 2.1 specs. Like accessibility.

You, the player, spend on average €60 or $60, depending on which side of the pond you are on ...

I thought everyone knew by now that paying $60 for a game is foolish. Very few games are so good that they are worth buying as soon as they come out. Most games are half that price after only a month or two, and a third that price after six months.

Sometimes the price drop is bizarre. I remember seeing unopened retail boxes of Bioshock for $5 in regular stores, only a year after Bioshock had come out! Yet, somehow, "gems" like Family Feud Home Edition continue to clog up the shelves for $20 each....

Don't blame outsourcing, blame having 20 years experience and still being a code-monkey. Your job should be "business analyst" by now - yeah, cringe at the title, but the point is to apply that experience towards requirements analysis and planning, and let the kids waste time in actual IDEs.

You are a major part of the problem. What I see in your words is that all developers are identical to entry-level code monkeys. In your mind, someone who spends decades becoming an excellent software engineer is worthless; the only worthwhile use of his time would have been learning to be a manager.

This is the real reason managers are so willing to outsource: they think everyone who can make code compile is equivalent, whether their experience is one month or twenty years. In the context of that belief, it makes sense to send the labor overseas.

I'll admit, though, that any engineer who's no better than he was twenty years ago has only himself to blame. (And I've met at least one who fits that description.)

Been tried before. I'd advise you to learn from their mistakes, but I'm not sure what they could have done to avoid their fate.

There are literally hundreds of reasons that the ribbon is superior to menus. Perhaps many of those reasons don't apply to you, or you are simply stubborn and don't want to learn something new. There are of course reasons why the menus are better than ribbons, but too many people act like it's all or nothing... That either Ribbons are better or menus are better, for everyone. Period. What's worse, most people argue reasons that aren't even true, like there being no keyboard shortcuts or that they're different keyboard shortcuts than they used to be. Or that the ribbon takes up more space (which it doesn't, especially if you auto-hide it)

I would be inclined to agree with your argument (well, not the "hundreds of reasons" part), if not for the fact that Office 2007 does not give users the choice. Any user interface programmer knows it would be trivially easy to allow switching between the ribbon and a menu bar. But Microsoft has deliberately kept that capability out. There used to be a Knowledge Base article that flat-out stated "you can't switch from the ribbon to a menu bar, and we did it that way on purpose." But I can't find the article anymore.

A good user interface satisfies all (major) user groups. It's usually not that difficult.

But, here's a few examples.

Menus are hard for people without fine motor control to use. If you are old, disabled, or simply not very well coordinated, ribbons will be much easier to use than trying to make your mouse follow the narrow paths that make submenus show up.

You have heard of the mile high menu bar, yes? It's true larger buttons are better than smaller buttons, especially for people with impaired motor skills. This actually suggests not that ribbons are easier to use than menus, but that they are easier to use than the tiny little toolbar buttons on the vast sea of Office toolbars.

The menus have become monstrous, with more and more features being added to apps, it's harder and harder to find the items you're looking for. The ribbon allows better organization, and "context sensitivity".

Yeah. That's not the fault of menus, that's the fault of the designers' inability to effectively organize the functions of the application. Rather than spend the effort to actually organize things, they tried "Personalized menus" (the visual equivalent of sweeping things under the rug) and when that failed, well, we got ribbons.

The ribbon is far more intuitive to new users.

The ribbon scales to your screen, making buttons smaller if you have less room and changing various other sizes.

I haven't seen any evidence, or even anecdotes, that suggests it's more intuitive. What I have seen is a few decades of accumulated observations that report that a consistent and stable user interface is crucial. Users can't build a pattern of behavior, much less muscle memory, if the controls are moving around all the time. It's like trying to become a touch-typist when the keyboard wants to rearrange itself based on the words you've recently entered.

I have also seen a few decades of accumulated observations that users should be able to list or otherwise examine all of the functionality available to them. That's why it's better to disable or gray out controls than to remove them. The user can't try out a function if he doesn't know it exists because he never saw it in passing while navigating for other functions.

In fact, it's counterintuitive, because it's trying to second-guess the user's wishes by "smartly" showing the "needed" controls. I would have thought Microsoft learned its lesson regarding second-guessing the user with an amateur attempt at AI, after the debacle that was automatic outline numbering in Word 97.

The ribbon provides live previews of changes before you apply them.

That is genuinely useful. What does it have to do with ribbons? It certainly doesn't replace any aspect of a menu bar. It could easily be its own panel or window.

Etc.. etc.. etc.. The ribbon is a net win if you give it a chance. Most people that argue against it have not given it a chance.

Forgive me, but this sounds like yet another "Windows/Microsoft product X is okay once you get used to it" statement. It's a true statement, but that doesn't mean the software is good. It just means one can learn to tolerate it.

James Gosling: ...I'm sure they were looking at the license fees they were getting from Microsoft. Microsoft .NET just smears over a huge pile of Sun patents. When they did the .NET design, they basically cut and pasted from the Java spec. The way that they did CLR, you know they swizzled the way the instruction set went but the way this thing really operated, they exercised essentially no creativity when coming up with .NET. They've done some things since then that have been kind of good but as part of the various court cases we ended up with this rather odd patent deal with them that involved them paying us fairly tasty amounts of money. And I'm sure that the lawyers looked at the Microsoft numbers and said, yeah I want that from Google

I actually did not know, until today, that Microsoft was paying a Java patent license fee for .NET's design.

Just before he said the above, he said this, which is probably obvious to many people, but I found it poignant all the same:

James Gosling: With Oracle it doesn't have to make sense, it just has to make money.

Don't write games in Java idiots.

Yeah, nothing good can come of it.

When are people going to grow up and admit MS has released several top-of-the-line products recently? IE is getting much nicer, especially with 9, and Windows 7 blows away any other OS available, except for certain *nix distributions for specific reasons. Likewise, if you would actually give the .NET framework and its associated languages a try you may find yourself impressed with the capabilities.

Surely you jest. Just because IE 9 and Windows 7 are vastly better than their horrid predecessors does not make them top-of-the-line. And .Net is just Java with a flood of feature creep and syntactic candy. As Microsoft has done so many times before, they took something successful and copied it, while completely overlooking the reason for its success: Java's strength was and is in its lack of syntactic fluff. It makes the code take slightly longer to write but dramatically and mercifully faster to read and maintain.

As far as I can work out, this is a follow on from a game previously released 14 years ago? is this correct? So who will care about its release apart from some very old-skool gamers? I guess it's just a kind of in-joke for old slashdot fans these days?

It's a sequel to one of the best games ever made. That's why everyone who remembers it cares.

More than that, we know that 3DRealms, who was responsible for the predecessor, created much of the content for this one, so there is ample reason to believe Duke Nukem Forever will be as fun as Duke Nukem 3D. Most gamers understand that what makes a game great isn't the polygon count, it's the gameplay. And Duke 3D was both a lot of fun and had excellent level design. If you can stand to play an FPS that lacks free-look, you should try it; you'll quickly understand what the big deal is.

We wouldn't continue to deride Duke Forever's epic tale of mismanagement if the previous game hadn't captivated our interest as much as it did.

Companies have no interest in paying more for people more skilled in software engineering. They want people who can "just write code." The medium-term to long-term consequences of writing unmaintainable, disorganized, undocumented code are almost never recognized by management. And even if they were recognized, we live in a short-term-profit world, where it is standard practice to run a project or company into the ground by releasing a shoddy product which holds together just enough to avoid lawsuits.

A company who values older developers is a company who values the quality and long-term viability of its products. Good luck finding one of those.

The .NET platform is leaps and bounds ahead of the Java platform in nearly every way.

When you're older and you've done tons of code maintenance, especially maintenance of code written by others, you'll realize Java's simplicity and lack of "features" are what make it superior. No language can guarantee maintainable code, but certainly having fewer means to write heinously complicated code betters one's chances. Syntactic sugar rots productivity the way cane sugar rots teeth.

Yeah, I know, I just fed a troll....

How nice of them. They apologized for calling Linux a cancer.

Still waiting for an apology for the OOXML atrocity. In fact, it's going to take a lot more than a few contributions and nice words to make me put OOXML and its enormously dirty dealings in the past.