Well, when I was there, mostly stuff just worked. German news web sites were no problem, and some major English news web sites (BBC etc) also worked most of the time. Google Mail also worked (obviously I reset my password). Notably, this was during the most recent major upheavals in Tibet. It was extremely slow, though, I give you that. However, we were using the web terminals at hostels, so that might have been a factor, I'd expect the net access at a hotel costing in excess of 10x to be more reliable.
It could erase the page and still mark it as being in use. Thus the page isn't used for wear-levelling by the drive, but if you ever rewrite to that page, it'll be a lot faster since the whole block containing the page won't have to be rewritten. Of course that still means the drive runs out of unused blocks after a while, but it's still an improvement over a drive with no TRIM support at all (or a drive used in an OS without TRIM, e.g. Ubuntu 10.04).
So who then are the right people? If you know why haven't you sent their names to the Government so they can do more than just worry about why it's taking so long? Also is it really a "news blackout" is is there really just nothing else to report? How on earth would BP enforce a news blackout anyway?
Leaving all other problems aside: if the batteries recharge as fast as the GP says (10-15 minutes), it's not inconceivable to charge them at "gas" stations while the residential power infrastructure is being upgraded.
"It may be inadvertent to collect, but keeping it requires a conscious and deliberate effort to allocate resources."
Usually, deleting some stuff is much more difficult than retaining everything, simply because it requires you to figure out what to delete and what to keep. Storage is cheap. Just saying.
I've found documentation coming out of Google to be somewhat weak. The docs for GWT, for example, are lacking in some areas - they don't even have complete Javadoc coverage AFAIK.
And using Google to look for GWT information isn't always useful, as it returns a lot of pages that no longer apply to the latest version of GWT. I also get lots of results for old Java documentation - look up anything in the Java libraries, and the results from Sun will probably be for Java 1.5 or 1.4.2 or even earlier, not Java 1.6.
That's because the Java 5 and maybe even the Java 1.4.2 docs are referenced more often than the more recent releases. Deployed more often, too, so it often makes sense to refer to the Java 5 docs since that's gonna be the runtime environment, anyway. I rarely get anything older than the J2SE5.0 docs, though -- I used to google for "java 5 keyword" to get the correct docs, but these days they are the default top result. Googling for "java 6 keyword" or java 7 keyword" reliably returns those API docs, so the problem is easily avoided.
I agree that the GWT docs are lacking. It's a rapidly moving target, though, so maybe it'll get better once it's more stable. I'm not sure, though. Anyway it's low quality is particularly noticeable since the Javadoc Sun authored is generally very high quality.
That ignores the presumed fact that things you do in the past do tend to represent people's behaviour when they're older. The humane and mature (and even the sensible) way would be to ignore this, but those are not always categories for businesses hiring or insurance companies.
Sure, you can create the field, and the db can delete those records when the time comes. But that won't delete the same records from backups, replicated copies, etc. So it wouldn't be all that difficult to access data which should have been forgotten. OTOH, for many practical purposes the data would be gone, so I guess it would be an improvement.
Yes, well that's what happens in wars... people fucking die.
Yeah. During a state of war, ie a state of government sanctioned mass murder, people die. Is that supposed to be some sort of insight? I suppose it is for someone who comes up with the two worst cases of the employment of WMDs in modern history as some sort of guiding example.
A well designed small heatsink will work better than a poorly designed large heatsink. And you're right that airflow management is important. But all things being different, I think, a heatsink with a large surface area will be more efficient than a heatsink with a smaller area. Of course, there are a lot of variables there, e.g. widely spaced fins tend to work better with low airflow.
Never heard of that one. Keyboard input always worked fine for me and plenty other people, though there was a problem with mouse input with a one-time workaround. I've been running 64-bit for a while now, but if Adobe is not fixing the security hole in the 64bit version, I guess I'll have to go back to nspluginwrapper. At least until YouTube reliably works in Firefox without Flash.
A tablet version will probably try to run apps full screen anyway, with a few possible exceptions. Ubuntu Netbook Remix already works that way, and I assume the tablet edition will take the netbook concepts one step further. Classic windowing controls don't really apply, though clearly there will still be a need to close windows/applications.
I'm in a country where liters/100km is the norm, and I think ml/km would be rather more elegant. Having a number within a unit seems rather odd. Sure, ml/km trades the number for an additional prefix, but unlike numbers, prefixes are not unusual in units; and ml is one of the most common units (in metric-land). Furthermore, the range of values is more practical: 6l/100km corresponds to 60ml/km.
Slashdot Mirror
Well, when I was there, mostly stuff just worked. German news web sites were no problem, and some major English news web sites (BBC etc) also worked most of the time. Google Mail also worked (obviously I reset my password). Notably, this was during the most recent major upheavals in Tibet. It was extremely slow, though, I give you that. However, we were using the web terminals at hostels, so that might have been a factor, I'd expect the net access at a hotel costing in excess of 10x to be more reliable.
I though so, too, but the block size would have to be 512 kB... Not sure if it's worth it.
It could erase the page and still mark it as being in use. Thus the page isn't used for wear-levelling by the drive, but if you ever rewrite to that page, it'll be a lot faster since the whole block containing the page won't have to be rewritten. Of course that still means the drive runs out of unused blocks after a while, but it's still an improvement over a drive with no TRIM support at all (or a drive used in an OS without TRIM, e.g. Ubuntu 10.04).
I'm sure there's a Greasemonkey script that removes the comments. Hell, a user CSS hack would probably do it.
So who then are the right people?
If you know why haven't you sent their names to the Government so they can do more than just worry about why it's taking so long?
Also is it really a "news blackout" is is there really just nothing else to report?
How on earth would BP enforce a news blackout anyway?
Are you astroturfing or something?
The right people would have been the Dutch.
Sending their names to the government woudn't help; they've already refused the help.
There is a kind-of blackout, ie here is CNN's take on it: http://www.youtube.com/watch?v=WpJBsjKhRTo
BP doesn't enforce the blackout, the government does.
I'd much rather have a pint of beer in a pub than I'd have a liter of anything at the Oktoberfest.
Leaving all other problems aside: if the batteries recharge as fast as the GP says (10-15 minutes), it's not inconceivable to charge them at "gas" stations while the residential power infrastructure is being upgraded.
Maybe it doesn't belong to you, but as long as it doesn't come with battery or a solar panel, the electricity sure does...
You mean you can actually move the pieces on the horizontal axis?! Suddenly the game makes a whole lot more sense!
Germany is phasing out advisory speed limits, which were always rare, anyway, and I don't think I've ever seen one for 30mph/50kph.
So just because it's impossible to be completely fair and proportionate in all situations you want to give up those metrics completely?
"It may be inadvertent to collect, but keeping it requires a conscious and deliberate effort to allocate resources."
Usually, deleting some stuff is much more difficult than retaining everything, simply because it requires you to figure out what to delete and what to keep. Storage is cheap. Just saying.
I've found documentation coming out of Google to be somewhat weak. The docs for GWT, for example, are lacking in some areas - they don't even have complete Javadoc coverage AFAIK.
And using Google to look for GWT information isn't always useful, as it returns a lot of pages that no longer apply to the latest version of GWT. I also get lots of results for old Java documentation - look up anything in the Java libraries, and the results from Sun will probably be for Java 1.5 or 1.4.2 or even earlier, not Java 1.6.
That's because the Java 5 and maybe even the Java 1.4.2 docs are referenced more often than the more recent releases. Deployed more often, too, so it often makes sense to refer to the Java 5 docs since that's gonna be the runtime environment, anyway. I rarely get anything older than the J2SE5.0 docs, though -- I used to google for "java 5 keyword" to get the correct docs, but these days they are the default top result. Googling for "java 6 keyword" or java 7 keyword" reliably returns those API docs, so the problem is easily avoided.
I agree that the GWT docs are lacking. It's a rapidly moving target, though, so maybe it'll get better once it's more stable. I'm not sure, though. Anyway it's low quality is particularly noticeable since the Javadoc Sun authored is generally very high quality.
That's what someone from the government would say!
That ignores the presumed fact that things you do in the past do tend to represent people's behaviour when they're older. The humane and mature (and even the sensible) way would be to ignore this, but those are not always categories for businesses hiring or insurance companies.
Sure, you can create the field, and the db can delete those records when the time comes. But that won't delete the same records from backups, replicated copies, etc. So it wouldn't be all that difficult to access data which should have been forgotten. OTOH, for many practical purposes the data would be gone, so I guess it would be an improvement.
You people are disgusting. The ways in which you seem to revel in another humans suffering... Very disconcerting.
Yes, well that's what happens in wars ... people fucking die.
Yeah. During a state of war, ie a state of government sanctioned mass murder, people die. Is that supposed to be some sort of insight? I suppose it is for someone who comes up with the two worst cases of the employment of WMDs in modern history as some sort of guiding example.
A well designed small heatsink will work better than a poorly designed large heatsink. And you're right that airflow management is important. But all things being different, I think, a heatsink with a large surface area will be more efficient than a heatsink with a smaller area. Of course, there are a lot of variables there, e.g. widely spaced fins tend to work better with low airflow.
Never heard of that one. Keyboard input always worked fine for me and plenty other people, though there was a problem with mouse input with a one-time workaround. I've been running 64-bit for a while now, but if Adobe is not fixing the security hole in the 64bit version, I guess I'll have to go back to nspluginwrapper. At least until YouTube reliably works in Firefox without Flash.
Small cases do limit the size of the heat sink, though.
A tablet version will probably try to run apps full screen anyway, with a few possible exceptions. Ubuntu Netbook Remix already works that way, and I assume the tablet edition will take the netbook concepts one step further. Classic windowing controls don't really apply, though clearly there will still be a need to close windows/applications.
I'm in a country where liters/100km is the norm, and I think ml/km would be rather more elegant. Having a number within a unit seems rather odd. Sure, ml/km trades the number for an additional prefix, but unlike numbers, prefixes are not unusual in units; and ml is one of the most common units (in metric-land). Furthermore, the range of values is more practical: 6l/100km corresponds to 60ml/km.
Plus, pay-per-view could pay for the whole war.
It should only be Slashdot frontpage news if the printer in question is made from a felt tip pen and LEGO.