Having worked on both sides of the IT support fence, I like the plumbing analogy.

If the plumbers started mandating toilet times and protocols, and required you to get management approval for each piece of toilet paper you planned to use, a month in advance, then you have a problem.

If the company employees insisted on their right to relieve themselves in their offices, and demanded to know why someone isn't there in five minutes to clean up after them, you also have a problem.

If your IT department are blissfully ignorant as to the needs of the organisation, and there is no oversight of what they do, then you have a problem.

If your IT department are forced to jump on demand, and are never given the chance to address network security, stability, or backups appropriately because they are always supporting random device X that has nothing to do with the job (until data is lost, and everyone suddenly remembers that backups *are* needed), then you have a problem.

As with many things, there is a healthy balance between the extremes that a company should be aiming for. It's all common sense, and sometimes, it's not all that common.

> A battleship that has shown its willingnes to keep firing all guns until all atoms previously making up any knife-wielding attacker is at least in earth orbit, preferably in sun orbit.

Well said.

If the size of the battleship doesn't give you pause, climbing over the charred remains of the last few knife-wielding attackers may.

You know, they might not be so rare if every do-gooder with a time machine didn't keep going back in time and picking up all of the remaining copies before they were found.

> Ever wonder why you see so few patent lawsuits from IBM relative to their portfolio?

Personally, I just assumed it was the same reason that you see very few knife attacks on the hull of a battleship.

> well they make hardware (motion capture sensors) for a niche market. So it's not terribly likely that their code being stolen will be a big issue, I think. It's a tiny market with few players. In fact, having the code open might make their hardware easier to integrate for some clients with custom solutions, or at least feel safe about it.

Hardware manufacturers can potentially be good candidates for open source software, since they can release the source, and sell the hardware. If it's a small market or the hardware is expensive, they probably won't gain much from hobbyist contributors, so the question as to whether or not a company is likely to use the source and contribute back becomes more important. Of course, the modifiable source could end up being a selling point as you suggest. :)

> If the cloner comes with a name like IBM, Google, MicroSoft or HP, they can be 3 years behind and still get the contract... nobody ever got fired for choosing ________.

If one of the big players starts intruding into your market, you've probably got a real, business-killing problem to deal with, unless you can satisfy a need that they can not or will not satisfy themselves.

But then again, sometimes they come bearing money instead, since they want the product, but don't want to develop it from scratch.

> Even if your competitors do then take that idea and steal it, it's possible to make money from the fact that your version is always months ahead in innovations. It's easier for someone who is actively inventing ideas to keep the flow of research moving forward, compared to someone that who just copied a subset of their ideas.

This is a very good point. If the product is such that you can keep improving it, and keep those improvements in the eyes of your customers, then anyone cloning the product will be seen as just playing catchup. It then becomes hard for them to compete on anything but price, which is hard to do if they're hiring double the number of developers as well. Heck, open sourcing your last version and charging for your most recent one would probably be one way to keep clone-based competitors from even *starting* to nip at your heels. I'd say there are probably lots of ways of playing it, depending on the type of product, and the potential benefits of opening some or all of the source in those circumstances.

Consider:

- Is your product something that hobby developers might take an interest in? Will their contributions add value to your codebase or company? Will they want to contribute?

- Is your product something other companies might find useful if they took it, added a feature, and contributed it back to you? Will they have any incentive to send anything back to you?

- Do you have anything that you can subsequently sell to the people using your open code, that they are going to want to buy, that a competitor can't quickly spring up and take the opportunity from you?

- Could opening the code allow you to steal away a significant part of the market, that you can later sell products or services to, for a net profit? Is this likely?

And weigh this up against:

- You've given away the code. Is there anything left to sell, and will people want to buy it?

- Would your company survive if someone saw the code, thought it was a good idea, and put double the number of developers on it and told them: "make something like this"? Assume they will use your code as a reference, but no proof of it will ever be found.

- A company with an international presence steals your code, builds it into their product, and sells it. Do you either have the resources to fight a huge multinational (possibly hiding behind a subsidiary in a different country), and the ability to survive for a few years whilst it works its way through the courts, as well as fight off baseless countersuits? Or is your product such that your company will survive, even if it is being ripped off, possibly even benefiting from the exposure?

I think that it's great that you've been able to run Windows for so long, and experienced no driver or stability problems. You definitely should receive some sort of award or official recognition.

Anyway, I'd love to chat, but it's Monday and Suzy's PC is infested with malware again.

A downmod for a post making fun of an attack piece, and an upmod of the attack piece? Stay classy.

Hairyfeet, I'm not 100% sure, but I get the feeling you *might* personally have a preference for using Windows operating systems over Linux-based ones. If you could respond with a few hundred more inflammatory words to let me know for sure, that'd be just peachy.

Also, did you have a traumatic experience using a commandline when you were young? Possibly lost family members due to an accident involving a poorly-formed regular expression? Just curious.

My personal, unverifiable, unscientific, pulled-out-of-my-rear theory is that the development of life similar to and understandable by our own is sufficiently rare, and the universe so imperceivably large that the countless life that has evolved (we'll just say billions of instances in a suitably chosen near-infinitely-tiny fraction of the universe), just haven't *found* each other for the most part. Perhaps we're just unlucky enough to be located sufficiently far from other life, and there are billions of interactions between billions of similarly evolved lifeforms in some areas of the universe. Maybe heavy interaction between such lifeforms is the norm, and we're just part of the smaller fraction who are pretty isolated. Perhaps we are the front of life spreading into a new area, or the result of life dying off in the same area. But even that is probably overstating our importance.

Going with the above, Earth is definitely special case within a certain area, if we extend that area out until just before the closest instance of the uncountable number of other cases that meet the same criteria. :} It certainly seems to be quite unique within the area that we can currently perceive and understand. Perhaps this will change one day, when we can better understand the universe around us. Or perhaps we'll have died off long before then.

Anyway, that's how I like to look at things.

Short version: Tiny fractions of an imperceivably large universe.

Looks like Apple wants in on the patent extortion rort.

Apple's competitors can pull the same tricks too- I'd fully expect a few "innovation startups" to spring up soon, preloaded with patent portfolios, and start hitting Apple back.

My hope is that in the resulting mess a few senior people in the bigger organisations take notice and figure out that they could make huge savings by spending some of that money on political lobbying instead, get patent laws cleaned up, and pull the fangs from these lawsuits. These organisations have made great efforts to get the cheapest manufacturing, labour, and development costs. It seems strange that they haven't gone for similar savings in the legal area as well.

But I know that I'm hoping for too much.

"Linux and UNIX-like operating systems have followed a particular, if arcane, way of organizing files"

In other news, if somebody doesn't personally understand the reason for something, it is now "arcane".

Personally, I still prefer to have "/usr" on its own filesystem, so I can unmount it if I need to and tidy it up, using the tools in "/bin" and "/sbin". It's not *necessarily* a space thing. I quite like the separation between basic tools, and "everything else". If an "everything else" package install or script or similar stuffs things up, it's nice to be able to fix it in a reasonable environment (which an unmounted "/usr" gets you).

I also don't mind the separation between admin tools, and user tools. I think that covers the "/usr/sbin" versus "/usr/bin" thing.

And there we have it.

1. Copy Fruit code? / Develop own code
2. Copy Crafty code? / Develop own code
3. Customise code / Develop own code
4. Enter tournament / Enter tournament
5. Win tournament / Identify Plagiarism!
6. Oh crap /

Black to play and mate in three.