The systems in question don't actually store your fingerprint, they store a hash (that should be relatively hard to reverse) based on some finger print information.
If you think about it, the 20% of MSRP thing is good for developers; Amazon is going to maximize their return, at the same time they're maximizing the developer's return, which is *at least* 70% of whatever Amazon is getting. If Amazon lowers or raises the price, it's because they expect a greater return (which means you'll get a greater return) and to be fair, they're probably better at setting a price to make the maximum amount of money than your average Indie developer. This means the 20% MSRP just means you'll get a larger cut than 70% if Amazon thinks they can make a killing slashing the price.
The only way you're going to get screwed is that if Amazon decides having your application priced in an uncompetitive way is going to maximize their return on another app. This is more of a danger than anything, because they might raise the prices of all competing apps to make one in particular seem like a "bargain" at the same time they advertise the hell out of it.
The compressors you list are dictionary compressors, which would not work well on the kind of data that the entropy encoder deals with in JPEG, as there are not many commonly repeating sequences of symbols; zeros are already run length encoded and these are the only symbols that repeat in such a fashion. There are however individual symbols that repeat with a high frequency, making this an ideal job for arithmetic or Huffman codes of which JPEG supports both, but mainly only the latter are used due to patent concerns in earlier years.
You might want to look into the NDK on Android. It's perfectly possible to port a runtime written in C/C++ to Android and then use that to run your python code.
They may not need to learn that much if Panasonic uses OpenGL 2.0 ES for graphics and an ARM core, because there are a lot of people who already develop games for phones that have just that.
Yes, they didn't understand economics on Easter Island and they completely managed to run out of a finite and slowly renewing resource. If they had just known basic economics, magically they wouldn't have run out.
No, all you must do is turn up. If you want you can put an empty ballot in, or write a diatribe on the back, or as many of our younger citizens do, draw a massive dick and balls on it.
Only attendance is compulsory, you don't actually have to cast a valid ballot.
They don't really need a particular project in mind, they have the cash at hand. Maybe they just want the option in their back pocket so they aren't backed into a corner.
He's lied about being sterile to try and get out of paternity and he ripped the Woz off a few grand back by lying even before they started Apple. So he is most definitely a liar and a douche, but the question is, is he lying this time?
Yes, but if CSIRO hadn't come up with the technology and some corporation had, we'd be paying the corporate R&D costs not to mention the royalties they imposed on other companies, which would be likely higher than what CSIRO are asking.
Oddly enough, STL contains a bsearch algorithm that works on variable length arrays and generates code which is pretty damn optimal. It also contains a highly optimized quicksort implementation (along with other sorting and inserting algorithms) that you can use to keep your array sorted. However, even the standard vector operations compile down to pretty much raw pointers if you use iterators, so you can use quicksort/bsearch with no extra penalty on a vector and all the work is done for you.
So it sounds awfully what you're saying is absolute horse-shit.
It's illegal to sell, publicly show or distribute, but it's legal to bring into the country and possess for personal use. The problem with electronic media though is that you only need one copy to be be able to distribute it, so it's very hard to prove that you don't intend to.
The best cut and paste UI of any mobile device? Windows Mobile has *always* done it (and done it better) despite the rest of its UI being a crime against ergonomics. In fact, most Android phones also do it better.
While this would be damn convoluted for an intentional leak (which is why I doubt it is), the idea that they would leak hardware doesn't seem too far fetched when you compare the 3GS against the flagship phones coming out from Apple's major competitors, with their much higher resolution screens, bigger batteries and faster processors. The 3GS when it hit wasn't competitive with a lot of other phones in these areas already, so now it's further behind.
Apple doesn't have the software advantage they did early on, or the "wow" factor from the initial launch, so they have to show they have competitive hardware is in the pipe or people might not bother waiting.
I won't argue that law is complex (and that it is reasonable for it to be so), but creating software can be several orders of a magnitude more complicated than the interpretation or even drafting of legislation. 1100 pages isn't that large for a big project software specification, let alone the actual source code which often runs into the 10s or 100s of millions of lines and can take thousands of people (not just programmers) several years to complete.
It sounds an awful lot like the only difference is that Apple was happier to save money by using good technology that was developed outside of the company. That's because Apple doesn't think of itself as a software company, they're a whole widget company and anything that will help them build a better widget using less development resources is fine by them.
I believe what the OP meant is that plain C can be pretty dangerous, even in experienced hands. But so are explosives and there are times when they're the best tool for the job.
As a side note, Java and.NET run well on a lot smaller systems these days. The.NET micro framework actually runs on devices with as low as 64K of RAM relatively well. Like anything, you trade safety for performance, but if you have performance to spare then safety isn't a bad way to spend it.
Slashdot Mirror
The systems in question don't actually store your fingerprint, they store a hash (that should be relatively hard to reverse) based on some finger print information.
If you think about it, the 20% of MSRP thing is good for developers; Amazon is going to maximize their return, at the same time they're maximizing the developer's return, which is *at least* 70% of whatever Amazon is getting. If Amazon lowers or raises the price, it's because they expect a greater return (which means you'll get a greater return) and to be fair, they're probably better at setting a price to make the maximum amount of money than your average Indie developer. This means the 20% MSRP just means you'll get a larger cut than 70% if Amazon thinks they can make a killing slashing the price.
The only way you're going to get screwed is that if Amazon decides having your application priced in an uncompetitive way is going to maximize their return on another app. This is more of a danger than anything, because they might raise the prices of all competing apps to make one in particular seem like a "bargain" at the same time they advertise the hell out of it.
The compressors you list are dictionary compressors, which would not work well on the kind of data that the entropy encoder deals with in JPEG, as there are not many commonly repeating sequences of symbols; zeros are already run length encoded and these are the only symbols that repeat in such a fashion. There are however individual symbols that repeat with a high frequency, making this an ideal job for arithmetic or Huffman codes of which JPEG supports both, but mainly only the latter are used due to patent concerns in earlier years.
The main processor in the Wii is a PowerPC processor, not an ARM though.
You might want to look into the NDK on Android. It's perfectly possible to port a runtime written in C/C++ to Android and then use that to run your python code.
That's 4Gbps per bus line, apparently. The card has a 256bit bus, which works out at exactly 128GB/s.
So you're saying God hacked up a sky-box?
They may not need to learn that much if Panasonic uses OpenGL 2.0 ES for graphics and an ARM core, because there are a lot of people who already develop games for phones that have just that.
Or you know, it could be this well researched study is more credible than your unsupported assertion on slashdot. Just saying.
Yes, they didn't understand economics on Easter Island and they completely managed to run out of a finite and slowly renewing resource. If they had just known basic economics, magically they wouldn't have run out.
No, all you must do is turn up. If you want you can put an empty ballot in, or write a diatribe on the back, or as many of our younger citizens do, draw a massive dick and balls on it.
Only attendance is compulsory, you don't actually have to cast a valid ballot.
They don't really need a particular project in mind, they have the cash at hand. Maybe they just want the option in their back pocket so they aren't backed into a corner.
He's lied about being sterile to try and get out of paternity and he ripped the Woz off a few grand back by lying even before they started Apple. So he is most definitely a liar and a douche, but the question is, is he lying this time?
It always seemed like a pretty simple an effective way to reduce fuel consumption to me.
Yes, but if CSIRO hadn't come up with the technology and some corporation had, we'd be paying the corporate R&D costs not to mention the royalties they imposed on other companies, which would be likely higher than what CSIRO are asking.
Oddly enough, STL contains a bsearch algorithm that works on variable length arrays and generates code which is pretty damn optimal. It also contains a highly optimized quicksort implementation (along with other sorting and inserting algorithms) that you can use to keep your array sorted. However, even the standard vector operations compile down to pretty much raw pointers if you use iterators, so you can use quicksort/bsearch with no extra penalty on a vector and all the work is done for you.
So it sounds awfully what you're saying is absolute horse-shit.
It's illegal to sell, publicly show or distribute, but it's legal to bring into the country and possess for personal use. The problem with electronic media though is that you only need one copy to be be able to distribute it, so it's very hard to prove that you don't intend to.
How many money-shots per Library of Congress?
The best cut and paste UI of any mobile device? Windows Mobile has *always* done it (and done it better) despite the rest of its UI being a crime against ergonomics. In fact, most Android phones also do it better.
While this would be damn convoluted for an intentional leak (which is why I doubt it is), the idea that they would leak hardware doesn't seem too far fetched when you compare the 3GS against the flagship phones coming out from Apple's major competitors, with their much higher resolution screens, bigger batteries and faster processors. The 3GS when it hit wasn't competitive with a lot of other phones in these areas already, so now it's further behind.
Apple doesn't have the software advantage they did early on, or the "wow" factor from the initial launch, so they have to show they have competitive hardware is in the pipe or people might not bother waiting.
What about health care, where Europeans generally have both more protection and cheaper products?
But Mickey Mouse is a lobbyist for copyright extension!
I won't argue that law is complex (and that it is reasonable for it to be so), but creating software can be several orders of a magnitude more complicated than the interpretation or even drafting of legislation. 1100 pages isn't that large for a big project software specification, let alone the actual source code which often runs into the 10s or 100s of millions of lines and can take thousands of people (not just programmers) several years to complete.
It sounds an awful lot like the only difference is that Apple was happier to save money by using good technology that was developed outside of the company. That's because Apple doesn't think of itself as a software company, they're a whole widget company and anything that will help them build a better widget using less development resources is fine by them.
I believe what the OP meant is that plain C can be pretty dangerous, even in experienced hands. But so are explosives and there are times when they're the best tool for the job.
As a side note, Java and .NET run well on a lot smaller systems these days. The .NET micro framework actually runs on devices with as low as 64K of RAM relatively well. Like anything, you trade safety for performance, but if you have performance to spare then safety isn't a bad way to spend it.