Garmin devices are increasingly embedding Linux in their products, and we know TomTom is. There are several XML parsing libraries available to do the job that build on ARM, and it isn't impossible to port them to whatever crazy OS you have on hand.
On the other hand, I've seen biologist written perl code that terminated on div-by-zero, and closed, re-opened then seeked into the input file rather than implement a linear processing of data. I've also met plenty of biology grad students who basically said their technique for analysis was to invite a statistics co-author. If you're going to claim Mendel as a mathematical biologist, we might as well call Babbage a computer scientist, and he built the diffrence engine 30 years before Mendel's pea experiment.
I also know of computational biologists who debug laptop BIOSes, and have a firm grasp of math. I believe them to be a minority, but perhaps there's selection effects I'm unaware of. Anyways, at this point I have to believe that math and statistics is vital to understanding the wealth of genomic data we face, and I expect most successful researchers meet or exceed my own humble understanding of statistics.
This is why I generally conflate "cloud computing" with elastic computing ala Amazon EC2. It's different than distributed computing in that multiple people share a cluster, and which node runs what is potentially ephemeral, changing, like a cloud.
There's a diversity of equipment out there that owning a single laptop can't capture. Consumers generally can't accurately make a conclusion about the state of Linux power support; my laptop works equally well on Windows and Ubuntu yet I won't start declaring Ubuntu power management just as good as Windows.
But there's more to this story. Consumers also don't have equipment to measure power demand. Time remaining can be misreported, so at the very least use wall-clocks. It's much better to measure power draw, but your kill-a-watt won't cut it, since laptops generally alter their behavior on AC. What you want is to instrument the battery itself. Not easily done without risking a fire.
1) It's a luxury device that will be subsidized in the US. 2) It's a very small form factor, and could be handy in lots of non-traditional cellphone places. My Subaru Legacy has an optional (expensive) navigation unit; I was thinking about building a Carputer from ARM like stuff, and this looks to be about perfect, and probably cheaper. Added carphone tech is a bonus.
HAM is backwards. Did you know you can't use encrypted communications? And that your posts would likely be a violation of decency laws if communicated via HAM radio? Technologically speaking, ad-hoc WiFi is a stronger tool for natural disasters, it's just crippled by low power requirements.
But your point about powerline networks doesn't make much sense. If there's a natural disaster and power outage, why is a home power network still operating?
Personally, I think it's a bit creepy for Canonical to capture revenues from whatever is installed in Firefox. There's significant participation from outside Canonical -- what prevents an Ubuntu Developer not affiliated with Canonical from taking the relatively simple steps to sell other changes to the highest bidder? Imagine if a Liferea maintainer started accepting payments to include feeds by default. What stops another developer from removing them and placing their own paid feeds?
Its hard to come up with examples because very few open source programs are prepared for adware; it's mostly web related stuff.
** Micro Center's "Web Pricing, Get It Now!" program applies to all in-stock Intel® and AMD® processors. Twice per week, on Monday and Thursday evenings, we verify CPU pricing from newegg.com and tigerdirect.com, and verify our price is set to the lowest non-rebated price including shipping. This price is effective when the store opens the next day and remains firm until the next price change is effective on a Tuesday or Friday morning. Comparisons will be for like product only; boxed product to boxed product and OEM (also known as tray product) to OEM product. Limited time offer. Micro Center reserves the right to limit quantities. Matched prices are exclusive of sales tax. Prior sales excluded.
They seem to be making improvements on this front to me...
Many cheap thermometers use alcohol rather than mercury. I don't know about legality of mercury tilt switches, but depending on the size, a ball bearing may be used instead. But, you could have pointed to the CFL bulbs instead.
have littlesnitch on my Macs, so in the unlikely event my keyboard is compromised (God forbid), at least I'll have a clue it's trying to squawk out of turn.:)
I think you missed the slide where they discussed how to disable it via keyboard commands.
Charging for an iphone app is symptomatic not of you the developer or the GPL, but of the scarcity of software for the iPhone, and the scarcity of developers for it. Free software should not discriminate against any field of endeavor, including commercial. We both know that if the iPhone was an open platform the price of GPL'd games would tend towards 0. The GPL is not in conflict with charging for binaries, as long as you have published the exact source used to build the binaries.
If the an XPilot author feels a violation has been made, he should ask himself why he isn't using an open cellphone platform and encouraging others to do the same.
Firefox makes users jump through hoops for a reason. Once upon a time, webmasters were terrible at keeping websites up to date, and browsers didn't work very hard to make it apparent. If the website is built and operated correctly, users never see a damn thing.
The first hoop is the most important: the page looks like an error, because it is. The proper thing to do is contact the webmaster, or call your helpdesk, and get the cert fixed. Don't continue. The wrong thing to do here is all the rest of the crap where you "pay attention" but intentionally make a stupid decision and "continue anyway." That process does actually give much more information than previous incarnations. If it's self-signed, or expired, or invalid, it'll say so. Not that it matters, because you as a user have no control over whether the certificate is valid or not. These messages should be intended for power users and developers, since they're the only people who might be able to escalate or *fix it*.
The problem as I see it is that web people seem okay with the idea of allowing bad certs. Helpdesk might have previously told users "just click continue anyways, and go on your way." So yea, error dialogs were much easier for users when they could click once and permanently ignore security warnings caused by incompetent IT.
I heard a piece on NPR about Chinese firms hiring Americans to present a "foreign firm" look to what is truthfully a local company. For whatever reasons, Chinese firms feel discriminated against for being Chinese by both foreign companies and other Chinese firms.
I'm not sure that hiring actors as negotiators for an hour is helping the whole trustworthy stereotype...
Guess what: the largest users of electricity are industrial. For example, aluminum is basically refined with electricity. Lots of it. Given a laborforce mostly working 9-5 to apply that electricty, there's still a peak use time.
I've been reviewing various proposals like this, and basically, it's a tradeoff mirrors don't want. This sorta stuff has been proposed for ages. I listened to a recording of the author of rsync give an introduction to the algorithm and program, and among the questions was "is this suitable for.deb?". The answer was "Not unless the archive is completely recompressed with gzip patched to be rsync compatible".
Eventually that patch landed, and you could conceivably do this. Except it expands the entire archive by 1-2 percent. And there's a lot of CPU overhead where there was none before.
Then someone cooked up zsync. It's the same thing as rsync except with a precalculated set of results for the server side. This looked like a winner. But someone else really wants LZMA compressed packages to fit more onto pressed CDs. So now we're at a fundamental impass: optimize for the distribution of install media to new users, or optimize for the distribution of updates to existing users.
The best resolution I've seen is to use LZMA compression on the entire CD volume, but that requires the kernel to get their ass in gear and allow yet another compression in the kernel. That may have finally happened, I haven't checked recently. But generally LZMA requires more RAM to operate, so that could raise the minimum requirements on installs.
In short, it's a balancing act of effort, bandwidth, CPU and RAM. What works for some may not work for all.
I also find it somewhat ironic that, in a discussion where I'm arguing in favour of an equivalency between computer science and mathematics, you use a mathematical theorem to find fault with my argument.
It's just that there are limits to what you can prove with formal logic techniques. For example, you can't prove that every computer routine terminates for every input. For example is newton's method is an algorithm that may or may not terminate depending on the inputs. If you want a contrived example, imagine using newton's method to calculate rocket trajectory and implement guidance routines. You might consider simulated annealing unprovable to terminate.
Finally, here's a concrete example of how software's relation to math confounds formal methods: Switch Stability is Undecidable.
I'm afraid you are displaying ignorance of the subject. Every algorithm and piece of software can be proven
Who exactly is ignorant here? I vote for the person who ignores the incompleteness theorem. Of course, you didn't exactly define what it means for an algorithm to be proven, or the scope of "every."
If that's their concern, it should have been mentioned at the working group. Their paper never mentions the subject. Nokia, on the other hand, does mention the need for hardware decoding, and insinuates that Ogg is proprietary.
Renting power tools isn't unusual. There's a place we have in town that rents out lots of stuff; we mostly go for the chainsaw and chipper, but they carry stuff big and small.
These aren't loops. You might make an argument that they're like loop unrolling, except there's no loops. It's entirely possible to have a smaller protein with an entirely different structure, composition and function encoded in the same region as a larger protein. Plus, there's a complementary DNA strand; you can have DNA that encodes something in one direction and something different in the other!
Slashdot Mirror
Garmin devices are increasingly embedding Linux in their products, and we know TomTom is. There are several XML parsing libraries available to do the job that build on ARM, and it isn't impossible to port them to whatever crazy OS you have on hand.
On the other hand, I've seen biologist written perl code that terminated on div-by-zero, and closed, re-opened then seeked into the input file rather than implement a linear processing of data. I've also met plenty of biology grad students who basically said their technique for analysis was to invite a statistics co-author. If you're going to claim Mendel as a mathematical biologist, we might as well call Babbage a computer scientist, and he built the diffrence engine 30 years before Mendel's pea experiment.
I also know of computational biologists who debug laptop BIOSes, and have a firm grasp of math. I believe them to be a minority, but perhaps there's selection effects I'm unaware of. Anyways, at this point I have to believe that math and statistics is vital to understanding the wealth of genomic data we face, and I expect most successful researchers meet or exceed my own humble understanding of statistics.
It's remarkable because a biologist discovered math and possibly statistics.
Until someone cuts power to the corporate datacenter, and it takes longer to restore than you have batteries.
This is why I generally conflate "cloud computing" with elastic computing ala Amazon EC2. It's different than distributed computing in that multiple people share a cluster, and which node runs what is potentially ephemeral, changing, like a cloud.
There's a diversity of equipment out there that owning a single laptop can't capture. Consumers generally can't accurately make a conclusion about the state of Linux power support; my laptop works equally well on Windows and Ubuntu yet I won't start declaring Ubuntu power management just as good as Windows.
But there's more to this story. Consumers also don't have equipment to measure power demand. Time remaining can be misreported, so at the very least use wall-clocks. It's much better to measure power draw, but your kill-a-watt won't cut it, since laptops generally alter their behavior on AC. What you want is to instrument the battery itself. Not easily done without risking a fire.
1) It's a luxury device that will be subsidized in the US.
2) It's a very small form factor, and could be handy in lots of non-traditional cellphone places. My Subaru Legacy has an optional (expensive) navigation unit; I was thinking about building a Carputer from ARM like stuff, and this looks to be about perfect, and probably cheaper. Added carphone tech is a bonus.
HAM is backwards. Did you know you can't use encrypted communications? And that your posts would likely be a violation of decency laws if communicated via HAM radio? Technologically speaking, ad-hoc WiFi is a stronger tool for natural disasters, it's just crippled by low power requirements.
But your point about powerline networks doesn't make much sense. If there's a natural disaster and power outage, why is a home power network still operating?
Personally, I think it's a bit creepy for Canonical to capture revenues from whatever is installed in Firefox. There's significant participation from outside Canonical -- what prevents an Ubuntu Developer not affiliated with Canonical from taking the relatively simple steps to sell other changes to the highest bidder? Imagine if a Liferea maintainer started accepting payments to include feeds by default. What stops another developer from removing them and placing their own paid feeds?
Its hard to come up with examples because very few open source programs are prepared for adware; it's mostly web related stuff.
From their front page:
They seem to be making improvements on this front to me...
Many cheap thermometers use alcohol rather than mercury. I don't know about legality of mercury tilt switches, but depending on the size, a ball bearing may be used instead. But, you could have pointed to the CFL bulbs instead.
I think you missed the slide where they discussed how to disable it via keyboard commands.
Charging for an iphone app is symptomatic not of you the developer or the GPL, but of the scarcity of software for the iPhone, and the scarcity of developers for it. Free software should not discriminate against any field of endeavor, including commercial. We both know that if the iPhone was an open platform the price of GPL'd games would tend towards 0. The GPL is not in conflict with charging for binaries, as long as you have published the exact source used to build the binaries.
If the an XPilot author feels a violation has been made, he should ask himself why he isn't using an open cellphone platform and encouraging others to do the same.
Yea, what a bunch of phonies.
Firefox makes users jump through hoops for a reason. Once upon a time, webmasters were terrible at keeping websites up to date, and browsers didn't work very hard to make it apparent. If the website is built and operated correctly, users never see a damn thing.
The first hoop is the most important: the page looks like an error, because it is. The proper thing to do is contact the webmaster, or call your helpdesk, and get the cert fixed. Don't continue. The wrong thing to do here is all the rest of the crap where you "pay attention" but intentionally make a stupid decision and "continue anyway." That process does actually give much more information than previous incarnations. If it's self-signed, or expired, or invalid, it'll say so. Not that it matters, because you as a user have no control over whether the certificate is valid or not. These messages should be intended for power users and developers, since they're the only people who might be able to escalate or *fix it*.
The problem as I see it is that web people seem okay with the idea of allowing bad certs. Helpdesk might have previously told users "just click continue anyways, and go on your way." So yea, error dialogs were much easier for users when they could click once and permanently ignore security warnings caused by incompetent IT.
So really, Microsoft and Apple made it big because Xerox PARC wasn't secretive enough?
I heard a piece on NPR about Chinese firms hiring Americans to present a "foreign firm" look to what is truthfully a local company. For whatever reasons, Chinese firms feel discriminated against for being Chinese by both foreign companies and other Chinese firms.
I'm not sure that hiring actors as negotiators for an hour is helping the whole trustworthy stereotype...
Guess what: the largest users of electricity are industrial. For example, aluminum is basically refined with electricity. Lots of it. Given a laborforce mostly working 9-5 to apply that electricty, there's still a peak use time.
I've been reviewing various proposals like this, and basically, it's a tradeoff mirrors don't want. This sorta stuff has been proposed for ages. I listened to a recording of the author of rsync give an introduction to the algorithm and program, and among the questions was "is this suitable for .deb?". The answer was "Not unless the archive is completely recompressed with gzip patched to be rsync compatible".
Eventually that patch landed, and you could conceivably do this. Except it expands the entire archive by 1-2 percent. And there's a lot of CPU overhead where there was none before.
Then someone cooked up zsync. It's the same thing as rsync except with a precalculated set of results for the server side. This looked like a winner. But someone else really wants LZMA compressed packages to fit more onto pressed CDs. So now we're at a fundamental impass: optimize for the distribution of install media to new users, or optimize for the distribution of updates to existing users.
The best resolution I've seen is to use LZMA compression on the entire CD volume, but that requires the kernel to get their ass in gear and allow yet another compression in the kernel. That may have finally happened, I haven't checked recently. But generally LZMA requires more RAM to operate, so that could raise the minimum requirements on installs.
In short, it's a balancing act of effort, bandwidth, CPU and RAM. What works for some may not work for all.
It's just that there are limits to what you can prove with formal logic techniques. For example, you can't prove that every computer routine terminates for every input. For example is newton's method is an algorithm that may or may not terminate depending on the inputs. If you want a contrived example, imagine using newton's method to calculate rocket trajectory and implement guidance routines. You might consider simulated annealing unprovable to terminate.
Finally, here's a concrete example of how software's relation to math confounds formal methods: Switch Stability is Undecidable.
No, they aren't. My question to you is: why not? The HTML5 working group is the place to mention things like that.
Who exactly is ignorant here? I vote for the person who ignores the incompleteness theorem. Of course, you didn't exactly define what it means for an algorithm to be proven, or the scope of "every."
If that's their concern, it should have been mentioned at the working group. Their paper never mentions the subject. Nokia, on the other hand, does mention the need for hardware decoding, and insinuates that Ogg is proprietary.
Renting power tools isn't unusual. There's a place we have in town that rents out lots of stuff; we mostly go for the chainsaw and chipper, but they carry stuff big and small.
These aren't loops. You might make an argument that they're like loop unrolling, except there's no loops. It's entirely possible to have a smaller protein with an entirely different structure, composition and function encoded in the same region as a larger protein. Plus, there's a complementary DNA strand; you can have DNA that encodes something in one direction and something different in the other!