Right now, Apple has about 80% of the personal digital music player market. That means that most people who want an iPod already have one The new touch screen design may be a way to entice existing iPod owners who don't want to buy a look-alike replacement for their existing iPod.
I stopped using IE many moons ago for one reason... security. It's the same reason why I use FireFox at work and run Safari at home. As far as features go I like tab browrsing etc. but I don't feel safe running IE on Windows.
I think Microsoft is noticing that the open source movement is not a fade. They were big proponents of XML based web services and now with them supporting XML document formats for Office they are finally giving users a choice. So, in the future instead of saying.NET/J2EE or Office/OpenOffice people can say both. They might not gain market share with this strategy but they might loose less in the long run.
Microsoft should by Apple and put Windows on Macs. Apple designs great hardware and this move would allow Microsoft to counteract the whimpering from Dell and HP by offering quality hardware as a Windows value add. The iPod line could be easy converted to play WMAs and the purchase would give Microsoft an instant launch into the online music business. If Microsoft decided to support OS X then Microsoft's Mac BU division could provide more applications to needy Mac users. This would also be a great defense against Linux desktop users.
JUST KIDDING!!!
While I would like purchase a G5 Powerbook I'm kind of glad that my G4 Powerbook is not totally obsolete yet. I bought one of the original 17" Powebooks about 3 years ago and it's still not that much slower then the current line. I didn't expect to have my current laptop for this long but there's nothing to upgrade to. On the other hand, I did purchase a G5 iMac 3 months ago.
Professionally I'm Java developer but in my spare time I create computer languages primality in C++. My main argument is that large book that document APIs seems to be dated since nearly all of that material is available on the web. As I mentioned, I have a lot of UNIX, Win32 and Java books but I find myself using the Internet more then those books.
I'll give you an example, I bought a book on pthreads when I prototyping a virtual machine design. The book was about 2 years old and the examples in the book were outdated; the functions syntax had changed. I has able to find working examples and better documentation on the Internet. That being said, this is just how I find my information many of my colleagues still prefer books for reference material.
It's good to know that the UNIX APIs are being updated. The major revisions that I noticed were IPv6 and as you mentioned 64-bit support.
Another way of looking at this... with so such content available on the Internet for free is there a real value in buying books that document APIs? I've noticed that most of the books that I buy today are about software development methologies i.e. TDD, Agile, re-factoring etc. I tend to go to the Internet for find the answers to implementing detail and view APIs.
Back in the day I did a lot of programming against specific operation system API such as Windows and UNIX and had the classic books for each environment. Now that programming environments such as Java and C# exist most of those book just gathering dust. How the UNIX API changed that much since 1993? I have huge book on Win32, MFC and UNIX programming that today are just take up space.
I bought a G5 iMac about 4 months ago because I thought Apples future applications would demand a G5 processor. I also have a 17" G4 Powerbook that I've had for about 3+ years. I'm kicking myself for buying this worthless G5 iMac now!
Slashdot Mirror
When the computer gets warm does it give off that seasonal smell of pumpkin pie?
This concept was stolen from War Games "...new data encryption algorithms" and two teenagers almost started WW3.
Right now, Apple has about 80% of the personal digital music player market. That means that most people who want an iPod already have one The new touch screen design may be a way to entice existing iPod owners who don't want to buy a look-alike replacement for their existing iPod.
I stopped using IE many moons ago for one reason... security. It's the same reason why I use FireFox at work and run Safari at home. As far as features go I like tab browrsing etc. but I don't feel safe running IE on Windows.
I think Microsoft is noticing that the open source movement is not a fade. They were big proponents of XML based web services and now with them supporting XML document formats for Office they are finally giving users a choice. So, in the future instead of saying .NET/J2EE or Office/OpenOffice people can say both. They might not gain market share with this strategy but they might loose less in the long run.
Microsoft should by Apple and put Windows on Macs. Apple designs great hardware and this move would allow Microsoft to counteract the whimpering from Dell and HP by offering quality hardware as a Windows value add. The iPod line could be easy converted to play WMAs and the purchase would give Microsoft an instant launch into the online music business. If Microsoft decided to support OS X then Microsoft's Mac BU division could provide more applications to needy Mac users. This would also be a great defense against Linux desktop users. JUST KIDDING!!!
While I would like purchase a G5 Powerbook I'm kind of glad that my G4 Powerbook is not totally obsolete yet. I bought one of the original 17" Powebooks about 3 years ago and it's still not that much slower then the current line. I didn't expect to have my current laptop for this long but there's nothing to upgrade to. On the other hand, I did purchase a G5 iMac 3 months ago.
Professionally I'm Java developer but in my spare time I create computer languages primality in C++. My main argument is that large book that document APIs seems to be dated since nearly all of that material is available on the web. As I mentioned, I have a lot of UNIX, Win32 and Java books but I find myself using the Internet more then those books.
I'll give you an example, I bought a book on pthreads when I prototyping a virtual machine design. The book was about 2 years old and the examples in the book were outdated; the functions syntax had changed. I has able to find working examples and better documentation on the Internet. That being said, this is just how I find my information many of my colleagues still prefer books for reference material.
It's good to know that the UNIX APIs are being updated. The major revisions that I noticed were IPv6 and as you mentioned 64-bit support.
I'd write a longer response but I've exceeded my 2.5 hours of personal Internet usage. I guess it's back to IM and IRC now.
Another way of looking at this... with so such content available on the Internet for free is there a real value in buying books that document APIs? I've noticed that most of the books that I buy today are about software development methologies i.e. TDD, Agile, re-factoring etc. I tend to go to the Internet for find the answers to implementing detail and view APIs.
Back in the day I did a lot of programming against specific operation system API such as Windows and UNIX and had the classic books for each environment. Now that programming environments such as Java and C# exist most of those book just gathering dust. How the UNIX API changed that much since 1993? I have huge book on Win32, MFC and UNIX programming that today are just take up space.
I bought a G5 iMac about 4 months ago because I thought Apples future applications would demand a G5 processor. I also have a 17" G4 Powerbook that I've had for about 3+ years. I'm kicking myself for buying this worthless G5 iMac now!