I hate to say it because it just makes me look like another fanboy, but essentialy you just described OS X. But even there Apple faced problems, and so will Linux and the biggest problem they will face is the legacy free bit.
Everyone wants their computer to run and support everything. You kill legacy and you piss people off.
Actualy you're wrong as well. Familiarity and compatability with work machines is what drives the desktop market. I see it all the time whenever someone walks into a computer store and looks at the macs. The firs tthing they ask is will it do stuff like their work computer and in the same manner that their work computer does it, and the second thing they ask is is there a good reason to pay more for it. That good reason is where asthetics, ease of use and other features come in. In my experience, cost is a suprisingly low factor, as most people looking to buy a computer come with a set price range that they want to spend in anyways.
Sure they are if that's what he was hired to do. Unless he was hired for a specific project, and that was his job description, then they have a right to any work that is related to his job. Thus if his job description is "Application Developer" then any "Applications" he "Develops" are first dibs to Apple if that's the contract he signed.
They don't own it, they have a right to it if they want it and that's the difference. If you signed the contract, you agreed to those terms. If you didn't agree, you shouldn't have signed the contract. It's very simple. The law explicitly states that content created relating to your work can be claimed by your company in a contract. Therefore, if you are hired to write code (not hired for a specific project mind you) then any code you right is first dibs to your employer.
As for you not wanting code you write in your spare time to go to your employer, you do have a choice. You have a choice to not sign the contract, to renegotiate the contract or to terminate your employment. However, you signed the contract, you agreed to the terms which are bounded by law.
I don't base my entire life arround my job, but I am reasonable. It is perfectly reasonable that if I am a programmer as a primary function of my job, that anything I program while I am employed, regardless of where or when, should first be given to my employer. If my employer does not want the project, then I am free to do with it as a please.
And why should I want or do otherwise? If I enjoy coding, then shouldn't I be happy to see my product incorporated into a major product? Should I not be happy to see my code distributed to far more people than would have been likely under the shareware model?
On top of that, if I first approach my employer with my code that I developed at home, I can really only stand to gain as I improve my standing in the company, I generate a level of respect between my superiors and myself, show my dedication to my company and am in a much better position to ask for and recieve just compensation for my work. I'm also in a better position if they turn it down, because then I have in writing that they did not want my product and as such they have no legal case if my product becomes succesful and they want in.
Not quite. Anything computer software related would fall under it, because you're company is a software company and that's what you were hired to do. If you designed a mouse, that would not, becuase it isn't related to your job.
Actualy, if this were microsoft doing this, I would be willing to bet you'd see a lot of the same comments. Contracts are contracts, if you signed it, it's your word. And don't quote the law, because the law has provisions for exceptions that this seems to fall under, and you can be damned sure Apple's legal team didn't miss that.
Read the law and it says that creations pertaining to your employers business are exempt from that law though. If he was hired by Apple to write software for OS X, then software he writes for OS X is Apple's during the duration of employment.
for that to fly you would have to prove that you were under immediate threat of homelessness and starvation. IOW you would have to prove that it would have been impossible for you to:
a) negotiate another contract b) seek a new or different job c) support yourself in another manner.
I think it should depend on your job. What you were hired to do. For example, if Apple hires me to write code specificaly for iMovie, and I write a text editing program in my spare time at home, that editor belongs to me. However, if I was employed by Apple as a programmer, period, and that was my job to write code for Apple, then any software I write in my free time is in part theirs because that's what I was hired to do.
I fail to see how this works. Under the current policy , saving the best for yourself means the best will never see the light of day, because if you distribute it, the company owns it. OTOH if you go above and beyond and develop this great thing on your own time, and the first thing you do is go to your employer and say "I've been working on this at home, do you guys wan't dibs on this?" you're in a better position to negotiate for compensation, you're in better standing with the company, and your idea may get even better distribution than you could have hoped for.
The thing is, you can probably (haven't tried it as I don't have one) get OS X to run on a beige too. Just like you could get OS X to run on systems that were not G3s or G3 ugrades using X post facto. The only thing apple did was drop official support for it.
The thing is, if you create something relating to your job, you should always ask your employer if they want it first. Hell Steve Wozniak did it with the original Apple computer. Developed on his own time, with his own equipment, and the first thing he did was take it to HP and ask them if they wanted it. Besides, if you volunteer your new design, I would think you're in a much better position to ask for a bonus for it.
The cheap box wont run OS X
The cheap box doesn't have as good a display
The cheap box isn't quiet
The cheap box doesn't have firewire
The cheap box wont fit into a small space
The cheap box doesn't have a DVD burner
Because by using the cheap box, I somehow have something in common with idiots like you.
I call bullshit. Your numbers are too close together. OS X is on a roughly 13 month upgrade pattern. Therefore, we wont see 10.4 untill late, most likely Nov of 04 (if that soon, as eventualy it will slow down). Which means at best we'll see 10.5 at the end of 2005. You're welcome to prove me wrong, but I call bullshit.
it may be possible that something is wrong with your adress book file because I've never seen this problem on either.
As for iTunes, I beleive that if you move the songs to a seperate disk, it looses track of the song because of the nature of the file system. iTunes itself doesn't have a direct link to where the file is, instead as I understand it (though I may be wrong) the computer has a sort of central map to point to where all the files are, and programs that need to access files access the map for the file location. But you can try this, first make sure that in the iTunes preferences, the option to copy songs into the music folder when adding them to your library is unchecked. Then physicaly drag and drop (or file -> add) the songs on the external disk to yoru library.
Ummm, the last printer Apple made was in something like 1996. Of course they don't support them any more, they're EOL. Tell yor friend to use the discussion forums at Apple
Wait a minute. You bought a product, and then they released a new version of the product, and you're pissed because they wouldn't give you a new version for free?
If I buy a motherboard for my PC and two weeks later they release a new version of the board with hardware RAID support, should they send me a new board for free?
As for the firewire drives, they probably waited a week untill they had enough confirmed reports of failure to give specifics as to which drives were affected. It makes no sense to release a blanket press release that it isn't working with firewire drives, because that clearly wasn't the case. You'll notice when they finaly released an official statement they had full details on which drives were failing.
It's possible that batteries have indeed gotten better and more efficient but that the technology that we've been using them in has gotten more and more power hungry?
Slashdot Mirror
I hate to say it because it just makes me look like another fanboy, but essentialy you just described OS X. But even there Apple faced problems, and so will Linux and the biggest problem they will face is the legacy free bit.
Everyone wants their computer to run and support everything. You kill legacy and you piss people off.
Actualy you're wrong as well. Familiarity and compatability with work machines is what drives the desktop market. I see it all the time whenever someone walks into a computer store and looks at the macs. The firs tthing they ask is will it do stuff like their work computer and in the same manner that their work computer does it, and the second thing they ask is is there a good reason to pay more for it. That good reason is where asthetics, ease of use and other features come in. In my experience, cost is a suprisingly low factor, as most people looking to buy a computer come with a set price range that they want to spend in anyways.
Sure they are if that's what he was hired to do. Unless he was hired for a specific project, and that was his job description, then they have a right to any work that is related to his job. Thus if his job description is "Application Developer" then any "Applications" he "Develops" are first dibs to Apple if that's the contract he signed.
They don't own it, they have a right to it if they want it and that's the difference. If you signed the contract, you agreed to those terms. If you didn't agree, you shouldn't have signed the contract. It's very simple. The law explicitly states that content created relating to your work can be claimed by your company in a contract. Therefore, if you are hired to write code (not hired for a specific project mind you) then any code you right is first dibs to your employer.
As for you not wanting code you write in your spare time to go to your employer, you do have a choice. You have a choice to not sign the contract, to renegotiate the contract or to terminate your employment. However, you signed the contract, you agreed to the terms which are bounded by law.
I don't base my entire life arround my job, but I am reasonable. It is perfectly reasonable that if I am a programmer as a primary function of my job, that anything I program while I am employed, regardless of where or when, should first be given to my employer. If my employer does not want the project, then I am free to do with it as a please.
And why should I want or do otherwise? If I enjoy coding, then shouldn't I be happy to see my product incorporated into a major product? Should I not be happy to see my code distributed to far more people than would have been likely under the shareware model?
On top of that, if I first approach my employer with my code that I developed at home, I can really only stand to gain as I improve my standing in the company, I generate a level of respect between my superiors and myself, show my dedication to my company and am in a much better position to ask for and recieve just compensation for my work. I'm also in a better position if they turn it down, because then I have in writing that they did not want my product and as such they have no legal case if my product becomes succesful and they want in.
Not quite. Anything computer software related would fall under it, because you're company is a software company and that's what you were hired to do. If you designed a mouse, that would not, becuase it isn't related to your job.
er, what's wrong with the ADP?
Closed architecture is a thing of business, you'll be hard pressed to find any companies that don't have it.
Any specific examples of the mine mine mine attitude?
They aren't brutefully stealing anything because it was in the contract he signed.
Actualy, if this were microsoft doing this, I would be willing to bet you'd see a lot of the same comments. Contracts are contracts, if you signed it, it's your word. And don't quote the law, because the law has provisions for exceptions that this seems to fall under, and you can be damned sure Apple's legal team didn't miss that.
Read the law and it says that creations pertaining to your employers business are exempt from that law though. If he was hired by Apple to write software for OS X, then software he writes for OS X is Apple's during the duration of employment.
for that to fly you would have to prove that you were under immediate threat of homelessness and starvation. IOW you would have to prove that it would have been impossible for you to:
a) negotiate another contract
b) seek a new or different job
c) support yourself in another manner.
I think it should depend on your job. What you were hired to do. For example, if Apple hires me to write code specificaly for iMovie, and I write a text editing program in my spare time at home, that editor belongs to me. However, if I was employed by Apple as a programmer, period, and that was my job to write code for Apple, then any software I write in my free time is in part theirs because that's what I was hired to do.
IANAL but don't modifications to contracts have to be agreed on by both parties?
I fail to see how this works. Under the current policy , saving the best for yourself means the best will never see the light of day, because if you distribute it, the company owns it. OTOH if you go above and beyond and develop this great thing on your own time, and the first thing you do is go to your employer and say "I've been working on this at home, do you guys wan't dibs on this?" you're in a better position to negotiate for compensation, you're in better standing with the company, and your idea may get even better distribution than you could have hoped for.
The thing is, you can probably (haven't tried it as I don't have one) get OS X to run on a beige too. Just like you could get OS X to run on systems that were not G3s or G3 ugrades using X post facto. The only thing apple did was drop official support for it.
The thing is, if you create something relating to your job, you should always ask your employer if they want it first. Hell Steve Wozniak did it with the original Apple computer. Developed on his own time, with his own equipment, and the first thing he did was take it to HP and ask them if they wanted it. Besides, if you volunteer your new design, I would think you're in a much better position to ask for a bonus for it.
and what pray tell qualifies as a real enthusiast or nerd?
Because:
The cheap box wont run OS X
The cheap box doesn't have as good a display
The cheap box isn't quiet
The cheap box doesn't have firewire
The cheap box wont fit into a small space
The cheap box doesn't have a DVD burner
Because by using the cheap box, I somehow have something in common with idiots like you.
Gotta keep a better eye on the upgrade cycles. 6 Months per product.
I call bullshit. Your numbers are too close together. OS X is on a roughly 13 month upgrade pattern. Therefore, we wont see 10.4 untill late, most likely Nov of 04 (if that soon, as eventualy it will slow down). Which means at best we'll see 10.5 at the end of 2005. You're welcome to prove me wrong, but I call bullshit.
it may be possible that something is wrong with your adress book file because I've never seen this problem on either.
As for iTunes, I beleive that if you move the songs to a seperate disk, it looses track of the song because of the nature of the file system. iTunes itself doesn't have a direct link to where the file is, instead as I understand it (though I may be wrong) the computer has a sort of central map to point to where all the files are, and programs that need to access files access the map for the file location. But you can try this, first make sure that in the iTunes preferences, the option to copy songs into the music folder when adding them to your library is unchecked. Then physicaly drag and drop (or file -> add) the songs on the external disk to yoru library.
Ummm, the last printer Apple made was in something like 1996. Of course they don't support them any more, they're EOL. Tell yor friend to use the discussion forums at Apple
Wait a minute. You bought a product, and then they released a new version of the product, and you're pissed because they wouldn't give you a new version for free?
If I buy a motherboard for my PC and two weeks later they release a new version of the board with hardware RAID support, should they send me a new board for free?
As for the firewire drives, they probably waited a week untill they had enough confirmed reports of failure to give specifics as to which drives were affected. It makes no sense to release a blanket press release that it isn't working with firewire drives, because that clearly wasn't the case. You'll notice when they finaly released an official statement they had full details on which drives were failing.
You must have been running the public beta. Because that's all that would have been out in early 2000
Not to feed trolls but:
a) Learn how to spell and type
b) What do you mean looking for addresses for 20 seconds?
c) Apple did not move BACK to UNIX, because Apple never used UNIX before.
d) You can very easily move music from one location to another outside of iTunes all the time and it works perfectly.
e) As for within iTunes, why do you want to move files arround your HDD from withinn a music player?
It's possible that batteries have indeed gotten better and more efficient but that the technology that we've been using them in has gotten more and more power hungry?