This, in a sense is the equivalent of saying that if a consumer does something so benign as not change their VCR remote batteries on a regular basis, then they deserve to be electrocuted the moment they try to turn the TV off manually.
It's quite a stretch to compare tire inflation with the batteries in your remote. After all, the tires are the things that keep your car on the road. As I heard it, tire inflation was the main cause, and the reason the tires were underinflated was because that was what Ford recommended. You see, if the tires were fully inflated, people complained about the rough ride.
I live in Southern Ontario where there are deer hits relatively regularly in some areas, and the devastation, even at a low speed, is massive:
Note the operative word - small. For example, a rabbit.
You're damn right I'll brake to the greatest extent safely possible. What's that? The person behind me smashed into me? By the rules of the road that is 100% their fault
Or (in MD) they could claim you were braking to avoid a cat. Then it may well be your fault.
Suppose a deer jumps into the road and had you been going 60 you could have breaked in time or it would have made it across?
The only reason I would brake for a deer is the fact that it will seriously mess up my car. If it's a small woodland creature and i'm going fast, it's roadkill. As a matter of fact, in many places (like maryland), it's illegal to brake in this situation.
if there were just a few months stability in the industry such that the media and C*O's can learn what's available, actually understand what things like 'XML' are
What, two and a half years isn't enough? I first encountered XML in 1999.
I believe this method of software creation is good for the Cathedral model, and with well-funded programmers who program for money, it can get done. But keep in mind, that since its not incremental, its not exciting. DFD's on paper, ERD's, are all boring, when you get down to them.
All this formality, boring as it is, is necessary if you want a cohesive, functional product and not a pile of hacks. Further, this model is quite compatible with incremental delivery; it's just a matter of determining your feature set and building to support it at each stage.
Also, I don't see how multiple contributors can't fit into this well-framed process.
They certainly can, but they should be strictly limited in the initial stages. Too many designers will kill your design clarity.
An assumption of mine, is that most useful features of a program are suggested at its usage stage, and not its design stage - This means you better minimize the design stage, and get to the usage stage as soon as possible. Do you disagree with this assumption?
Vehemently. useful features and usage models are best done at design stage, which necessarily includes a prototype (Maya, in this case). The worst thing that can happen is to get to the usage stage (near the end of the dev cycle) and find out that your core assumptions were wrong. Better to find that out up front.
As far as the specific question being asked here, I think this guy's got no chance, and he'd be better off thinking about what unique features he wants and then go write a plugin.
[It] means that, in this case at least, the auto makers (with pressure from congress) decided that public good out weighed copyright law.
It's more likely that they believed that, had they not done this, congress would have found a way to open it forcibly in the interest of free trade or something.
While it is true that no war has technically been declared, that is due more to the fact that there is no sovereign state to declare war against.
Not true, else we would have declared war on Iraq back in 1990. The reason we haven't and won't declare war is because we don't need to put the country on a war footing, which is what we would be doing by declaring war.
There is know known cure other than enlightened managers and these are hard to come by.
Sounds like what you really mean is Unrealistic Deadline Syndrome. Try telling your boss that the software is feature complete, but it needs to be 50% faster. See if he gives you the extra month.
And this is different from restricting my "Use" of the code by distributing it how I like how? Maybe my entire "use" of the code is distributing it. How is restricting distribution any different from restricting the running of it. They are both actions that can be taken with the copyrighted object in question.
Is this some kind of joke? Use of a program is not covered nor is it restricted in any way. Distribution is granted, sbuject to conditions. If you don't like it, don't accept the license. Then it reverts to standard copyright, which also governs distribution. By default, standard copyright reserves all rights to the author.
You obviously don't know anything about suspensions, because there's a lot more to them that just raising and lowering. A suspension design that works well on a truck will never perform well on a car, because of the different goals to be met.
You're deliberately missing the point: with no engine and no drivetrain, the porblem of ground clearance is vastly simplified. The hydraulic lifts were simply thrown in in order to have something.
In addition to making war on europe and killing 6 million jews, Hitler started volkswagen. He didn't do the engineering, but he did do the requirements (affordable, reliable, specific performance and weight requirements for the engine), and his chief designer went on to work for Porsche. Thus concludes today's history lesson.
True, one of the accepted meanings of the word "average" is "being intermediate between extremes". However, the thing about that statement is that "50%" is by definition at the median, NOT the average.
Actually, it is. Average may mean 3 things - mean, median, or mode. Without more info, there's no way to say which. This is used to great effect in advertising, where they say average, but do not mean mean, as most assume.
In other news, the original comment is a fucking joke on this subject, which you totally missed. Thank you for playing.
Yeah, you should finance at least one of those cars so you get a credit bump. You can have fun with this - show up at the dealer, hardball the price so they try to screw you on the financing, then pay it off in 2 or 3 months.
The only way you're going to charge batteries in 5 minutes for 2 hours of driving is by using liquid acid batteries
Why not just manufacture the batteries to a uniform size and power grade. Then instead of charging them, swap them out. This also handles the problem of limited life cycle - add a surcharge to cover replacement after 2 or 3 years. In addition, this allows your car to take advantage of better technology.
If you hire two programmers that each work for 40 hours per week rather than one that works 80, you double your administrative costs, health insurance costs, training costs, etc
You also double the amount of work produced. Not so with programmers working 80 hour weeks.
Slashdot Mirror
interstellar starships are created from genetically engineered trees grown in orbit.
Perchance, were any of the trees named Tsunami?
The cool thing is that, should somebody detach the thing, it'll fall up
This, in a sense is the equivalent of saying that if a consumer does something so benign as not change their VCR remote batteries on a regular basis, then they deserve to be electrocuted the moment they try to turn the TV off manually.
It's quite a stretch to compare tire inflation with the batteries in your remote. After all, the tires are the things that keep your car on the road. As I heard it, tire inflation was the main cause, and the reason the tires were underinflated was because that was what Ford recommended. You see, if the tires were fully inflated, people complained about the rough ride.
That's a thoroughly inconsistent law
No, it makes a value judgement you disagree with. To wit, the life of a small furry beast is not worth endangering others over.
I live in Southern Ontario where there are deer hits relatively regularly in some areas, and the devastation, even at a low speed, is massive:
Note the operative word - small. For example, a rabbit.
You're damn right I'll brake to the greatest extent safely possible. What's that? The person behind me smashed into me? By the rules of the road that is 100% their fault
Or (in MD) they could claim you were braking to avoid a cat. Then it may well be your fault.
Suppose a deer jumps into the road and had you been going 60 you could have breaked in time or it would have made it across?
The only reason I would brake for a deer is the fact that it will seriously mess up my car. If it's a small woodland creature and i'm going fast, it's roadkill. As a matter of fact, in many places (like maryland), it's illegal to brake in this situation.
if there were just a few months stability in the industry such that the media and C*O's can learn what's available, actually understand what things like 'XML' are
What, two and a half years isn't enough? I first encountered XML in 1999.
I believe this method of software creation is good for the Cathedral model, and with well-funded programmers who program for money, it can get done. But keep in mind, that since its not incremental, its not exciting. DFD's on paper, ERD's, are all boring, when you get down to them.
All this formality, boring as it is, is necessary if you want a cohesive, functional product and not a pile of hacks. Further, this model is quite compatible with incremental delivery; it's just a matter of determining your feature set and building to support it at each stage.
Also, I don't see how multiple contributors can't fit into this well-framed process.
They certainly can, but they should be strictly limited in the initial stages. Too many designers will kill your design clarity.
An assumption of mine, is that most useful features of a program are suggested at its usage stage, and not its design stage - This means you better minimize the design stage, and get to the usage stage as soon as possible. Do you disagree with this assumption?
Vehemently. useful features and usage models are best done at design stage, which necessarily includes a prototype (Maya, in this case). The worst thing that can happen is to get to the usage stage (near the end of the dev cycle) and find out that your core assumptions were wrong. Better to find that out up front.
As far as the specific question being asked here, I think this guy's got no chance, and he'd be better off thinking about what unique features he wants and then go write a plugin.
[It] means that, in this case at least, the auto makers (with pressure from congress) decided that public good out weighed copyright law.
It's more likely that they believed that, had they not done this, congress would have found a way to open it forcibly in the interest of free trade or something.
While it is true that no war has technically been declared, that is due more to the fact that there is no sovereign state to declare war against.
Not true, else we would have declared war on Iraq back in 1990. The reason we haven't and won't declare war is because we don't need to put the country on a war footing, which is what we would be doing by declaring war.
Believe it or not, this is a feature I would use.
Same here, only i already use it - it's called scp and it works with any systems that support ssh (and have it configured)
Colour me stupid, but I tend to think that a superior game console that doesn't have games is best defined as a paperweight.
Nah, Paperweights don't cost $200
There is know known cure other than enlightened managers and these are hard to come by.
Sounds like what you really mean is Unrealistic Deadline Syndrome. Try telling your boss that the software is feature complete, but it needs to be 50% faster. See if he gives you the extra month.
And this is different from restricting my "Use" of the code by distributing it how I like how? Maybe my entire "use" of the code is distributing it. How is restricting distribution any different from restricting the running of it. They are both actions that can be taken with the copyrighted object in question.
Is this some kind of joke? Use of a program is not covered nor is it restricted in any way. Distribution is granted, sbuject to conditions. If you don't like it, don't accept the license. Then it reverts to standard copyright, which also governs distribution. By default, standard copyright reserves all rights to the author.
Oh, wait. IHBT, right?
You obviously don't know anything about suspensions, because there's a lot more to them that just raising and lowering. A suspension design that works well on a truck will never perform well on a car, because of the different goals to be met.
You're deliberately missing the point: with no engine and no drivetrain, the porblem of ground clearance is vastly simplified. The hydraulic lifts were simply thrown in in order to have something.
But it didn't have anti-piracy features!
Big deal. Neither does XP.
Umm, Hitler was a dictator, not an engineer.
In addition to making war on europe and killing 6 million jews, Hitler started volkswagen. He didn't do the engineering, but he did do the requirements (affordable, reliable, specific performance and weight requirements for the engine), and his chief designer went on to work for Porsche. Thus concludes today's history lesson.
True, one of the accepted meanings of the word "average" is "being intermediate between extremes". However, the thing about that statement is that "50%" is by definition at the median, NOT the average.
Actually, it is. Average may mean 3 things - mean, median, or mode. Without more info, there's no way to say which. This is used to great effect in advertising, where they say average, but do not mean mean, as most assume.
In other news, the original comment is a fucking joke on this subject, which you totally missed. Thank you for playing.
They claim I can't remove it, because I told them I didn't enter it in the first place.
Sounds like a legitimate reason to me.
Sounds actionable to me (IANAL). Something about accomplice to fraud.
Verisign, abominable as they may be, are most certainly not the only culprits of this practise in the registrar world.
They are, however, so legendary for their horrid service and incompetence that they had to change their name.
good luck getting a house.
Yeah, you should finance at least one of those cars so you get a credit bump. You can have fun with this - show up at the dealer, hardball the price so they try to screw you on the financing, then pay it off in 2 or 3 months.
my favorite, "if you were so smart, you would be working at IBM like me doing network engineering instead of taking calls from people like me."
I'm sure it's really hard to outwit a person who doesn't dare respond because he's being taped.
The only way you're going to charge batteries in 5 minutes for 2 hours of driving is by using liquid acid batteries
Why not just manufacture the batteries to a uniform size and power grade. Then instead of charging them, swap them out. This also handles the problem of limited life cycle - add a surcharge to cover replacement after 2 or 3 years. In addition, this allows your car to take advantage of better technology.
Lack of speed. When I need to merge, I need to get up and GO damn it.
In all fairness, this isn't a problem - electric motors beat gas as far as torque is concerned.
If you hire two programmers that each work for 40 hours per week rather than one that works 80, you double your administrative costs, health insurance costs, training costs, etc
You also double the amount of work produced. Not so with programmers working 80 hour weeks.