The distinction is between non-free firmware, which runs entirely on the hardware peripheral (most wireless controllers), and non-free drivers, which run on the main CPU (NVidia).
The UK isn't getting mobile TV until 2012, when the bandwidth currently used for analogue TV becomes available nationwide. The networks have various video on demand services, but that isn't the same as broadcast mobile TV.
Since the US is not leading the field, like Japan and Korea, I'd expect them to leverage the work done by the DVB consortium to develop a global handheld digital TV standard. At the very least as market followers, they could have gone with the existing Korean system (which has support from China) or maybe the Japanese system (the Japanese similarly take the "do own own thing" approach, but at least they have the excuse that they're deploying before the standards are ready). Going with a single vendor proprietary solution is shortsighted, which is exactly what I'd expect of the US mobile industry.
Especially with the validator's stupidity in treating & signs in the href attribute of my a elements as the beginning of an entity which it's not!/rant >.>
According to every HTML spec ever produced, it is. The fact that browsers handle unknown entities by printing verbatim to the output saves your ass, but it is incorrect to use an ampersand without escaping it as &
I meant DVB-H (H for handheld, T for terrestrial), but I see TFA mentions MediaFLO, which it turns out is a proprietary Qualcomm broadcast technology not just the name of the front end software as I'd assumed.
TFA is a bit light on details. Is this a true broadcast system, or 3G bandwidth sucking streaming out to individual handsets like the UK networks have rolled out? If it's true broadcast, have they adopted DVB-T, Korea's T-DMB, Japan's 1-seg, or done the American thing and gone their own incompatible way?
That assumes that you only trust PGP keys that you yourself have verified. In that case you can achieve the same level of trust by running your own CA. The difference comes when you need to trust a wider range of keys. In the PGP model, you have to trust your contacts to be as vigilant about checking the identities of others as you yourself are. In the S/MIME model, you trust one third party to have consistent checking policies, and generally the more you pay the more thoroughly they will check.
Which model you prefer generally comes down to how paranoid you are about government spying and other issues arising out of centralised control. For terrorists and those that communicate with them, there is probably good grounds for preferring PGP, out of fear that a CA might issue fake keys to government agencies to allow them to trick you into sending them info. For others, the scenario of fake keys is far more likely to be a problem with PGP where you are trusting random people to verify others' identities. There was a case some years ago where Mickey Mouse was found to be only two or three degrees of separation away from Linus Torvolds in the PGP web of trust, demonstrating the flaws that appear when you try to scale PGP beyond those you immediately trust.
Nope. The way it works is that you generate a private/public keypair, then you send the public key to the CA as a CSR (certificate signing request). The CA never needs to see your private key, and signing it would be pointless, as noone other than yourself needs to be convinced of its authenticity.
It's a pretty serious problem for this notion, that none of the people Sturgeon claimed to have killed, are dead.
It does establish that he is mentally disturbed and has murderous fantasies. If Sturgeon was the one on trial, it would count against him about as much as some of Reiser's behavior. But Sturgeon isn't the one on trial, and the US has an adversarial system where the accused is put on trial to see if the prosecutions case against them stacks up, not an inquisitorial system where other possibilities can be considered.
Yes, in the early days, the byte code interpreter was just that - an interpreter, and the garbage collection was naive and blocked all threads when it kicked in, leading to the notorious GC pauses at random times (great for all those Java games that sprung up in the early days).
After Java 1.2 was released, Sun released a drop in replacement "Server VM" which had "hotspot" compilation, where programs were profiled at runtime and parts of the code that were frequently called were compiled to native code. In Java 1.3, this became the default VM on Unix platforms, and incremental garbage collection was introduced as an option. Both the hotspot compiler and the garbage collector have continued to be improved, to the point where there is no longer a distinction between server and client VMs and at some point generational garbage collection was introduced to speed up collection of short-lived objects. The focus now in 1.6 seems to be on improving startup time by loading only parts of the standard class library that are needed, instead of loading the whole lot at startup, and improving download time by downloading parts of the JVM on demand (the latter feature is currently in beta).
GWT is an API. You write your server side java code to use the GWT library to do its display instead of one of the alternatives like AWT, SWT or Swing. GWT then takes care of sending the right Javascript to the client to do the display. The client never gets sent any Java.
This is a byte code interpreter written in Javascript. You send it compiled Java, and it interprets it using Javascript. Presumably it has limited support for one of the aforementioned graphics APIs, probably AWT, and probably only enough of it to get their demos running.
Getting Java or Ruby code to interact with the DOM seems like it would be a huge pain compared with JQuery.
Not really, the netscape.javascript.* package for interacting with Javascript and the DOM has been a standard part of Java (even the notoriously incompatible MS JVM) since the early days. Perhaps it isn't as well known as it could be due to being outside the java.* namespace.
Java developers can already develop so called RIA applications using an old technology called applets. Some of the first RIA applications used it, because ten years ago there was no such thing as cross browser Javascript and Flash was only useful for making vector animation cartoons.
(In fact, IBM's commitment to Eclipse is so strong of late that some people feel they've become dominant in the project, which is a bit of a sticky political situation for them.)
<kneejerk>You mean they've wrenched control of the platform from the original developers?!!!</kneejerk>
In a large business, you will be limiting your users and doing a lot of management no matter what software you choose to run your mail servers. Your competitors will too.
Was it they didn't want to deliver 3G? I doubt it.
I think it was time and moeny for development + possible licensing costs from AT&T and other carriers for the tech to use the network.
I'd be prepared to put money on the licensing issues being the major reason for Apple avoiding 3G in their first generation product. Not just the cost (which comes from the chip manufacturers who hold patents over the various technologies used, not the carriers), but the uncertainty of it all with lawsuits going on all over the place and Qualcomm banned from importing their chips around the time the iPhone was launched.
The official story of battery drain is not borne out by other manufacturers' figures - which actually show less drain for data use due to the radio transmitting and receiving for shorter periods. If the iPhone is not a data centric device, then what is?
What sort of support are you expecting for a certificate? Installation support should be available from the vendor of your servers. Was it renewal or revocation you had problems with? Renewal means more money for the CA, so it should just be a matter of phoning their sales team, they'll fall over themselves to provide you with service if you have a large number of certificates to renew. Revocation - I'm not sure enough customers will have had to deal with that to get enough feedback to make a judgement.
In java I can create two objects which point to each other, but with nothing else pointing to each object, and that memory will be lost for ever, but the garbage collector won't free them because it works by counting references.
Nonsense. GC in Java has never worked by counting references, and bugs due to circular references have been a thing of the past since Java 1.3 or so. Perhaps you're thinking of some of the psuedo garbage collection libraries available for C++.
Paypal Europe operates under Luxembourg law now, and they are a bank, so subject to whatever requirements Luxembourg puts on banks for handling disputes and account closures. Fire your lawyer and get a new one, as they are clearly incompetent if they have not figured this much out yet.
You mean like the racist western conspiracy that instigated a war with a formerly allied country mainly because of that countries despicable actions in China?
If the US and other Western countries gave a shit about what was happening in China, they would have jumped in 10 or 15 years earlier when things kicked off. What they were really worried about was Japan's expansion of its empire building into territories that they themselves had taken control of in the preceding decades. With everyone else busy in Europe, it was only the US that Japan had to worry about, and while they did not have colonies per se, they did have sufficient financial interest in South East Asia to get involved.
If Paypal is really concerned about phishing, why do they still send out emails saying their Terms and Conditions have changed please log in to your paypal account (link helpfully provided) to view the changes? Why do I need to log in to see the Terms and Conditions anyway? What if I want to see them before creating an account?
Thought Quebec was ignored but on closer inspection there's just nothing there.
The same goes for Libya if you look closer.
Both Koreas are empty, not surprising in the case of the North, maybe the South is worried about North Korea using Google Maps to plan an invasion? Also Guyana, Suriname and French Guiana in addition to a handful of islands in the Caribbean, some of which you named.
Slashdot Mirror
The distinction is between non-free firmware, which runs entirely on the hardware peripheral (most wireless controllers), and non-free drivers, which run on the main CPU (NVidia).
The UK isn't getting mobile TV until 2012, when the bandwidth currently used for analogue TV becomes available nationwide. The networks have various video on demand services, but that isn't the same as broadcast mobile TV.
Since the US is not leading the field, like Japan and Korea, I'd expect them to leverage the work done by the DVB consortium to develop a global handheld digital TV standard. At the very least as market followers, they could have gone with the existing Korean system (which has support from China) or maybe the Japanese system (the Japanese similarly take the "do own own thing" approach, but at least they have the excuse that they're deploying before the standards are ready). Going with a single vendor proprietary solution is shortsighted, which is exactly what I'd expect of the US mobile industry.
According to every HTML spec ever produced, it is. The fact that browsers handle unknown entities by printing verbatim to the output saves your ass, but it is incorrect to use an ampersand without escaping it as &
Huh? The Windows port of GTK/GLib is a bunch of DLLs, as is libpurple and all the IM provider plugins that it uses. So what are you waiting for?
I meant DVB-H (H for handheld, T for terrestrial), but I see TFA mentions MediaFLO, which it turns out is a proprietary Qualcomm broadcast technology not just the name of the front end software as I'd assumed.
TFA is a bit light on details. Is this a true broadcast system, or 3G bandwidth sucking streaming out to individual handsets like the UK networks have rolled out? If it's true broadcast, have they adopted DVB-T, Korea's T-DMB, Japan's 1-seg, or done the American thing and gone their own incompatible way?
That assumes that you only trust PGP keys that you yourself have verified. In that case you can achieve the same level of trust by running your own CA. The difference comes when you need to trust a wider range of keys. In the PGP model, you have to trust your contacts to be as vigilant about checking the identities of others as you yourself are. In the S/MIME model, you trust one third party to have consistent checking policies, and generally the more you pay the more thoroughly they will check.
Which model you prefer generally comes down to how paranoid you are about government spying and other issues arising out of centralised control. For terrorists and those that communicate with them, there is probably good grounds for preferring PGP, out of fear that a CA might issue fake keys to government agencies to allow them to trick you into sending them info. For others, the scenario of fake keys is far more likely to be a problem with PGP where you are trusting random people to verify others' identities. There was a case some years ago where Mickey Mouse was found to be only two or three degrees of separation away from Linus Torvolds in the PGP web of trust, demonstrating the flaws that appear when you try to scale PGP beyond those you immediately trust.
Nope. The way it works is that you generate a private/public keypair, then you send the public key to the CA as a CSR (certificate signing request). The CA never needs to see your private key, and signing it would be pointless, as noone other than yourself needs to be convinced of its authenticity.
It does establish that he is mentally disturbed and has murderous fantasies. If Sturgeon was the one on trial, it would count against him about as much as some of Reiser's behavior. But Sturgeon isn't the one on trial, and the US has an adversarial system where the accused is put on trial to see if the prosecutions case against them stacks up, not an inquisitorial system where other possibilities can be considered.
Yes, in the early days, the byte code interpreter was just that - an interpreter, and the garbage collection was naive and blocked all threads when it kicked in, leading to the notorious GC pauses at random times (great for all those Java games that sprung up in the early days).
After Java 1.2 was released, Sun released a drop in replacement "Server VM" which had "hotspot" compilation, where programs were profiled at runtime and parts of the code that were frequently called were compiled to native code. In Java 1.3, this became the default VM on Unix platforms, and incremental garbage collection was introduced as an option. Both the hotspot compiler and the garbage collector have continued to be improved, to the point where there is no longer a distinction between server and client VMs and at some point generational garbage collection was introduced to speed up collection of short-lived objects. The focus now in 1.6 seems to be on improving startup time by loading only parts of the standard class library that are needed, instead of loading the whole lot at startup, and improving download time by downloading parts of the JVM on demand (the latter feature is currently in beta).
GWT is an API. You write your server side java code to use the GWT library to do its display instead of one of the alternatives like AWT, SWT or Swing. GWT then takes care of sending the right Javascript to the client to do the display. The client never gets sent any Java.
This is a byte code interpreter written in Javascript. You send it compiled Java, and it interprets it using Javascript. Presumably it has limited support for one of the aforementioned graphics APIs, probably AWT, and probably only enough of it to get their demos running.
Not really, the netscape.javascript.* package for interacting with Javascript and the DOM has been a standard part of Java (even the notoriously incompatible MS JVM) since the early days. Perhaps it isn't as well known as it could be due to being outside the java.* namespace.
Java developers can already develop so called RIA applications using an old technology called applets. Some of the first RIA applications used it, because ten years ago there was no such thing as cross browser Javascript and Flash was only useful for making vector animation cartoons.
<kneejerk>You mean they've wrenched control of the platform from the original developers?!!!</kneejerk>
In a large business, you will be limiting your users and doing a lot of management no matter what software you choose to run your mail servers. Your competitors will too.
I'd be prepared to put money on the licensing issues being the major reason for Apple avoiding 3G in their first generation product. Not just the cost (which comes from the chip manufacturers who hold patents over the various technologies used, not the carriers), but the uncertainty of it all with lawsuits going on all over the place and Qualcomm banned from importing their chips around the time the iPhone was launched.
The official story of battery drain is not borne out by other manufacturers' figures - which actually show less drain for data use due to the radio transmitting and receiving for shorter periods. If the iPhone is not a data centric device, then what is?
What sort of support are you expecting for a certificate? Installation support should be available from the vendor of your servers. Was it renewal or revocation you had problems with? Renewal means more money for the CA, so it should just be a matter of phoning their sales team, they'll fall over themselves to provide you with service if you have a large number of certificates to renew. Revocation - I'm not sure enough customers will have had to deal with that to get enough feedback to make a judgement.
Printer? Luxury!!!! When I were a lad, we punched 'oles in our own palms, as we didn't even 'ave punchcards yet.
Nonsense. GC in Java has never worked by counting references, and bugs due to circular references have been a thing of the past since Java 1.3 or so. Perhaps you're thinking of some of the psuedo garbage collection libraries available for C++.
Paypal Europe operates under Luxembourg law now, and they are a bank, so subject to whatever requirements Luxembourg puts on banks for handling disputes and account closures. Fire your lawyer and get a new one, as they are clearly incompetent if they have not figured this much out yet.
If Paypal is really concerned about phishing, why do they still send out emails saying their Terms and Conditions have changed please log in to your paypal account (link helpfully provided) to view the changes? Why do I need to log in to see the Terms and Conditions anyway? What if I want to see them before creating an account?
The same goes for Libya if you look closer.
Both Koreas are empty, not surprising in the case of the North, maybe the South is worried about North Korea using Google Maps to plan an invasion? Also Guyana, Suriname and French Guiana in addition to a handful of islands in the Caribbean, some of which you named.
Turkey? The only nuclear weapons on Turkish soil are the ones stored at the USAF base at Inçirlik.