yellow
Apr 4, 12:33 PM
"Shooting To Wound" is purely a product of television, movies, and video games. In real situations where gunfire is exchanged, milliseconds count, and center mass until the target is down is the ONLY reality.
ksz
Jul 14, 09:40 AM
Does anyone think we should be hitting 4ghz about now?
I mean weve been stuck on 2.x for ages. Whats the deal? A 4ghz quad would be frickin awesome. :confused:
If you raised the clock speed of NetBurst-based Pentium 4s (or Pentium Ds) to 4GHz, you would still not achieve the same performance as today's Conroe at 2.13GHz. Clock speed alone is not an accurate gauge of performance.
Because of increasing problems with heat density, clock speeds haven't been rising at their historical rates. A kind of brick wall was hit when the semiconductor industry moved to 90nm. At those dimensions a series of unexpected problems plagued ramp and ushered a change away from blindly raising clock speeds towards more functionality and more optimized functionality at more manageable clock speeds.
Clock speeds will hit 4GHz and keep rising, but not at the rate we have been accustomed to. But as the Core 2 benchmarks show, Intel has intelligently redesigned the processor to achieve significant speed improvements at existing clock speeds.
I mean weve been stuck on 2.x for ages. Whats the deal? A 4ghz quad would be frickin awesome. :confused:
If you raised the clock speed of NetBurst-based Pentium 4s (or Pentium Ds) to 4GHz, you would still not achieve the same performance as today's Conroe at 2.13GHz. Clock speed alone is not an accurate gauge of performance.
Because of increasing problems with heat density, clock speeds haven't been rising at their historical rates. A kind of brick wall was hit when the semiconductor industry moved to 90nm. At those dimensions a series of unexpected problems plagued ramp and ushered a change away from blindly raising clock speeds towards more functionality and more optimized functionality at more manageable clock speeds.
Clock speeds will hit 4GHz and keep rising, but not at the rate we have been accustomed to. But as the Core 2 benchmarks show, Intel has intelligently redesigned the processor to achieve significant speed improvements at existing clock speeds.
JoeG4
Apr 11, 03:52 AM
Whee let's all drive eco friendly subcompacts! I love cramming 4 people into a tiny hatchback! So fun and friendly! And then they .. yea so fun and friendly. :D
Cameront9
Aug 24, 12:35 AM
Not Hierarchial File System! Hierarchial MENU System!
Now, we can freely discuss the "merits" of this patent, but fact is that Apple lost, fair 'n square. If Apple thought that Creatives patent was bogus, they would have NOT paid. 100 million dollars is a lot of cash, no matter how you slice it. If the patent was bogus, and they still paid, Apple would be sending other companies a message that said "Want some cash? Sue us with bogus patents, we'll gladly pay!". No, Apple paid because they felt that they were really infringing and that if they had proceedd with the lawsuit, they would have lost a lot more than 100 million.
If it's a BS patent, why did Apple pay? Clearly, it was NOT a BS patent. True, the patent-system might be screwed up, but that is not the point of this discussion.
Alright, Menu system. But it's the same thing. You select songs (files) through groups of albums/artists/etc (folders/directories).
Of COURSE Apple was infringing on the patent if you assume it was a valid patent. I'm saying the patent never should have been granted because it's not something you can patent. I have a feeling that Apple possibly could have won this lawsuit, but it would have taken years of red tape, legal fees, etc, and they would be taking a gamble. Apple's taken gambles in the legal process before and lost (see: Microsoft GUI case). Steve doesn't want to go through that again, so he pays off Creative. Then, being Steve, he somehow uses his RDF to get Creative to join the licensing program, which has the potential to MAKE APPLE MONEY off of this deal.
Did Apple "win" this? Of course not. They're still out 100 million. But they also came out with some interesting deals that make this not a total loss.
And finally, to answer your statement in the first paragraph: This is EXACTLY why the patent system IS messed up. Because it DOES send a message of "hey we filed this patent for something blatantly obvious, give us some money" In most cases, it will be cheaper to settle. Thus companies end up using Patents, rather than products, as a money-maker.
Now, we can freely discuss the "merits" of this patent, but fact is that Apple lost, fair 'n square. If Apple thought that Creatives patent was bogus, they would have NOT paid. 100 million dollars is a lot of cash, no matter how you slice it. If the patent was bogus, and they still paid, Apple would be sending other companies a message that said "Want some cash? Sue us with bogus patents, we'll gladly pay!". No, Apple paid because they felt that they were really infringing and that if they had proceedd with the lawsuit, they would have lost a lot more than 100 million.
If it's a BS patent, why did Apple pay? Clearly, it was NOT a BS patent. True, the patent-system might be screwed up, but that is not the point of this discussion.
Alright, Menu system. But it's the same thing. You select songs (files) through groups of albums/artists/etc (folders/directories).
Of COURSE Apple was infringing on the patent if you assume it was a valid patent. I'm saying the patent never should have been granted because it's not something you can patent. I have a feeling that Apple possibly could have won this lawsuit, but it would have taken years of red tape, legal fees, etc, and they would be taking a gamble. Apple's taken gambles in the legal process before and lost (see: Microsoft GUI case). Steve doesn't want to go through that again, so he pays off Creative. Then, being Steve, he somehow uses his RDF to get Creative to join the licensing program, which has the potential to MAKE APPLE MONEY off of this deal.
Did Apple "win" this? Of course not. They're still out 100 million. But they also came out with some interesting deals that make this not a total loss.
And finally, to answer your statement in the first paragraph: This is EXACTLY why the patent system IS messed up. Because it DOES send a message of "hey we filed this patent for something blatantly obvious, give us some money" In most cases, it will be cheaper to settle. Thus companies end up using Patents, rather than products, as a money-maker.
MacVault
Sep 14, 08:31 AM
Anyone know when we might see an update to the MacBook (not MBP)???
talkingfuture
Apr 19, 07:02 AM
I think this may be one of those stories where the media make it sound much bigger than it is. A load of lawyers will make a ton of money and the two companies will come to some sort of licensing agreement or Apple will get a discount on some of the parts they buy.
Silentwave
Jul 17, 08:08 AM
Could someone please clarify, are we expecting the MacBook Pro to be updated at WWDC? I'm ready to purchase a MacBook Pro right away, but if we are fairly certain that there will be a new release in August I will wait as my current laptop is doing the job.
Does anyone want to give some odds? I know that no-one can be certain but for instance for a 25% chance I'll wait, for a 5% chance I'll just order one now.
I wouldn't give you good odds for WWDC, but you should have your update within less than a month from it.
Merom isn't out at the time of WWDC- it won't be until later in August. It is possible they may let apple take pre-orders if steve wants to really make it a massive attack at WWDC on all parts of the line charging ahead into the next generation, but you never know with him.
Of course the way things are going, for all we know there may really be PB G5s at WWDC, who knows nowadays :rolleyes:
Does anyone want to give some odds? I know that no-one can be certain but for instance for a 25% chance I'll wait, for a 5% chance I'll just order one now.
I wouldn't give you good odds for WWDC, but you should have your update within less than a month from it.
Merom isn't out at the time of WWDC- it won't be until later in August. It is possible they may let apple take pre-orders if steve wants to really make it a massive attack at WWDC on all parts of the line charging ahead into the next generation, but you never know with him.
Of course the way things are going, for all we know there may really be PB G5s at WWDC, who knows nowadays :rolleyes:
gugy
Sep 26, 11:00 AM
wow, That's really bad. Cingular is sucks like pretty much every carrier in the US.
I hope at least they have the iphone to the major carriers. Just cingular is a joke. Verizon, T mobile and Sprint need to be included if they want the iphone to be a success.
I hope at least they have the iphone to the major carriers. Just cingular is a joke. Verizon, T mobile and Sprint need to be included if they want the iphone to be a success.
zer0sum
Mar 22, 12:44 PM
I did read it. It doesn't answer why there are no viruses today, now that Mac OS has greater market share than ever, when there were viruses back when it had a much smaller market share. The market share theory is pure nonsense. It doesn't stand up to simple math.
The theory that OS X is completely secure is equally nonsense.
You definitely don't need an anti-malware solution installed right now, but it is only a matter of time.
There is a reason malware isn't prevalent and it's certainly not because there are no flaws to be leveraged into exploits.
Just look at the security fixes of 10.6.7 update released a few days ago: http://support.apple.com/kb/HT4581
Here's a list of some of the more serious 54 security fixes released
AppleScript
A format string issue existed in AppleScript Studio's generic dialog commands ("display dialog" and "display alert"). Running an AppleScript Studio-based application that allows untrusted input to be passed to a dialog may lead to an unexpected application termination or arbitrary code execution.
ATS
A heap buffer overflow issue existed in the handling of OpenType, TrueType and Type 1 fonts. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
Multiple buffer overflow issues existed in the handling of SFNT tables. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
bzip2
An integer overflow issue existed in bzip2's handling of bzip2 compressed files. Using the command line bzip2 or bunzip2 tool to decompress a bzip2 file may result in an unexpected application termination or arbitrary code execution.
ClamAV
Multiple vulnerabilities exist in ClamAV, the most serious of which may lead to arbitrary code execution. This update addresses the issues by updating ClamAV to version 0.96.5. ClamAV is distributed only with Mac OS X Server systems.
CoreText
A memory corruption issue existed in CoreText's handling of font files. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
File Quarantine
The OSX.OpinionSpy definition has been added to the malware check within File Quarantine.
ImageIO
A heap buffer overflow issue existed in ImageIO's handling of JPEG and XBM images. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.
A buffer overflow existed in libTIFF's handling of JPEG encoded TIFF images and CCITT Group 4 encoded TIFF images. Viewing a maliciously crafted TIFF image may result in an unexpected application termination or arbitrary code execution.
An integer overflow issue existed in ImageIO's handling of JPEG-encoded TIFF images. Viewing a maliciously crafted TIFF image may result in an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
Image RAW
Multiple buffer overflow issues existed in Image RAW's handling of Canon RAW images. Viewing a maliciously crafted Canon RAW image may result in an unexpected application termination or arbitrary code execution.
Installer
A URL processing issue in Install Helper may lead to the installation of an agent that contacts an arbitrary server when the user logs in. The dialog resulting from a connection failure may lead the user to believe that the connection was attempted with Apple. This issue is addressed by removing Install Helper.
Kerberos
Multiple cryptographic issues existed in MIT Kerberos 5. Only CVE-2010-1323 affects Mac OS X v10.5.
Kernel
A privilege checking issue existed in the i386_set_ldt system call's handling of call gates. A local user may be able to execute arbitrary code with system privileges. This issue is addressed by disallowing creation of call gate entries via i386_set_ldt().
libxml
A memory corruption issue existed in libxml's XPath handling. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.
A double free issue existed in libxml's handling of XPath expressions. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
Mailman
Multiple cross-site scripting issues existed in Mailman 2.1.13. These issues are addressed by updating Mailman to version 2.1.14.
PHP
PHP is updated to version 5.3.4 to address multiple vulnerabilities, the most serious of which may lead to arbitrary code execution.
QuickLook
A memory corruption issue existed in QuickLook's handling of Excel files. Downloading a maliciously crafted Excel file may lead to an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
A memory corruption issue existed in QuickLook's handling of Microsoft Office files. Downloading a maliciously crafted Microsoft Office file may lead to an unexpected application termination or arbitrary code execution.
QuickTime
Multiple memory corruption issues existed in QuickTime's handling of JPEG2000 images. Viewing a maliciously crafted JPEG2000 image with QuickTime may lead to an unexpected application termination or arbitrary code execution.
An integer overflow existed in QuickTime's handling of movie files. Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
A memory corruption issue existed in QuickTime's handling of FlashPix images. Viewing a maliciously crafted FlashPix image may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
A cross-origin issue existed in QuickTime plug-in's handling of cross-site redirects. Visiting a maliciously crafted website may lead to the disclosure of video data from another site. This issue is addressed by preventing QuickTime from following cross-site redirects.
A memory corruption issue existed in QuickTime's handling of panorama atoms in QTVR (QuickTime Virtual Reality) movie files. Viewing a maliciously crafted QTVR movie file may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
Ruby
An integer truncation issue existed in Ruby's BigDecimal class. Running a Ruby script that uses untrusted input to create a BigDecimal object may lead to an unexpected application termination or arbitrary code execution. This issue only affects 64-bit Ruby processes.
Samba
A stack buffer overflow existed in Samba's handling of Windows Security IDs. If SMB file sharing is enabled, a remote attacker may cause a denial of service or arbitrary code execution.
Subversion
Subversion servers that use the non-default "SVNPathAuthz short_circuit" mod_dav_svn configuration setting may allow unauthorized users to access portions of the repository. This issue is addressed by updating Subversion to version 1.6.13. This issue does not affect systems prior to Mac OS X v10.6.
X11
Multiple vulnerabilities existed in FreeType, the most serious of which may lead to arbitrary code execution when processing a maliciously crafted font. These issues are addressed by updating FreeType to version 2.4.3
The theory that OS X is completely secure is equally nonsense.
You definitely don't need an anti-malware solution installed right now, but it is only a matter of time.
There is a reason malware isn't prevalent and it's certainly not because there are no flaws to be leveraged into exploits.
Just look at the security fixes of 10.6.7 update released a few days ago: http://support.apple.com/kb/HT4581
Here's a list of some of the more serious 54 security fixes released
AppleScript
A format string issue existed in AppleScript Studio's generic dialog commands ("display dialog" and "display alert"). Running an AppleScript Studio-based application that allows untrusted input to be passed to a dialog may lead to an unexpected application termination or arbitrary code execution.
ATS
A heap buffer overflow issue existed in the handling of OpenType, TrueType and Type 1 fonts. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
Multiple buffer overflow issues existed in the handling of SFNT tables. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
bzip2
An integer overflow issue existed in bzip2's handling of bzip2 compressed files. Using the command line bzip2 or bunzip2 tool to decompress a bzip2 file may result in an unexpected application termination or arbitrary code execution.
ClamAV
Multiple vulnerabilities exist in ClamAV, the most serious of which may lead to arbitrary code execution. This update addresses the issues by updating ClamAV to version 0.96.5. ClamAV is distributed only with Mac OS X Server systems.
CoreText
A memory corruption issue existed in CoreText's handling of font files. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
File Quarantine
The OSX.OpinionSpy definition has been added to the malware check within File Quarantine.
ImageIO
A heap buffer overflow issue existed in ImageIO's handling of JPEG and XBM images. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.
A buffer overflow existed in libTIFF's handling of JPEG encoded TIFF images and CCITT Group 4 encoded TIFF images. Viewing a maliciously crafted TIFF image may result in an unexpected application termination or arbitrary code execution.
An integer overflow issue existed in ImageIO's handling of JPEG-encoded TIFF images. Viewing a maliciously crafted TIFF image may result in an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
Image RAW
Multiple buffer overflow issues existed in Image RAW's handling of Canon RAW images. Viewing a maliciously crafted Canon RAW image may result in an unexpected application termination or arbitrary code execution.
Installer
A URL processing issue in Install Helper may lead to the installation of an agent that contacts an arbitrary server when the user logs in. The dialog resulting from a connection failure may lead the user to believe that the connection was attempted with Apple. This issue is addressed by removing Install Helper.
Kerberos
Multiple cryptographic issues existed in MIT Kerberos 5. Only CVE-2010-1323 affects Mac OS X v10.5.
Kernel
A privilege checking issue existed in the i386_set_ldt system call's handling of call gates. A local user may be able to execute arbitrary code with system privileges. This issue is addressed by disallowing creation of call gate entries via i386_set_ldt().
libxml
A memory corruption issue existed in libxml's XPath handling. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.
A double free issue existed in libxml's handling of XPath expressions. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
Mailman
Multiple cross-site scripting issues existed in Mailman 2.1.13. These issues are addressed by updating Mailman to version 2.1.14.
PHP
PHP is updated to version 5.3.4 to address multiple vulnerabilities, the most serious of which may lead to arbitrary code execution.
QuickLook
A memory corruption issue existed in QuickLook's handling of Excel files. Downloading a maliciously crafted Excel file may lead to an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
A memory corruption issue existed in QuickLook's handling of Microsoft Office files. Downloading a maliciously crafted Microsoft Office file may lead to an unexpected application termination or arbitrary code execution.
QuickTime
Multiple memory corruption issues existed in QuickTime's handling of JPEG2000 images. Viewing a maliciously crafted JPEG2000 image with QuickTime may lead to an unexpected application termination or arbitrary code execution.
An integer overflow existed in QuickTime's handling of movie files. Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
A memory corruption issue existed in QuickTime's handling of FlashPix images. Viewing a maliciously crafted FlashPix image may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
A cross-origin issue existed in QuickTime plug-in's handling of cross-site redirects. Visiting a maliciously crafted website may lead to the disclosure of video data from another site. This issue is addressed by preventing QuickTime from following cross-site redirects.
A memory corruption issue existed in QuickTime's handling of panorama atoms in QTVR (QuickTime Virtual Reality) movie files. Viewing a maliciously crafted QTVR movie file may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
Ruby
An integer truncation issue existed in Ruby's BigDecimal class. Running a Ruby script that uses untrusted input to create a BigDecimal object may lead to an unexpected application termination or arbitrary code execution. This issue only affects 64-bit Ruby processes.
Samba
A stack buffer overflow existed in Samba's handling of Windows Security IDs. If SMB file sharing is enabled, a remote attacker may cause a denial of service or arbitrary code execution.
Subversion
Subversion servers that use the non-default "SVNPathAuthz short_circuit" mod_dav_svn configuration setting may allow unauthorized users to access portions of the repository. This issue is addressed by updating Subversion to version 1.6.13. This issue does not affect systems prior to Mac OS X v10.6.
X11
Multiple vulnerabilities existed in FreeType, the most serious of which may lead to arbitrary code execution when processing a maliciously crafted font. These issues are addressed by updating FreeType to version 2.4.3
twoodcc
Aug 31, 01:27 PM
all we can do is hope and pray
McGiord
Mar 29, 01:15 PM
CMD-X does NOT cut a file and let you move it. I am in SL right now. DOESN'T work.
Well...well
The whole cut and paste concept, as it was initially implemented, was based on how in real life one was handling documents and folders, while working on your desk. You do not cut a document to move it to another folder. In real life you move it, you drag and drop.
The undo was the most nicely implemented feature of all OS.
And yes, it was MacOS.
Well...well
The whole cut and paste concept, as it was initially implemented, was based on how in real life one was handling documents and folders, while working on your desk. You do not cut a document to move it to another folder. In real life you move it, you drag and drop.
The undo was the most nicely implemented feature of all OS.
And yes, it was MacOS.
Meandmunch
Apr 25, 07:08 PM
Other than shaving a few millimeters of the case, a few grams of weight what amount of change isn't incremental at this point?
ju5tin81
Oct 27, 09:56 AM
By getting press coverage, by being ejected, they have got what they wanted: To raise awareness of their cause.
In addition, the british press just LOVE to bring down a sucessful person/product/brand... brace yourselves for a lot of anti-apple press, now everyone knows how un-green apple are.
I was there today, and was offered a leaflet, and an organic apple, on leaving olympia tube station. They do have a valid point...
It hurt when I saw my work arrange for a broken tangerine iMac to be taken to the tip, when Dell came personally to take their broken PC...
I love apple, they could do more than simply offer to recycle their PACKAGING! Finish the job Apple. (We pay enough for the privelige)
Edit: Apple can you also put a spell check into Safari please :)
In addition, the british press just LOVE to bring down a sucessful person/product/brand... brace yourselves for a lot of anti-apple press, now everyone knows how un-green apple are.
I was there today, and was offered a leaflet, and an organic apple, on leaving olympia tube station. They do have a valid point...
It hurt when I saw my work arrange for a broken tangerine iMac to be taken to the tip, when Dell came personally to take their broken PC...
I love apple, they could do more than simply offer to recycle their PACKAGING! Finish the job Apple. (We pay enough for the privelige)
Edit: Apple can you also put a spell check into Safari please :)
skunk
Sep 14, 08:24 AM
Yes it has.It was a MacUser UK cover picture months ago.
gyrogeerloose
Apr 28, 07:03 PM
ROFL! I totally see what you're saying. Why can't people just avoid fanboyish behavior? Both companies make some great products. Both companies make bad products too. *shrugs*
I think it's a holdover from the bad old days in the mid-nineties, when Microsoft was riding high with Windows 95. Apple was at it's nadir, the common wisdom was that it was going to go under and Michael Dell said that if it were up to him, he'd sell the company and give the money back to the shareholders. Only the die-hard fans disagreed.
Fast forward fifteen years: not only did Apple survive, it has now surpassed the behemoth Microsoft in profitability. Under those circumstances, please don't complain about us diehards gloating just a little bit...
I think it's a holdover from the bad old days in the mid-nineties, when Microsoft was riding high with Windows 95. Apple was at it's nadir, the common wisdom was that it was going to go under and Michael Dell said that if it were up to him, he'd sell the company and give the money back to the shareholders. Only the die-hard fans disagreed.
Fast forward fifteen years: not only did Apple survive, it has now surpassed the behemoth Microsoft in profitability. Under those circumstances, please don't complain about us diehards gloating just a little bit...
EagerDragon
Sep 14, 07:42 PM
I'm hoping for a MBP. It'll be my first Mac. My son just started college and we were going to buy him a Mac Mini. Then I heard about new imacs coming and waited it out and I found that to be a better value than a mac mini. Well he just got it a week ago and it's great! Now I've decided to switch from Windows to Mac and will get a MBP but am waiting for the next generation. I was disappointed it didn't come last week but maybe the 24th. Isn't it unusual for Apple to have something like this on a Sunday? I hear so much about Tuesdays but as other's have said maybe the 19th. I've heard estimates of as late as January becuase of a meron shortage. I can't wait that long to switch to Mac! :)
Extemly likely it will be updated by end of the month at the latests. More than likely before 9/25. Not too worried about the numbers, Intel should have Apple in the prefered list and Apple not likely to expect to sell more than 1/2 mil of them, so they prob have plenty of chips. Likely it may have memry card reader, Meron, no latch, new gen chip for wireless (pre-n). Im not a Pro photographer, but anything that helps the photographer like better way to import or export photos and make life easier for them. All plus for you and me also. BTW welcome to the Family.
Extemly likely it will be updated by end of the month at the latests. More than likely before 9/25. Not too worried about the numbers, Intel should have Apple in the prefered list and Apple not likely to expect to sell more than 1/2 mil of them, so they prob have plenty of chips. Likely it may have memry card reader, Meron, no latch, new gen chip for wireless (pre-n). Im not a Pro photographer, but anything that helps the photographer like better way to import or export photos and make life easier for them. All plus for you and me also. BTW welcome to the Family.
soapsuds
Sep 6, 01:09 AM
3 Mbps for a 720p movie? That's actually pretty close to a typical broadband download rate... neglecting the 2 GB storage requirements, all they would have to do is add the ability to watch a video as it is being downloaded (I'm pretty sure iTunes currently doesn't do that, which seems rather stupid, although the iTunes video player is also quite clunky) to make that feasible. I would still guess that they'll only do 640x480 or something like that, because it would be "good enough" for most people. If they stick to 320x240 for movies nobody will buy them.
If they can put the menu logic into iTunes, all the "Airport Express A/V" would have do do is add an H264 decoder chip and video DAC to the current Airport Express, that would be a pretty cheap solution. I think there is already a way to plug a remote control via USB into an Airport Express and remote-control iTunes. I don't see any reason why they couldn't fit this into something roughly the same cost as the current Airport Express ($130). Have iTunes for Windows handle simple movie and music playback, have the Mac version do a more full-featured FrontRow experience. Can most current Macs encode 640x480 into H264 or at least MP4 in real time to handle the UI? I suppose they could use a more quick & dirty compression technique for the UI, perhaps something that could take advantage of the large amounts of black background.
The only sticky part is the current AirportExpress is designed to sit on your powerstrip, where an IR receiver wouldn't work. So either you need a receiver on a cord, use an R/F remote instead of IR, or turn it into a "box with a cord" design more like a cable box.
If they can put the menu logic into iTunes, all the "Airport Express A/V" would have do do is add an H264 decoder chip and video DAC to the current Airport Express, that would be a pretty cheap solution. I think there is already a way to plug a remote control via USB into an Airport Express and remote-control iTunes. I don't see any reason why they couldn't fit this into something roughly the same cost as the current Airport Express ($130). Have iTunes for Windows handle simple movie and music playback, have the Mac version do a more full-featured FrontRow experience. Can most current Macs encode 640x480 into H264 or at least MP4 in real time to handle the UI? I suppose they could use a more quick & dirty compression technique for the UI, perhaps something that could take advantage of the large amounts of black background.
The only sticky part is the current AirportExpress is designed to sit on your powerstrip, where an IR receiver wouldn't work. So either you need a receiver on a cord, use an R/F remote instead of IR, or turn it into a "box with a cord" design more like a cable box.
rhett7660
Nov 13, 05:37 PM
You're talking about some hardcore Apple supporters, well known in the community, jumping ship. It ain't a good sign.
It just says they are jumping ship from the iPhone... For some reason, 3 people jumping ship don't really stir the pot for me. For some reason I have a feeling there will be many behind them to take their place.
It just says they are jumping ship from the iPhone... For some reason, 3 people jumping ship don't really stir the pot for me. For some reason I have a feeling there will be many behind them to take their place.
iphones4evry1
Nov 13, 02:38 PM
This is becoming an epidemic of developers that are upset with Apple's App review process. I have no problem with Apple reviewing Apps, as it increases security for us users, BUT I think Apple needs to COMPLETELY overhaul their App process. There is no way in heck that it should take three months for a follow-up review of an App that they have already delayed. Three months is completely unacceptable in the rest of the world, and this looks VERY bad for Apple. Apple needs to COMPLETELY redo their completely inefficient app-review process, and get back up with the standards that the rest of the world operates on. If it took me three months to do anything, I would never have graduated college. They gave us due dates, and we did our work! It works the same way at my job. People aren't given three months to get things done. Apple gets an "F" on this one! "A day late, a penny short."
HecubusPro
Aug 28, 06:11 PM
To be fair to direzz, he said that every mac LAPTOP he bought has sucked, not every computer.
To be fair to me, that's what I meant, actually. :)
To be fair to me, that's what I meant, actually. :)
blahblah100
Mar 30, 01:35 PM
An .exe is an executable, not an application. Some people may have called them applications, but not MS. Never. Until now.
Again, you are wrong.
Again, you are wrong.
Pravius
Apr 22, 08:37 AM
You never OWNED any of this stuff. You owned the physical media, and you had an unlimited license to you. The technology is just clarifying this.
If you had actually owned it, you could have copied it as much as you wanted-- legally-- and resold the copies to others. You have been capable of doing this, but it was illegal; it also was difficult to enforce the law. Now the technology is actually starting to match your legal rights. It's actually wonderful. You are not losing anything you had legally, but the true owners (the content creators and the people who support them financially) can stop getting ripped off by criminals.
Not sure this will completely stop piracy, but it will further deter it. However if you can store it on a drive without any sort of DRM. This service will do nothing for piracy.
If you had actually owned it, you could have copied it as much as you wanted-- legally-- and resold the copies to others. You have been capable of doing this, but it was illegal; it also was difficult to enforce the law. Now the technology is actually starting to match your legal rights. It's actually wonderful. You are not losing anything you had legally, but the true owners (the content creators and the people who support them financially) can stop getting ripped off by criminals.
Not sure this will completely stop piracy, but it will further deter it. However if you can store it on a drive without any sort of DRM. This service will do nothing for piracy.
BornAgainMac
Sep 19, 06:51 PM
I was disappointed that only Disney signed up so I bought a ton of movies in the last week. Hopefully that got the attention of the other studios and sign up too. I really like the idea of downloading musics and I think HD movies will be a killer next year. Hopefully hard drives will continue to go down in price.
Most of the movies I purchased I didn't plan to purchase in DVD format. I looked at the trailer and liked it so I bought it. It is the convenience that sold me. This is revenue the studio would never receive before now.
Most of the movies I purchased I didn't plan to purchase in DVD format. I looked at the trailer and liked it so I bought it. It is the convenience that sold me. This is revenue the studio would never receive before now.
donlphi
Sep 5, 08:25 PM
I agree with everyone here who says that when Apple starts their own movie store they should also release a new Application along with it.
Playing video in iTunes is pretty bad.
They could call it iMovie... wait that won't work.
iFlix (too netflix-ee)? iPix(too pixarish)? iMedia (too micro$oftish)? nah.. just stick with iTunes... everybody knows how to use it, but fix the video playback.
Playing video in iTunes is pretty bad.
They could call it iMovie... wait that won't work.
iFlix (too netflix-ee)? iPix(too pixarish)? iMedia (too micro$oftish)? nah.. just stick with iTunes... everybody knows how to use it, but fix the video playback.
No comments:
Post a Comment