The problem with supporting all frequency bands is not the availability of hardware to decode them, it's that consumers have gotten used to their nice thin devices.
Enough metal to wire up antennas even just for the (ridiculously long list of) bands used in the US would make the phone prohibitively thick.
You mean the Symbian that isn't open source yet?
http://en.wikipedia.org/wiki/Symbian_OS#Open_source
Steps in the right direction, sure. However Google has definitively beaten them to the punch on the actual open sourcing.
Of course it doesn't particularly matter, since all phones are likely to be Tivoized for the foreseeable future.
The voltage drops off drastically at the end, sure. But for that very reason you'd have to be insane to make a battery monitor that didn't sense the current in use and integrate that over time for a very good estimate of the battery life you have remaining. The voltage curves give you additional information, but they're certainly not the only source.
You can see this if you look at your ACPI info for your battery in, say, Linux. It tells you the last full charge capacity, your current discharge rate, and how much time that is likely to buy you.
I second Microchip. Used in industry a lot, essentially impossible to fry with a mis-built circuit, easy to program, freely available student version C compiler along with 100% free assembler...
I agree. At U-M we pretty much autograde everything. As an added bonus, most classes require you to not only submit the source to your program that compiles and then passes the tests, but you're required to submit testcases that are then run against intentionally buggy programs written by the instructors.
This way you get a score not only based on how well you completed the task, but also your ability to write high-coverage test cases--and considering how many corner-cases get exploited these days, teaching kids to write their own test suites sounds like a great idea to me.
As for the malicious code factor, since all of the testing is done on a remote machine and you receive reports by e-mail, you'd have to either A) have inside knowledge of exploitable holes (in which case you're proabably a TA already) or B) write code that performs recon and reports back to you. Since I know our TA's at least scan through people source code submissions, writing recon code would probably get caught. Our school's Honor Code would not be very forgiving at that point etiher, you'd likely find yourself looking for another school to complete your degree at.
Bottom line: grading by hand is great until you've got 150 pipelined CPU simulators to go through by hand. Automated grading is an easy solution.
Don't worry, that's still the norm. I dunno what TF poster is talking about, I dug my laptop out of the tech graveyard. The keyboard flips out sometimes, but you can't beat free...
How it violates US monopoly laws to not provide you with support for a product you didn't buy?
Bugs aside, if the thing worked properly that's essentially what it would do. I have no qualms about Microsoft choosing not to provide support to people using pirated copies.
Your claims of it locking Office to the Windows platform are also unfounded, considering there's a Mac download site that doesn't require WGA...
I don't have a problem with a company making money off of a product. I have a problem with a company actively subverting other people's altruism in order to maintain a stranglehold on profit.
Don't confuse me with an open-source-only hippie, but at the same time the Eclipse people deserve better than Sun trying to flush them out just to keep Java on a tight leash.
...that everyone sees what I saw in the beginning.
Sun has no interest in Java for the technology, and this latest ploy isn't to help *Java* -- its to help Sun. It always has been. If you're looking for the most greedy company out there that has absolutely zero interest in its customers and every interest in profit, it isn't Microsoft--its Sun.
Then you might as well just go write your own patcher. Hell, he told you *exactly* what to do in the article.
More likely its in a server exterior to the US so some judge-with-a-god-complex can't just rip the server down at a request from the people who run Skype. Injunctions are like candy these days.
People need to understand the difference between memory and hard drive. My god. And good luck on this one, because I know some people who still get it wrong, 30,000 explainations later...
Canada? Into Detroit or New York I have never needed (though there are laws and motions in play to change this right now) needed a passport to re-enter the US. In fact, while birth certificates are technically required, I've only ever had *those* checked upon entry to Canada. Never on re-entry to the US.
Not even counting the fact that "good" viruses stand a pretty good chance of screwing something up for someone somewhere along the line, the primary thing that stops people from writing these "White Knight" viruses?
The Law.
You write a virus that compromises someone's system--even under the pretense of doing good--and you go to jail. Done.
Slashdot Mirror
The problem with supporting all frequency bands is not the availability of hardware to decode them, it's that consumers have gotten used to their nice thin devices.
Enough metal to wire up antennas even just for the (ridiculously long list of) bands used in the US would make the phone prohibitively thick.
You mean the Symbian that isn't open source yet? http://en.wikipedia.org/wiki/Symbian_OS#Open_source Steps in the right direction, sure. However Google has definitively beaten them to the punch on the actual open sourcing. Of course it doesn't particularly matter, since all phones are likely to be Tivoized for the foreseeable future.
The voltage drops off drastically at the end, sure. But for that very reason you'd have to be insane to make a battery monitor that didn't sense the current in use and integrate that over time for a very good estimate of the battery life you have remaining. The voltage curves give you additional information, but they're certainly not the only source. You can see this if you look at your ACPI info for your battery in, say, Linux. It tells you the last full charge capacity, your current discharge rate, and how much time that is likely to buy you.
I second Microchip. Used in industry a lot, essentially impossible to fry with a mis-built circuit, easy to program, freely available student version C compiler along with 100% free assembler...
I 3 Microchip.
I agree. At U-M we pretty much autograde everything. As an added bonus, most classes require you to not only submit the source to your program that compiles and then passes the tests, but you're required to submit testcases that are then run against intentionally buggy programs written by the instructors.
This way you get a score not only based on how well you completed the task, but also your ability to write high-coverage test cases--and considering how many corner-cases get exploited these days, teaching kids to write their own test suites sounds like a great idea to me.
As for the malicious code factor, since all of the testing is done on a remote machine and you receive reports by e-mail, you'd have to either A) have inside knowledge of exploitable holes (in which case you're proabably a TA already) or B) write code that performs recon and reports back to you. Since I know our TA's at least scan through people source code submissions, writing recon code would probably get caught. Our school's Honor Code would not be very forgiving at that point etiher, you'd likely find yourself looking for another school to complete your degree at.
Bottom line: grading by hand is great until you've got 150 pipelined CPU simulators to go through by hand. Automated grading is an easy solution.
Don't worry, that's still the norm. I dunno what TF poster is talking about, I dug my laptop out of the tech graveyard. The keyboard flips out sometimes, but you can't beat free...
How it violates US monopoly laws to not provide you with support for a product you didn't buy?
Bugs aside, if the thing worked properly that's essentially what it would do. I have no qualms about Microsoft choosing not to provide support to people using pirated copies.
Your claims of it locking Office to the Windows platform are also unfounded, considering there's a Mac download site that doesn't require WGA...
I don't have a problem with a company making money off of a product. I have a problem with a company actively subverting other people's altruism in order to maintain a stranglehold on profit. Don't confuse me with an open-source-only hippie, but at the same time the Eclipse people deserve better than Sun trying to flush them out just to keep Java on a tight leash.
...that everyone sees what I saw in the beginning. Sun has no interest in Java for the technology, and this latest ploy isn't to help *Java* -- its to help Sun. It always has been. If you're looking for the most greedy company out there that has absolutely zero interest in its customers and every interest in profit, it isn't Microsoft--its Sun.
Then you might as well just go write your own patcher. Hell, he told you *exactly* what to do in the article.
More likely its in a server exterior to the US so some judge-with-a-god-complex can't just rip the server down at a request from the people who run Skype. Injunctions are like candy these days.
People need to understand the difference between memory and hard drive. My god. And good luck on this one, because I know some people who still get it wrong, 30,000 explainations later...
What does your server closet look like, and what poor sod is in charge of wiring it *shudder*?
You can always use their flaws in the dual core caching to circumvent any DRM stuff in their chips!
Thanks Intel. The backdoor's really handy!
Canada? Into Detroit or New York I have never needed (though there are laws and motions in play to change this right now) needed a passport to re-enter the US. In fact, while birth certificates are technically required, I've only ever had *those* checked upon entry to Canada. Never on re-entry to the US.
Not even counting the fact that "good" viruses stand a pretty good chance of screwing something up for someone somewhere along the line, the primary thing that stops people from writing these "White Knight" viruses? The Law. You write a virus that compromises someone's system--even under the pretense of doing good--and you go to jail. Done.