If you liked this post, you may also be interested in...
- Hertz Ordered To Tell Court How Many Thousands Of Renters It Falsely Accuses Of Theft Every Year
- Even As Trump Relies On Section 230 For Truth Social, He's Claiming In Lawsuits That It's Unconstitutional
- Letter From High-Ranking FBI Lawyer Tells Prosecutors How To Avoid Court Scrutiny Of Firearms Analysis Junk Science
- FTC Promises To Play Hardball With Robocall-Enabling VOIP Providers
- FOIA Lawsuit Featuring A DC Police Whistleblower Says PD Conspired To Screw Requesters It Didn't Like
Reader Comments
Subscribe: RSS
View by: Time | Thread
No Subject Given
[ link to this | view in thread ]
Apple's leak.
That would explain a lack of reaction from Apple against C/Net...
[ link to this | view in thread ]
Of course not
[ link to this | view in thread ]
Did they invite it?
So for the Mac rumor sites, there's a pretty clear culpability. For c|net, Apple can sue for sources, but don't have nearly as strong a case, as c|net doesn't publicly beg for NDA violations.
[ link to this | view in thread ]
No Subject Given
Chris H on June 6, 2005 07:11 AM writes...
I think the difference is that C|Net might just be wrong. Remember, Apple was upset because the blogs posted very specific technical details, NOT rumours. The C|Net article is also vague. Will it be x86, PPC, or something else? The article is pretty low on technical detail and specs, which is a huge difference...
The other possibility is that Apple intentional leaked this rumour to build interest in WWDC (I didn't think it was going to be a big deal; now I will be watching)
and...
Chris W on June 6, 2005 07:23 AM writes...
I don't want to be repetitive, so I suggest you consider what Chris H. has posted. if C|Net came out and said Intel will began producing x86 chips for the new 4.2Ghz Powerbooks, I imagine Apple would be all over them (justified or not). It seems as though you are stretching for a relation that doesn't exist here.
Interesting you didn't have an opinion on this- not your norm.
[ link to this | view in thread ]