Another way to look at it is that this lost opportunity is costing them around 1 billion dollars and 1 billion can pay for a lot of development work, say on copy protection. So it may only be 4% but that 4% is still a huge amount of cash that can easily pay for development costs if then are able to nudge that number down a little as a result.
Nothing prevents the use of more conventional means of propulsion on the Mars end of things combined with the gravity well of Mars (and possibly other bodies in the area) also combined with atmospheric braking to slow the craft for orbit or a surface landing.
This type of system could be used to haul supplies for example to Mars in a relatively should period of time and supply vessels can generally under go more higher deceleration effects then vessels with crew... so they could utilize heavy atmospheric breaking over one or more passes to drop the supplies into orbit or onto the surface. Also supplies are generally a one type of thing.
The wind that sail boat use generally only blows in one direction as well yet they can sail around in all direction with enough course changes. A space craft also has the ability to use gravity well assists to sling shot them on their way and they can use solar sails to provide the push to get them into such trajectories.
Just to be clear for folks that don't know... 480p is 640 x 480 progressively scanned (not interlaced) which is still far below what PC games are generally played at.
It's kinda like expecting really good support from Apple for Mozilla when they'd rather push Safari
You do know that Safari is built using KHTML & KJS (both part of KDE) and Apple is supporting them by feeding back bug fixes, enhancements and optimizations.
Also they have made those frameworks available to other developers, outside of Safari, on Mac OS X by bundling them with the OS distribution.
Re:supporting DOC != using it as its native format
on
Apple iWork Screenshots
·
· Score: 2, Interesting
But it also has its own, native format. That could be yet another messy, proprietary format, or it could be a standard XML-based format like OASIS. Well, which is it?
Likely it is an open file format just like Keynote (v1) and likely not that greatly different from it. They just haven't publish the information yet (the product hasn't shipped yet for one).
Apple has no reason to keep it proprietary and many reasons to publish the format in the open (it helps the product if others can important/export it).
But what file format does it use natively? What it uses natively hasn't been announced yet but since the have published info about Keynote (v1) format I would expect the same information for iWorks once it gets close to shipping.
A brand new Apple XML mystery format that's theoretically importable to everywhere else but no one practically bothers to write support for? Or OASIS format, which everyone should support but few do?
You relize in many ways what you said can easily be said about OASIS.
In the real world very few folks create documents in OASIS format, it may get more and more popular or time but it isn't even close to being common yet.
In other words why should ANY product support OASIS if it isn't used much, yes a chicken-and-egg type problem but a real factor in the development decisions process.
I find Delicious Library a great product for being so new. Many customer empowering features and overall refinement. It also leverages the best of what Mac OS X has to offer developers.
If folks haven't noticed Apple has updated their Tiger page with more stuff including movies of features in action. The polish they have put on Tiger since its announcement is rather impressive (was at WWDC 2004 and have access to seeds).
One of the safety recommendations was to always insure it can reach the ISS by limiting its mission and cargo as needed. In fact that is one reason why the shuttle isn't currently being allowed to service Hubble.
Shoot Intel Hyper-Threading is not new - It looks to OS as two processors but only 1 is running at given time.
Actually both virtual CPUs in an HT system are running instructions at the same time on the same core. The intent of HT (and related implementation but differing names) is to help fill the several execution units that exist on todays CPU cores by allowing an intermixing of instructions from two (or more) execution streams (threads). Having more instructions and often nondependent instruction to choose from for scheduling can improve the utilization of the execution units. This can lead to better overall system throughput.
If the "halo" effect is just 1% of _new_ iPod owners switch to using a Mac you are looking at around 30,000 (being conservative) extra Mac sales this quarter (assuming around 3 million iPod sold this quarter). That by it self represents a 3.5% increase in Mac sales over the prior quarter.
If the numbers are closer to the 6% (as the survey appears to imply) then we are talking greater then 20% increase in Mac volumes coming from the halo affect in just one quarter (which is something like over 220 million in revenue).
This is what some company analysts are starting to see if the crunch the numbers.
Will it happen and will it continue? Who knows but I do believe at least some halo effect is and will continue to take place and it will help Apple's mac sales.
Well said in this and your other response posts...
Folks worked hard on making this product, folks with talent and likely the desire/love of making the product and this is a direct slap in the face to those folks.
Please don't freeload. Respect the work of others. This is all stuff you should have learned in kindergarden...
The referenced item from Intego was about a theoretical Trojan horse that no one appears to have actually taken advantage of to do evil (symantec's take on it. Also a detailed look at the "security alert" can be found here.
Anyway yes any storage device could have a Trojan, etc. dropped onto it. Yet in the case of the iPod and other storage devices (at least under Mac OS X) just because such a beasts exists on the storage device doesn't mean that once connected it spreads (no auto-run of code on mounted devices is supported on Mac OS X without third-party tools).
Not much can protect one from a Trojan if the victim cannot recognize it for what it is (sure virus scanners may hit on it if it is a known trojan).
Anyway the real issue is mostly about users dropping company data onto their iPod, etc. (likely unencrypted) and then walking out the door and possibly losing it...
Slashdot Mirror
LMAO
It looks like wikipedia has a servicable definition for trade secret that I won't bother duplicating here.
Another way to look at it is that this lost opportunity is costing them around 1 billion dollars and 1 billion can pay for a lot of development work, say on copy protection. So it may only be 4% but that 4% is still a huge amount of cash that can easily pay for development costs if then are able to nudge that number down a little as a result.
Révolution!
For those that don't already know is that autovectorization is being worked on for GCC by folks from IBM and others.
GCC vectorizatoin project (site seem offline atm) but the abstract from a recent GCC summit is up.
Autovectorization Talk (google html view of pdf)
Just pick a few items out ...
Apple provides source code for some of their vector libraries
I must be sick or at least a geek... I find this darn funny :-)
Nothing prevents the use of more conventional means of propulsion on the Mars end of things combined with the gravity well of Mars (and possibly other bodies in the area) also combined with atmospheric braking to slow the craft for orbit or a surface landing.
This type of system could be used to haul supplies for example to Mars in a relatively should period of time and supply vessels can generally under go more higher deceleration effects then vessels with crew... so they could utilize heavy atmospheric breaking over one or more passes to drop the supplies into orbit or onto the surface. Also supplies are generally a one type of thing.
The wind that sail boat use generally only blows in one direction as well yet they can sail around in all direction with enough course changes. A space craft also has the ability to use gravity well assists to sling shot them on their way and they can use solar sails to provide the push to get them into such trajectories.
Just to be clear for folks that don't know... 480p is 640 x 480 progressively scanned (not interlaced) which is still far below what PC games are generally played at.
For related info on HDTV resolutions... wikipedia
Oh I should point out that WebCore is exposed to developers via the Web Kit framework.
Just because the didn't pick your pet horse...
It's kinda like expecting really good support from Apple for Mozilla when they'd rather push Safari
You do know that Safari is built using KHTML & KJS (both part of KDE) and Apple is supporting them by feeding back bug fixes, enhancements and optimizations.
Also they have made those frameworks available to other developers, outside of Safari, on Mac OS X by bundling them with the OS distribution.
WebCore
But it also has its own, native format. That could be yet another messy, proprietary format, or it could be a standard XML-based format like OASIS. Well, which is it?
Likely it is an open file format just like Keynote (v1) and likely not that greatly different from it. They just haven't publish the information yet (the product hasn't shipped yet for one).
Keynote (v1) technote
Apple has no reason to keep it proprietary and many reasons to publish the format in the open (it helps the product if others can important/export it).
Similar name and features but a totally different and new code base.
But what file format does it use natively?
What it uses natively hasn't been announced yet but since the have published info about Keynote (v1) format I would expect the same information for iWorks once it gets close to shipping.
A brand new Apple XML mystery format that's theoretically importable to everywhere else but no one practically bothers to write support for? Or OASIS format, which everyone should support but few do?
You relize in many ways what you said can easily be said about OASIS.
In the real world very few folks create documents in OASIS format, it may get more and more popular or time but it isn't even close to being common yet.
In other words why should ANY product support OASIS if it isn't used much, yes a chicken-and-egg type problem but a real factor in the development decisions process.
Just want to throw a kudo their way.
I find Delicious Library a great product for being so new. Many customer empowering features and overall refinement. It also leverages the best of what Mac OS X has to offer developers.
Good job and keep it up!
If folks haven't noticed Apple has updated their Tiger page with more stuff including movies of features in action. The polish they have put on Tiger since its announcement is rather impressive (was at WWDC 2004 and have access to seeds).
http://www.apple.com/macosx/tiger
Now this is just cool...
b ook20050111.jpg
http://images.apple.com/ipodshuffle/images/indexi
Don't go to the store that is slower... but yeah Apple.com is getting hammered big time at the moment.
iWork
Mac mini
iPod shuffle
Final Cut Express (new version)
iLife '05
Tiger iChat ;-)
One of the safety recommendations was to always insure it can reach the ISS by limiting its mission and cargo as needed. In fact that is one reason why the shuttle isn't currently being allowed to service Hubble.
Shoot Intel Hyper-Threading is not new - It looks to OS as two processors but only 1 is running at given time.
Actually both virtual CPUs in an HT system are running instructions at the same time on the same core. The intent of HT (and related implementation but differing names) is to help fill the several execution units that exist on todays CPU cores by allowing an intermixing of instructions from two (or more) execution streams (threads). Having more instructions and often nondependent instruction to choose from for scheduling can improve the utilization of the execution units. This can lead to better overall system throughput.
You hit it on the head...
If the "halo" effect is just 1% of _new_ iPod owners switch to using a Mac you are looking at around 30,000 (being conservative) extra Mac sales this quarter (assuming around 3 million iPod sold this quarter). That by it self represents a 3.5% increase in Mac sales over the prior quarter.
If the numbers are closer to the 6% (as the survey appears to imply) then we are talking greater then 20% increase in Mac volumes coming from the halo affect in just one quarter (which is something like over 220 million in revenue).
This is what some company analysts are starting to see if the crunch the numbers.
Will it happen and will it continue? Who knows but I do believe at least some halo effect is and will continue to take place and it will help Apple's mac sales.
Well said in this and your other response posts...
Folks worked hard on making this product, folks with talent and likely the desire/love of making the product and this is a direct slap in the face to those folks.
Please don't freeload. Respect the work of others. This is all stuff you should have learned in kindergarden...
Don't worry folks you can still get your pr0n with out getting a social dease...
www.asciipr0n.com
The referenced item from Intego was about a theoretical Trojan horse that no one appears to have actually taken advantage of to do evil (symantec's take on it. Also a detailed look at the "security alert" can be found here.
Anyway yes any storage device could have a Trojan, etc. dropped onto it. Yet in the case of the iPod and other storage devices (at least under Mac OS X) just because such a beasts exists on the storage device doesn't mean that once connected it spreads (no auto-run of code on mounted devices is supported on Mac OS X without third-party tools).
Not much can protect one from a Trojan if the victim cannot recognize it for what it is (sure virus scanners may hit on it if it is a known trojan).
Anyway the real issue is mostly about users dropping company data onto their iPod, etc. (likely unencrypted) and then walking out the door and possibly losing it...