The coefficient of friction is dimensionless; it's the ratio of the maximum frictional force (opposing motion) to the force pressing the two objects together (such as the upper object's weight).
WebOS is quite happy to run C apps; it's just that the graphical toolkit is different from the one on the iPhone. There's not a whit of difference between this distinction and writing for MVC versus, say, Motif.
You can't port graphical Windows apps, Mac apps, or the like to the iPhone or WebOS--but non-graphical programs (even including a full Apache install) run quite happily on the latter.
The ability to run HTML5 apps on WebOS, the iPhone, and Android is exactly what I'm saying is a feature--you get cross-platform compatibility and a standards-based development target. I haven't run benchmarks, either, but very heavyweight Javascript apps (including, for example, full Facebook and many desktop-target GWT apps) run just fine on the Pre's OMAP.
Finally, of course, you can write WebOS apps in straight SDL. Quake's been playable on it for quite some time.
The full Optware distribution, native SDL apps, and a click-the-launcher Terminal application, all looked on with favor by Palm tend to disagree with your claims, and that's not even mentioning that you can run custom kernels under WebOS if you like.
It's also funny you should mention writing apps in HTML+JS; I'm using GWT to do that right now for a desktop application exactly because it's an easy way to write multi-platform apps, including mobile versions.
I'm not currently a research physicist, but I'm a (prior) collaborator on the experiment in question.
No "strangelet" has ever been observed, and their behavior depends on certain parameters that are unknown... because they've never been observed. It's reasonable to guess at this point that the strangelet-eats-the-world scenario is probably bogus just due to the anthropic principle.
The concern over the eating-the-world scenario was allayed to physicists' satisfaction based on calculations about cosmic rays. The kinds of collisions that would produce strangelets happen constantly to the moon because of the lack of an atmosphere or magnetic field to shield it, and the moon's still there. Statistics suggest, therefore, that these particular concerns are unlikely to be realized.
And this is why "direct benefit" is a completely useless metric, and in fact isn't applied to most of the rest of a business's operations. A/C and heating, for example, don't provide a direct benefit except for industrial controls, yet most businesses see the value in providing a comfortable work environment to employees.
It's the same old story: Centralized policymaking suffers from a chronic lack of both information and imagination, and policies like global whitelists essentially kill off many useful innovations.
The claims look quite similar to compressed RTP, which is used to shorten IP/UDP/RTP headers for VoIP calls from 40 bytes to 2 and has been an RFC since 1999. For that matter, this patent could describe MPLS as well.
I bought my first home about a year ago, and even before I moved in I installed a whole-house audio system. I didn't put in the expensive source-selection room controls, but I did install per-room volume controls and in-ceiling speakers in each main room. I have home-run speaker cables to the same spot where my network cables go and an input cable that runs to where I have my receiver in the living room. The speaker distribution panel I have actually has two inputs and per-output switching, so I could send an alternate audio source to some of the rooms.
My receiver has dual outputs (5.1 plus a separate stereo output), which is important since it can be easy to run at too low an impedance if you have multiple pairs of speakers. This arrangement allows me to send the main channels of a movie or the like everywhere in the house, in case somebody goes to the bathroom or to get popcorn.
I purchased my cable and wall plates from Monoprice, and my speakers, volume controls, and the distribution unit were from Outdoor Speaker Depot. I was able to do stereo audio to four rooms, with volume in each room, for a little under $500 in materials.
Sounds like you "installed an unauthorized program" when you loaded Slashdot from a public computer. After all, you were downloading and running all sorts of programs in a scary language called ECMAScript...
IPv6 has a number of sane ways to multihome. The problem is that network implementers (at whatever level these decisions are made) just don't want to bother.
Additionally, TCP is the only protocol that has serious issues with this. Yes, we can't handwave it, but for new protocols, why isn't SCTP usually a better choice?
It should have been set up as a transparent change, where every person who had an IPv4 address magically had an IPv6 address that worked, and whenever an IPv6 stack, be it either your computer or some router halfway down the road, determined it was talking to IPv4, converted it into IPv4.
This is actually the way that IPv4-mapped addresses (::ffff:0:0/96) were originally envisioned, and it's the way that Linux and [^Open]BSD handle it internally. You'll notice a conspicuous absence in that list of OSs, though.
Minor clarification: The difficulty isn't so much IPv6 clients talking to IPv4 hosts as it is the other way around. Mapping IPv4 addresses into IPv6 addresses is trivial (take a look at totd/ptrtd for an example), but IPv4 addresses don't map onto IPv6: Legacy hosts can't initiate connections to every address in the IPv6 space.
I know I'm only seeing a small piece of the diagnostics here, but it's my understanding that they are correct that Verizon's end-user network should act as a stub as far as end-user traffic is concerned. If the problem is that they won't route traffic from your address (inside Verizon's/32) to another direct-allocation network that is in fact a legitimate BGP peer for IPv6 services, I'd complain to ARIN directly that their traffic is being dropped.
The answer to "what should we do about it" is that we should require the bank, at its own expense, to fix the problem it created, by changing account numbers or doing whatever else would be done in the event this information were compromised some other way.
The First Amendment protection is a bit wider than some other commenters expect, but probably the Fifth Amendment (can't take property, which would include an e-mail account) would be even higher than the Fourth. All that said, I think there's likely a case for interference with a business relationship (between Google and the customer) and maybe even something under the federal Computer Fraud and Abuse Act.
Getting Akamai on board would solve a huge chunk of that inaccessible-Web problem. Seems like it'd even be easier to handle content distribution for IPv6 than for IPv4.
Every home router I've seen does IP in software, so they ought to be updatable with a firmware upgrade. All it will take is for one major ISP to roll out IPv6 to customers and start advertising "next generation Internet" support for the others to put it on their while-we're-replacing-old-equipment list. Sure, it'll take a while, but it'll happen sometime.
Depends entirely on the make of the car. My VW's outlet is on all the time, and my previous vehicle, a GM, had it on all the time too (though I think the behavior might have been selectable).
Radar detectors aren't illegal except in Virginia, and even there, there's a case waiting to be made that federal law governing radio signals preempts the state restriction.
I've never said you shouldn't still use a firewall. Defense in depth is still the best policy.
Additionally, those machines were compromised only because the IPv4 address space is small enough to scan. If you're not assigning addresses like:1 to machines, scanning even a/64 is infeasible.
Because you are still running an IPv4 stack. IPv6 autoconfig will give you a prefix and a router(s). That's it.
Plus an RDNSS (recursive DNS server) entry. That gives you an IP address, a default gateway, and DNS servers. That's all of the information that most IPv4 DHCP replies contain.
Slashdot Mirror
"Jesus said to them, 'But now if you have a purse, take it, and also a bag; and if you don't have a sword, sell your cloak and buy one.'" (Luke 22:36)
The coefficient of friction is dimensionless; it's the ratio of the maximum frictional force (opposing motion) to the force pressing the two objects together (such as the upper object's weight).
Especially since CHAdeMO chargers can provide up to 62.5kW...
WebOS is quite happy to run C apps; it's just that the graphical toolkit is different from the one on the iPhone. There's not a whit of difference between this distinction and writing for MVC versus, say, Motif.
You can't port graphical Windows apps, Mac apps, or the like to the iPhone or WebOS--but non-graphical programs (even including a full Apache install) run quite happily on the latter.
The ability to run HTML5 apps on WebOS, the iPhone, and Android is exactly what I'm saying is a feature--you get cross-platform compatibility and a standards-based development target. I haven't run benchmarks, either, but very heavyweight Javascript apps (including, for example, full Facebook and many desktop-target GWT apps) run just fine on the Pre's OMAP.
Finally, of course, you can write WebOS apps in straight SDL. Quake's been playable on it for quite some time.
The full Optware distribution, native SDL apps, and a click-the-launcher Terminal application, all looked on with favor by Palm tend to disagree with your claims, and that's not even mentioning that you can run custom kernels under WebOS if you like.
It's also funny you should mention writing apps in HTML+JS; I'm using GWT to do that right now for a desktop application exactly because it's an easy way to write multi-platform apps, including mobile versions.
I'm not currently a research physicist, but I'm a (prior) collaborator on the experiment in question.
No "strangelet" has ever been observed, and their behavior depends on certain parameters that are unknown... because they've never been observed. It's reasonable to guess at this point that the strangelet-eats-the-world scenario is probably bogus just due to the anthropic principle.
The concern over the eating-the-world scenario was allayed to physicists' satisfaction based on calculations about cosmic rays. The kinds of collisions that would produce strangelets happen constantly to the moon because of the lack of an atmosphere or magnetic field to shield it, and the moon's still there. Statistics suggest, therefore, that these particular concerns are unlikely to be realized.
It seems to me that Ms. LeGuin is engaging in a bit of doublethink: How exactly is anything "free" while it's simultaneously "controlled"?
(Not to mention, of course, that claiming "legitimate right" is begging the question...)
And this is why "direct benefit" is a completely useless metric, and in fact isn't applied to most of the rest of a business's operations. A/C and heating, for example, don't provide a direct benefit except for industrial controls, yet most businesses see the value in providing a comfortable work environment to employees.
By the same token, the studies are now old news that have shown that employees who take "mental breaks" with Facebook and friends are more productive and that external communications channels are becoming increasingly valuable to businesses.
It's the same old story: Centralized policymaking suffers from a chronic lack of both information and imagination, and policies like global whitelists essentially kill off many useful innovations.
The claims look quite similar to compressed RTP, which is used to shorten IP/UDP/RTP headers for VoIP calls from 40 bytes to 2 and has been an RFC since 1999. For that matter, this patent could describe MPLS as well.
I bought my first home about a year ago, and even before I moved in I installed a whole-house audio system. I didn't put in the expensive source-selection room controls, but I did install per-room volume controls and in-ceiling speakers in each main room. I have home-run speaker cables to the same spot where my network cables go and an input cable that runs to where I have my receiver in the living room. The speaker distribution panel I have actually has two inputs and per-output switching, so I could send an alternate audio source to some of the rooms.
My receiver has dual outputs (5.1 plus a separate stereo output), which is important since it can be easy to run at too low an impedance if you have multiple pairs of speakers. This arrangement allows me to send the main channels of a movie or the like everywhere in the house, in case somebody goes to the bathroom or to get popcorn.
I purchased my cable and wall plates from Monoprice, and my speakers, volume controls, and the distribution unit were from Outdoor Speaker Depot. I was able to do stereo audio to four rooms, with volume in each room, for a little under $500 in materials.
Sounds like you "installed an unauthorized program" when you loaded Slashdot from a public computer. After all, you were downloading and running all sorts of programs in a scary language called ECMAScript...
IPv6 has a number of sane ways to multihome. The problem is that network implementers (at whatever level these decisions are made) just don't want to bother.
Additionally, TCP is the only protocol that has serious issues with this. Yes, we can't handwave it, but for new protocols, why isn't SCTP usually a better choice?
It should have been set up as a transparent change, where every person who had an IPv4 address magically had an IPv6 address that worked, and whenever an IPv6 stack, be it either your computer or some router halfway down the road, determined it was talking to IPv4, converted it into IPv4.
This is actually the way that IPv4-mapped addresses (::ffff:0:0/96) were originally envisioned, and it's the way that Linux and [^Open]BSD handle it internally. You'll notice a conspicuous absence in that list of OSs, though.
Minor clarification: The difficulty isn't so much IPv6 clients talking to IPv4 hosts as it is the other way around. Mapping IPv4 addresses into IPv6 addresses is trivial (take a look at totd/ptrtd for an example), but IPv4 addresses don't map onto IPv6: Legacy hosts can't initiate connections to every address in the IPv6 space.
I know I'm only seeing a small piece of the diagnostics here, but it's my understanding that they are correct that Verizon's end-user network should act as a stub as far as end-user traffic is concerned. If the problem is that they won't route traffic from your address (inside Verizon's /32) to another direct-allocation network that is in fact a legitimate BGP peer for IPv6 services, I'd complain to ARIN directly that their traffic is being dropped.
The answer to "what should we do about it" is that we should require the bank, at its own expense, to fix the problem it created, by changing account numbers or doing whatever else would be done in the event this information were compromised some other way.
The First Amendment protection is a bit wider than some other commenters expect, but probably the Fifth Amendment (can't take property, which would include an e-mail account) would be even higher than the Fourth. All that said, I think there's likely a case for interference with a business relationship (between Google and the customer) and maybe even something under the federal Computer Fraud and Abuse Act.
Getting Akamai on board would solve a huge chunk of that inaccessible-Web problem. Seems like it'd even be easier to handle content distribution for IPv6 than for IPv4.
Especially ironic since just this afternoon I was looking at a Cisco Press book that gave a lookup for www.cisco.com as an example of IPv6 DNS.
Every home router I've seen does IP in software, so they ought to be updatable with a firmware upgrade. All it will take is for one major ISP to roll out IPv6 to customers and start advertising "next generation Internet" support for the others to put it on their while-we're-replacing-old-equipment list. Sure, it'll take a while, but it'll happen sometime.
The routers are fine, it's only layer-3 switches that have to be replaced.
Although on that count, could Vyatta and friends *please* get up to speed with IPv6 support? The underlying engine's supported it for years...
Depends entirely on the make of the car. My VW's outlet is on all the time, and my previous vehicle, a GM, had it on all the time too (though I think the behavior might have been selectable).
Radar detectors aren't illegal except in Virginia, and even there, there's a case waiting to be made that federal law governing radio signals preempts the state restriction.
I've never said you shouldn't still use a firewall. Defense in depth is still the best policy.
Additionally, those machines were compromised only because the IPv4 address space is small enough to scan. If you're not assigning addresses like :1 to machines, scanning even a /64 is infeasible.
Because you are still running an IPv4 stack. IPv6 autoconfig will give you a prefix and a router(s). That's it.
Plus an RDNSS (recursive DNS server) entry. That gives you an IP address, a default gateway, and DNS servers. That's all of the information that most IPv4 DHCP replies contain.