But for general text with all kinds of irregularities (idioms, euphemisms, allusions, metaphors, jargon, slang, all kinds of word play) translations will still suck bad.
100 years is a long time, though. There are a countable number of these idioms, euphemisms, etc. For example, if I google translate "I haven't the foggiest idea," Google gives me, "No tengo ni la más remota idea de" -- but if I translate, "foggiest" I get "más brumosa" (my emphasis in the quotes).
100 years ago, we barely had vacuum tubes -- and only diodes and triodes at that. We already have context-aware translations, albeit of limited utility. In another 100 years, I suspect our translators will be able to cope reasonably well with the subtle nuances of language.
Additionally, I've always had very good experiences with the nvidia driver supporting relatively old cards without much fuss. Older Radeon cards, on the other hand, have given me a fair amount of trouble with the closed-source drivers.
I don't think the issue should be about, "is nuclear safe," because it's emphatically not. It's like that quote about democracy -- nuclear is the worst form of energy, but it's better than all others.
Nuclear energy is, I believe, the safest form of energy (joules per fatality), and it's carbon-neutral. Storage is, relatively speaking, not a huge technological hurdle, especially when compared against the difficulty of nation-scale solar/wind.
Yeah, it's unfortunate -- a few bucks probably doesn't matter to average Joe, so it's not worth persuing...but there are many millions of average Joes, which really makes it worthwhile for T-Mobile, etc.!
GM and BMW have one fewer degree of freedom to worry about.
Staying within our atmosphere (or orbit!) is loads easier than leaving it. Of course, Boeing and Airbus do what they do with ridiculous safety, so I suppose it depends on your metric for impressiveness -- how you weight safety vs. mechanical/physical difficulty.
The carrier must pay at least $67.5 million to fund a program to pay its customers back, plus $18 million to state governments participating in the settlement and a $4.5 million penalty paid to the U.S. Treasury. If consumers’ claims go higher, T-Mobile will have to pay them, with no upper limit. Consumers who believe they were wrongly charged will be able to apply for refunds at a website set up for the purpose. That site was not immediately available.
Filesystems can be used in myriad ways. What if I want to cache a bunch of files, with the filename being some sort of hash? In this case, it would make sense for a79t5qr.png to be a different file than A79t5qR.png .
Personally, I prefer knowing that the filename I type is the filename the file gets. If I want to call something "finaldraft.txt" and "FINALdraft.txt," that should be up to me.
An AC above somewhere (comment: "polish != Polish") had a great comment: there's a difference between the filesystem and the UI. If a UI (file manager, shell, etc.) wants to reference two different files in a different fashion, fine. But the filesystem "should give back exactly what was put into it (both in terms of files and data)."
I think there is a bit of a difference, though -- email addresses and domain names are typed by hand by the "average" (read: GUI-only) user on a day-to-day basis. That filenames were case-insensitive probably made a lot more sense back when the average user had to type at a command line -- in which case yeah, it probably was a better UX to have case-insensitivity (at least, from a casual user's perspective). In today's world of GUIs, case sensitivity might not increase legibility -- but it doesn't decrease legibility either, and is (I think?) a POSIX violation.
Despite the fact that I think case-sensitivity is a Good Idea, I really like zsh's ability to tab-complete in a case-insensitive fashion:)
Perhaps, but I would argue that SSL'ing websites isn't really the right tool. If you want *everything* encrypted (your IP address, your DNS queries, etc.), then I think a fundamentally different tactic is required.
My point about not needing certain sites SSL'd is that if I'm on my favorite webcomic's page, it really doesn't matter if you're sniffing encrypted or unencrypted packets -- you have gained essentially the same information, as the website and the specific content I'm viewing are more-or-less the same. This is of course not the case with richer dynamic content (email, wikipedia, etc.).
Who knows, maybe there would be a "bug" in the shadow system that "accidently" resolved every hostname to MPAA-affiliated sites every now and again, causing massive DDoS attacks once every few hours...
Even if there's no such bug, I'm sure Sony et al. would pick up some free -- if unwanted and obscene -- CNAME entries!
But the bragging rights could be pretty cool -- it sounds like at these altitudes it would be a breathable atmosphere. Would be very cool to be the first human beings to breathe another planet's atmosphere!
Great, thanks for responding. I believe I tested various settings and found that this worked well for my setup, but perhaps my test environment was a little contrived (I think I just dd'd a few hundred megs). Will give 32768 a shot though!
Perhaps some of it could be due to videos vs. static images. For a resolution (or angular pixel density if you prefer) with clearly visible jaggies on, say, text or line art, I might not notice anything if it's a good video. Of course, if you're watching the news or something then you might have static text anyway...
Likewise, I love mine, and it works great even on raw blu ray files. No passthrough on TrueHD is the only stumbling block, but hardly a big deal as those discs usually have AC3 or similar as well.
That said, how successful have you been with high bitrate (read: raw blu ray files) over NFS shares? I'm using mine (NFS with UDP), and dd claims I'm getting north of 9MB/s, which should be plenty for the ~50Mb/s of blu ray. However, it often stumbles over NFS. Local (USB disk) is generally fine, though. Any thoughts greatly appreciated...currently, I'm using:
mount -t nfs -o nfsvers=3,udp,ro,noatime,rsize=131072,nolock $SERVER:$SHARE $MOUNTPOINT
With a compatible A/V receiver, I am able to play raw blu-ray videos on my Raspberry Pi. With an audio format that's unsupported for passthrough (e.g., TrueHD), then it's unusable (luckily, there's usually another 5.1 channel in addition to TrueHD, albeit at lower quality). Streaming over the network can be problematic for certain high-bandwidth films, but a local disk works well for almost everything I've thrown at it. (Unsure why network is an issue -- with an NFS share I can get north of 9MB/s, which should be enough...more overhead somewhere, I guess...)
My favorite was when I apt-get upgraded my (headless) machine, which would then refuse to boot. No SSH access, just an emergency shell (very annoying for a headless machine). The problem? I didn't have my external USB hard disk -- which had an/etc/fstab entry -- plugged in.
In fairness, there really aren't Good Units for dealing with this sort of thing. Yes, you can use "proper" energy units (J), but because we really don't use "metric time," a kJ/MJ/etc. isn't wonderful for everyday use (given that we're familiar with Watts).
If all you care about is running calculations and making them look pretty, then yeah...stick with SI. But if you want something to be intuitive, unfortunately, sometimes really stupid units make more sense.
We don't have a completely satisfactory theory of gravity (getting GR to play nice with quantum mechanics). Yet, we are very confident that the hypothesis that "things tend to fall" is correct.
Gravity is exceedingly complex, yet there are certain things which are evident from even a rudimentary theory of gravity -- namely, things tend to fall. CO2, likewise, has a complicated relationship to the climate -- but it is a known greenhouse gas, which has certain implications.
Slashdot Mirror
But for general text with all kinds of irregularities (idioms, euphemisms, allusions, metaphors, jargon, slang, all kinds of word play) translations will still suck bad.
100 years is a long time, though. There are a countable number of these idioms, euphemisms, etc. For example, if I google translate "I haven't the foggiest idea," Google gives me, "No tengo ni la más remota idea de" -- but if I translate, "foggiest" I get "más brumosa" (my emphasis in the quotes).
100 years ago, we barely had vacuum tubes -- and only diodes and triodes at that. We already have context-aware translations, albeit of limited utility. In another 100 years, I suspect our translators will be able to cope reasonably well with the subtle nuances of language.
Additionally, I've always had very good experiences with the nvidia driver supporting relatively old cards without much fuss. Older Radeon cards, on the other hand, have given me a fair amount of trouble with the closed-source drivers.
I use it between my my remote control and TV. Never can be too careful these days.
By echoing commands over ssh, I have my Raspberry Pi control my TV (HDMI CEC), you insensitive clod!
250,000 to 470,000 years in the future...sounds about right.
I don't think the issue should be about, "is nuclear safe," because it's emphatically not. It's like that quote about democracy -- nuclear is the worst form of energy, but it's better than all others.
Nuclear energy is, I believe, the safest form of energy (joules per fatality), and it's carbon-neutral. Storage is, relatively speaking, not a huge technological hurdle, especially when compared against the difficulty of nation-scale solar/wind.
Yeah, it's unfortunate -- a few bucks probably doesn't matter to average Joe, so it's not worth persuing...but there are many millions of average Joes, which really makes it worthwhile for T-Mobile, etc.!
GM and BMW have one fewer degree of freedom to worry about.
Staying within our atmosphere (or orbit!) is loads easier than leaving it. Of course, Boeing and Airbus do what they do with ridiculous safety, so I suppose it depends on your metric for impressiveness -- how you weight safety vs. mechanical/physical difficulty.
The carrier must pay at least $67.5 million to fund a program to pay its customers back, plus $18 million to state governments participating in the settlement and a $4.5 million penalty paid to the U.S. Treasury. If consumers’ claims go higher, T-Mobile will have to pay them, with no upper limit. Consumers who believe they were wrongly charged will be able to apply for refunds at a website set up for the purpose. That site was not immediately available.
Filesystems can be used in myriad ways. What if I want to cache a bunch of files, with the filename being some sort of hash? In this case, it would make sense for a79t5qr.png to be a different file than A79t5qR.png .
Personally, I prefer knowing that the filename I type is the filename the file gets. If I want to call something "finaldraft.txt" and "FINALdraft.txt," that should be up to me.
An AC above somewhere (comment: "polish != Polish") had a great comment: there's a difference between the filesystem and the UI. If a UI (file manager, shell, etc.) wants to reference two different files in a different fashion, fine. But the filesystem "should give back exactly what was put into it (both in terms of files and data)."
I think there is a bit of a difference, though -- email addresses and domain names are typed by hand by the "average" (read: GUI-only) user on a day-to-day basis. That filenames were case-insensitive probably made a lot more sense back when the average user had to type at a command line -- in which case yeah, it probably was a better UX to have case-insensitivity (at least, from a casual user's perspective). In today's world of GUIs, case sensitivity might not increase legibility -- but it doesn't decrease legibility either, and is (I think?) a POSIX violation.
:)
Despite the fact that I think case-sensitivity is a Good Idea, I really like zsh's ability to tab-complete in a case-insensitive fashion
Perhaps, but I would argue that SSL'ing websites isn't really the right tool. If you want *everything* encrypted (your IP address, your DNS queries, etc.), then I think a fundamentally different tactic is required.
My point about not needing certain sites SSL'd is that if I'm on my favorite webcomic's page, it really doesn't matter if you're sniffing encrypted or unencrypted packets -- you have gained essentially the same information, as the website and the specific content I'm viewing are more-or-less the same. This is of course not the case with richer dynamic content (email, wikipedia, etc.).
Yeah, I really don't care that a webcomic/news site/etc. is non-SSL.
That said, if a website has a password field, it might be a Good Idea to notify the user if it's non-SSL.
I think the 1TB/day was additional data transferred, not total.
Who knows, maybe there would be a "bug" in the shadow system that "accidently" resolved every hostname to MPAA-affiliated sites every now and again, causing massive DDoS attacks once every few hours...
Even if there's no such bug, I'm sure Sony et al. would pick up some free -- if unwanted and obscene -- CNAME entries!
But the bragging rights could be pretty cool -- it sounds like at these altitudes it would be a breathable atmosphere. Would be very cool to be the first human beings to breathe another planet's atmosphere!
http://en.wikipedia.org/wiki/A...
Great, thanks for responding. I believe I tested various settings and found that this worked well for my setup, but perhaps my test environment was a little contrived (I think I just dd'd a few hundred megs). Will give 32768 a shot though!
Perhaps some of it could be due to videos vs. static images. For a resolution (or angular pixel density if you prefer) with clearly visible jaggies on, say, text or line art, I might not notice anything if it's a good video. Of course, if you're watching the news or something then you might have static text anyway...
Likewise, I love mine, and it works great even on raw blu ray files. No passthrough on TrueHD is the only stumbling block, but hardly a big deal as those discs usually have AC3 or similar as well.
That said, how successful have you been with high bitrate (read: raw blu ray files) over NFS shares? I'm using mine (NFS with UDP), and dd claims I'm getting north of 9MB/s, which should be plenty for the ~50Mb/s of blu ray. However, it often stumbles over NFS. Local (USB disk) is generally fine, though. Any thoughts greatly appreciated...currently, I'm using:
mount -t nfs -o nfsvers=3,udp,ro,noatime,rsize=131072,nolock $SERVER:$SHARE $MOUNTPOINT
With a compatible A/V receiver, I am able to play raw blu-ray videos on my Raspberry Pi. With an audio format that's unsupported for passthrough (e.g., TrueHD), then it's unusable (luckily, there's usually another 5.1 channel in addition to TrueHD, albeit at lower quality). Streaming over the network can be problematic for certain high-bandwidth films, but a local disk works well for almost everything I've thrown at it. (Unsure why network is an issue -- with an NFS share I can get north of 9MB/s, which should be enough...more overhead somewhere, I guess...)
Did it also include a 3D init system? Something tells me I'd prefer that to systemd...
My favorite was when I apt-get upgraded my (headless) machine, which would then refuse to boot. No SSH access, just an emergency shell (very annoying for a headless machine). The problem? I didn't have my external USB hard disk -- which had an /etc/fstab entry -- plugged in.
In fairness, there really aren't Good Units for dealing with this sort of thing. Yes, you can use "proper" energy units (J), but because we really don't use "metric time," a kJ/MJ/etc. isn't wonderful for everyday use (given that we're familiar with Watts).
If all you care about is running calculations and making them look pretty, then yeah...stick with SI. But if you want something to be intuitive, unfortunately, sometimes really stupid units make more sense.
We don't have a completely satisfactory theory of gravity (getting GR to play nice with quantum mechanics). Yet, we are very confident that the hypothesis that "things tend to fall" is correct.
Gravity is exceedingly complex, yet there are certain things which are evident from even a rudimentary theory of gravity -- namely, things tend to fall. CO2, likewise, has a complicated relationship to the climate -- but it is a known greenhouse gas, which has certain implications.
Unfortunate that respecting privacy to the extent the law permits is the exception, not the norm...