Nokia have already licensed Microsoft's "Plays4Sure" Janus DRM and Media Transfer Protocol. Don't think they are going to be making anything compatible with iTunes. I don't think Apple wants them to either.
You don't have to keep paying Napster forever. If some other company comes up with a better deal you can just export a text file of all your songs, cancel your Napster subscription, sign up for a new subscription with the other company, and redownload the same songs.
You havn't lost anything, because you never bought anything to begin with, but you get to listen to hundreds of thousands of tracks during the period you are subscribed.
If you buy from iTunes you are still locked in. You only have access the the music while Apple are still around producing iPods, still updating iTunes to support the operating system de jour, and still operating their iTunes activation server so you can authenticate your iTunes account.
Its probably unlikely that Apple will disappear entirely, but you can't be certain what will happen 30 years down the line.
It is however likely that there will be Music subscription services of one form or another that you can use.
iTunes also makes it your responsibility to maintain your digital copies indefinatly. Napster lets you redownload or stream any file at any time on a number of machines.
They are pulling a lot of stuff back into usermode for Longhorn. USB device drivers will be usermode, GDI will be software rendered in usermode, the new unified audio architechture is usermode. Basically only drivers that need to access hardware registers directly will remain in kernel mode. They are also changing the driver model to make writing drivers easier, so individual drivers do not have to reimplement plug and play and power management support etc. I guess they think that hardware performance has improved enough that it is worth sacrificing speed for stability.
Check out this recent video discussing Microsofts "Singularity" research project works in this way. <URL:http://channel9.msdn.com/ShowPost.aspx? PostID =68302>
Microsoft already tried that "Smart Displays", wasn't very successful. Essentially the device becomes a paperweight if you go out of wireless range. There also wasn't enough bandwidth to play games or watch movies over the wireless connection.
Smart displays ran using RDP, which is far less bandwidth intensive and more responsive than VNC used by "Apple Remote Desktop".
It says the widget gets its permissions from it.plist file. That file is inside the widget bundle so it can be modified by the widget without asking for elevated permissions.
If the widget is added without requiring permissions, but as it's first it act modifies its own plist file, the next time dashboard is run it is given permissions without asking the user since it is already added to the dashboard.
I don't honestly believe that any more. Sure they make a lot on iPods, but surely they make more money selling Tiger for $129 and iLife for $79 than selling a Mac mini with both included for $499. I can't imagine theres a lot of margins on a $291 PC.
Apples major selling point is now its software, the operating systems, and professional creative software. It's the OS people are after, not the hardware.
The only parts running in kernel space are the directx interfaces and the new driver model. Most of the low level parts of Avalon are in milcore.dll a usermode library that renders through directx. The higher level Avalon libraries are all managed code.
The've actually removed a lot of the existing kernel mode code. All previous directx interfaces are now emulated through directx 9, and GDI is now back in user mode and no longer hardware accelerated.
A driver writer now only needs to create a directx9 driver, which removes a lot of the complexity.
Thats just for running existing Win32 applications at higher dpis. The new display platform, Avalon, is fully vector based so new applications will scale much more smoothly.
Actually its because of WinHEC, the hardware engineering conference, where they gave the driver writers all the information about the new driver model etc. The date for WinHEC was set long before the release date for Tiger was annouced. WinHEC was going to be the last week in April while Tiger was still the only set for the first half of 2005.
Well it looks like they are attacking this from both ends. Getting the printer manufacturers to include a Metro processing engine in their firmwares. If there are any advantages to using Metro over PDF, which I'm not sure there are so far, you could have print shops asking for content in Metro format instead.
1: Metro is a subset of the new Longhorn display model Avalon. Avalon renders directly on the graphics card through DirectX9. 2: See 1: and the Longhorn shell makes much more use of document thumbnails instead of icons. 3: See 1: A metro document uses the same objects and semantics as a new Windows user interface layout. 4: - Possibly 5: Metro is the new print spooler format for Longhorn. All printed documents are automatically metro documents sent to a printer.
This is not being designed as a replacement for the Word file format, and you will not need to use word to create content in it. It is going to be the new spooler format on Windows, that means every application that can print will be creating Metro documents behind the scenes. For evey program that can print you will be able to "Save as Metro" in the same way that you can "Save as PDF" from the print dialog on OSX.
If Microsoft is successful at getting printer manufacturers to include in their embedded document processors with a renderer for this format you could well see print shops accepting Metro documents in addition to PDFs.
It's WinHEC, Windows Hardware Engineering Conference, they are making lots of announcements regarding 64bit Windows, Longhorn etc and the press is reporting on them. WinHEC happens every year and the date for WinHEC was set long before Tiger's release date was annouced.
They can't make it too difficult to render Metro documents as they are expecting all the printer manufacturers to embed a Metro rendering engine in all their large scale printers. All existing windows applications that can print will be able to create Metro documents. It will be easy to read Metro documents on other platforms since they are just XML, images and fonts wrapped up in a Zip archive.
People will still use Adobe tools to create content. But when they go to print they will be able to create Metro documents, in the same way that printing on OSX creates PDF documents. Even if they decide not to support it directly Adobe cannot prevent people from exporting to Metro without also sabotageing their ability to print from the Windows versions of their applications. Everything that anyone prints from any application will be turned into a metro document by the print spooler.
If you store your data in a format to which you have the specification, how can they prevent you from using the specification to read the data from your own files later on?
Well you know the OSX display system is based on PDF right? So Preview itself is not rendering the PDF, it is just reading the data from the file and passing it to Quartz the systems display framework.
Windows display system is currently based on GDI, so any pdf renderer on windows must read the pdf, and then calculate how to draw the equivelent image using GDI commands, a much slower process. You couldn't port Preview to Windows without also porting Quartz, and then it wouldn't really be Windows anymore.
Windows can render WMF and EMF files really fast because those formats are basically a set of GDI operations streamed to a file.
This Metro format will have the same benifits on Windows as PDF does on OSX, Metro is based on Avalon and XAML, which will be built into Windows as the presentation model.
Except this was the antivirus software, a file system filter driver running in kernel mode. Its not a matter of one process taking up more resources, it was happening with kernel threads running at a high priority.
Who would you expect to write one if an exploit was found that did need an update? BeOS is unsupported.
How many security researchers do you think are still actively trying to pick holes in it? How can you be sure there isn't a buffer overrun in an image processing library used by NetPositive that no one has bothered to find.
Slashdot Mirror
Thief Of Time
Nokia have already licensed Microsoft's "Plays4Sure" Janus DRM and Media Transfer Protocol. Don't think they are going to be making anything compatible with iTunes. I don't think Apple wants them to either.
You don't have to keep paying Napster forever. If some other company comes up with a better deal you can just export a text file of all your songs, cancel your Napster subscription, sign up for a new subscription with the other company, and redownload the same songs.
You havn't lost anything, because you never bought anything to begin with, but you get to listen to hundreds of thousands of tracks during the period you are subscribed.
If you buy from iTunes you are still locked in. You only have access the the music while Apple are still around producing iPods, still updating iTunes to support the operating system de jour, and still operating their iTunes activation server so you can authenticate your iTunes account.
Its probably unlikely that Apple will disappear entirely, but you can't be certain what will happen 30 years down the line.
It is however likely that there will be Music subscription services of one form or another that you can use.
iTunes also makes it your responsibility to maintain your digital copies indefinatly. Napster lets you redownload or stream any file at any time on a number of machines.
You are right that longhorn componants are no longer built on .Net, but the WinFX API and the .Net framework 2.0 will be included in Longhorn out of the box.l ic.windows.developer.winfx.sdk/msg/d477a0bc7d4a69a 8
http://groups-beta.google.com/group/microsoft.pub
They are pulling a lot of stuff back into usermode for Longhorn. USB device drivers will be usermode, GDI will be software rendered in usermode, the new unified audio architechture is usermode. Basically only drivers that need to access hardware registers directly will remain in kernel mode.
They are also changing the driver model to make writing drivers easier, so individual drivers do not have to reimplement plug and play and power management support etc. I guess they think that hardware performance has improved enough that it is worth sacrificing speed for stability.
And now with a clickable link.0 2
http://channel9.msdn.com/ShowPost.aspx?PostID=683
Check out this recent video discussing Microsofts "Singularity" research project works in this way.? PostID =68302>
<URL:http://channel9.msdn.com/ShowPost.aspx
Well I hope that in the process they come up with an improvement for VNC. Coz its no where near fast enough at the moment.
Microsoft already tried that "Smart Displays", wasn't very successful. Essentially the device becomes a paperweight if you go out of wireless range. There also wasn't enough bandwidth to play games or watch movies over the wireless connection.
Smart displays ran using RDP, which is far less bandwidth intensive and more responsive than VNC used by "Apple Remote Desktop".
It says the widget gets its permissions from it .plist file. That file is inside the widget bundle so it can be modified by the widget without asking for elevated permissions.
If the widget is added without requiring permissions, but as it's first it act modifies its own plist file, the next time dashboard is run it is given permissions without asking the user since it is already added to the dashboard.
Thats the way it seems to work anyway.
I don't honestly believe that any more. Sure they make a lot on iPods, but surely they make more money selling Tiger for $129 and iLife for $79 than selling a Mac mini with both included for $499.
I can't imagine theres a lot of margins on a $291 PC.
Apples major selling point is now its software, the operating systems, and professional creative software. It's the OS people are after, not the hardware.
The only parts running in kernel space are the directx interfaces and the new driver model.
Most of the low level parts of Avalon are in milcore.dll a usermode library that renders through directx. The higher level Avalon libraries are all managed code.
The've actually removed a lot of the existing kernel mode code. All previous directx interfaces are now emulated through directx 9, and GDI is now back in user mode and no longer hardware accelerated.
A driver writer now only needs to create a directx9 driver, which removes a lot of the complexity.
Thats just for running existing Win32 applications at higher dpis. The new display platform, Avalon, is fully vector based so new applications will scale much more smoothly.
Actually its because of WinHEC, the hardware engineering conference, where they gave the driver writers all the information about the new driver model etc.
The date for WinHEC was set long before the release date for Tiger was annouced. WinHEC was going to be the last week in April while Tiger was still the only set for the first half of 2005.
Well it looks like they are attacking this from both ends. Getting the printer manufacturers to include a Metro processing engine in their firmwares.
If there are any advantages to using Metro over PDF, which I'm not sure there are so far, you could have print shops asking for content in Metro format instead.
1: Metro is a subset of the new Longhorn display model Avalon. Avalon renders directly on the graphics card through DirectX9.
2: See 1: and the Longhorn shell makes much more use of document thumbnails instead of icons.
3: See 1: A metro document uses the same objects and semantics as a new Windows user interface layout.
4: - Possibly
5: Metro is the new print spooler format for Longhorn. All printed documents are automatically metro documents sent to a printer.
Looks like they are already well on their way.
This is not being designed as a replacement for the Word file format, and you will not need to use word to create content in it. It is going to be the new spooler format on Windows, that means every application that can print will be creating Metro documents behind the scenes. For evey program that can print you will be able to "Save as Metro" in the same way that you can "Save as PDF" from the print dialog on OSX.
If Microsoft is successful at getting printer manufacturers to include in their embedded document processors with a renderer for this format you could well see print shops accepting Metro documents in addition to PDFs.
It's WinHEC, Windows Hardware Engineering Conference, they are making lots of announcements regarding 64bit Windows, Longhorn etc and the press is reporting on them. WinHEC happens every year and the date for WinHEC was set long before Tiger's release date was annouced.
The format doesn't need to be cracked. It's already fully documented.
They can't make it too difficult to render Metro documents as they are expecting all the printer manufacturers to embed a Metro rendering engine in all their large scale printers.
All existing windows applications that can print will be able to create Metro documents.
It will be easy to read Metro documents on other platforms since they are just XML, images and fonts wrapped up in a Zip archive.
People will still use Adobe tools to create content. But when they go to print they will be able to create Metro documents, in the same way that printing on OSX creates PDF documents.
Even if they decide not to support it directly Adobe cannot prevent people from exporting to Metro without also sabotageing their ability to print from the Windows versions of their applications.
Everything that anyone prints from any application will be turned into a metro document by the print spooler.
If you store your data in a format to which you have the specification, how can they prevent you from using the specification to read the data from your own files later on?
Well you know the OSX display system is based on PDF right? So Preview itself is not rendering the PDF, it is just reading the data from the file and passing it to Quartz the systems display framework.
Windows display system is currently based on GDI, so any pdf renderer on windows must read the pdf, and then calculate how to draw the equivelent image using GDI commands, a much slower process. You couldn't port Preview to Windows without also porting Quartz, and then it wouldn't really be Windows anymore.
Windows can render WMF and EMF files really fast because those formats are basically a set of GDI operations streamed to a file.
This Metro format will have the same benifits on Windows as PDF does on OSX, Metro is based on Avalon and XAML, which will be built into Windows as the presentation model.
Except this was the antivirus software, a file system filter driver running in kernel mode. Its not a matter of one process taking up more resources, it was happening with kernel threads running at a high priority.
Who would you expect to write one if an exploit was found that did need an update? BeOS is unsupported.
How many security researchers do you think are still actively trying to pick holes in it?
How can you be sure there isn't a buffer overrun in an image processing library used by NetPositive that no one has bothered to find.