...all sorts of data about you (such as income, marital status, gender, age group, etc. etc.)... Does any company have the right to that kind of data? Does any person?... Don't you have friends who could estimate your income, marital status, gender, and age?
A small pack of high-grade explosives up against your ear is not the same thing as a battery in your shirt pocket. This sounds like a Cialis commercial explaining why it's better than Viagra.
So, can anybody in Israel with legal knowledge comment? Apparently not.
However, it seems plenty of people can act as armchair lawyers, and assume that the Israeli laws are the same as the US. Most likely, their not. We need better information.
In constrast, in Unix, you load the whole binary in memory... Not true; Many versions of Unix and compatible OS's such as Linux support demand paging. This is a very old design trick, so its not surprising that *nix and Windows both do it. The reason you can still delete running programs in *nix is that it supports deleting open files, which are kept around until the last process closes them.
Wow, that glosses over reality very nicely. The codes were all zeros until the 80's, because said generals refused to implement a system that would prevent them from "hitting back". The keys were all set by 1977, and the "all 0's" codes were only used on ICBMs stationed in the US by that time. It's worth noting that US ICBMs required dual-activated keys, so it was still secure against a single compromised person (but not two due to the bad codes). Bombs overseas had proper codes once they got PALs (which did take too long to deploy). So, while it took far too long to deploy proper security, lets at least get our facts right.
There isn't a really good reason the British should take 21 years longer than the (already late) US to deploy PALs with proper codes, and over 40 years later to use a dual-key initiation. "Someone else was late doing it" is not an excuse, especially when you are twice as late.
Sure, and instead of making high mileage vehicles, why don't we just ban cars altogether? Don't make an unqualified claim unless you are willing to stand up for it. You made the claim that you want completely linear time, which means you want to ignore the sun. You didn't even say you were willing to have a leap-hour, in which case the only way to make linear time is to wait until an entire leap-day has been accrued.
Sometimes you can have a sensible half-way solution. And before you reply, I don't think leap seconds is one of them. How is a leap-day or leap-hour a sensible solution? How is completely ignoring the sun to make linear time a sensible solution? The leap-hour, which is the smallest change, is like moving an entire time zone. Right now, official times are already pretty bad approximations of local solar time. There's no reason to make it worse.
So, what is your sensible halfway solution that maintains purely linear time? Mine is to just use two time systems tailored for each use, which we've already got today.
In this day and age, do we really have to keep lining up our time system to astronomy events Well, in that case the first thing we should do is eliminate all time zones. Go ahead, start living your life on UTC and you'll see what its like to "not line your life up to astronomy events". Unless you live near 0 deg longitude, it could be a bit difficult to coordinate with the locals. It turns out that "the sun coming up" is an important astronomic event even for non-astronomers.
What's funny is that to show the "problem" you even mention the solution. If you want linear time, use Unix Time or GPS Time. If you want time that has something to do with the sun, use UTC. Most applications only care about one or the other, and don't need to convert between the two. If you really do need to convert, there are tables for the conversion, and they change only slowly over time. You can also get the information from GPS receivers, which are becoming more pervasive over time.
Furthermore, even if you "fix" the system, historical times before 2013 will still use the old system, and necessitate keeping around all the same logic. Changing this type of thing only makes it more complicated in the long run, as you add another formula and switchover date, but you'll need to keep both sets of logic around almost indefinitely. We've got a system in place right now that deals pretty well with leap seconds, so why screw it up?
You're off by a factor of 3600. It's "leap hours" that are being proposed; We already have leap seconds. Of course, I'm not sure the math from TFA makes too much sense anyway, as I don't recall having an average of 3 or 6 leap seconds every year.
Here's a page with an illustration that makes the operation of the fountain obvious. The other page explains the operation only in text, and pictures of old devices that were constructed to be deliberately misleading.
4-5 years ahead? I remember people saying the same thing about the PowerPC chips in the early 90s. Apple's been doing a great job lately, but betting on your future, based on success in the previous generation, is far from a certainty. Just ask Sony.
A true socialist believes in universal healthcare, a minimum wage that you can support a family on, maximum working week, state funded education for everyone, unions (not US style unions), equality, taxing the rich to support the poor. I think you're being unfair. US Democrats love to talk about all those things. That's got to count for something, right?
True, they are only as real as Bush's vision of a peaceful middle east democracy brought about by force.
How about a party candidate who's willing to set realistic goals and do what (s)he says?
Makes me wonder if they'll be able to throw you in an MRI without removing your metallic objects. Or even a Terminator-style MRI-based walk-through security scanner? That scanner was from Total Recall. For better or worse, we're not that far off.
In my experience, Japanese and English density is pretty similar because Hiragana makes up a reasonable fraction of the characters, and you need a slightly bigger font than English so that the Kanji is legible. The one language I know of that is significantly more dense is Chinese.
The only way mobile internet works on compact phones is when the website is designed for it. In Japan, a website would be mad not to support mobile phones directly, but in the US this hasn't caught on nearly as much. I think that might start to change soon though.
Google has never called it the "gPhone"; Bloggers and press came up with that name since they needed to call it something. Google's name for the platform is Android.
The most important thing is that the algorithms are written up and published in peer-reviewed journals. That understanding is more important than the code itself. My RoboCup robootic soccer team published all of its source code one year, and not much came of it; Some people used it but they didn't really understand it. It's also hard to take the code and make it work with a different robot, as all the customized hardware on the robot means a lot of porting, and uncovering bugs and design limitations. Also, competition code often has its design stretched to the limit by the time the competition arrives, and if you redid it you might design it differently to make it cleaner. So, our papers have probably helped many more people than our code ever did. I did release a library along with some papers explaining it, and that worked well. But that's just a small part of the overall codebase.
Of course, it would be nice to see the code out there, but the science is more important than the implementation. However, if we were talking about an off-the-shelf robot such as a roomba or aibo, the situation is quite different.
Slashdot Mirror
I think you've been reading too much John C. Dvorak.
...all sorts of data about you (such as income, marital status, gender, age group, etc. etc.)You must be new here.
www.goog.il
However, it seems plenty of people can act as armchair lawyers, and assume that the Israeli laws are the same as the US. Most likely, their not. We need better information.
There isn't a really good reason the British should take 21 years longer than the (already late) US to deploy PALs with proper codes, and over 40 years later to use a dual-key initiation. "Someone else was late doing it" is not an excuse, especially when you are twice as late.
So, what is your sensible halfway solution that maintains purely linear time? Mine is to just use two time systems tailored for each use, which we've already got today.
Well, call me idealistic, but then we light up the fiber ourselves; start some sort of co-op, I dunno.
Sounds like 21st century hippies. In the 60s, they lit up on weed; In the 2010s, we'll light up dark fiber. FREE BANDWIDTH!What's funny is that to show the "problem" you even mention the solution. If you want linear time, use Unix Time or GPS Time. If you want time that has something to do with the sun, use UTC. Most applications only care about one or the other, and don't need to convert between the two. If you really do need to convert, there are tables for the conversion, and they change only slowly over time. You can also get the information from GPS receivers, which are becoming more pervasive over time.
Furthermore, even if you "fix" the system, historical times before 2013 will still use the old system, and necessitate keeping around all the same logic. Changing this type of thing only makes it more complicated in the long run, as you add another formula and switchover date, but you'll need to keep both sets of logic around almost indefinitely. We've got a system in place right now that deals pretty well with leap seconds, so why screw it up?
You're off by a factor of 3600. It's "leap hours" that are being proposed; We already have leap seconds. Of course, I'm not sure the math from TFA makes too much sense anyway, as I don't recall having an average of 3 or 6 leap seconds every year.
If you happen to be in Redmond, just refer to them as "features" when you communicate to the locals.
Here's a page with an illustration that makes the operation of the fountain obvious. The other page explains the operation only in text, and pictures of old devices that were constructed to be deliberately misleading.
4-5 years ahead? I remember people saying the same thing about the PowerPC chips in the early 90s. Apple's been doing a great job lately, but betting on your future, based on success in the previous generation, is far from a certainty. Just ask Sony.
True, they are only as real as Bush's vision of a peaceful middle east democracy brought about by force.
How about a party candidate who's willing to set realistic goals and do what (s)he says?
Quick, someone invent hyperbolic encryption! I think I've already seen that used here on slashdot to encode comments. Oh no wait, that's hyperbole...
Clearly you are a hat-wearing terrorist.
In my experience, Japanese and English density is pretty similar because Hiragana makes up a reasonable fraction of the characters, and you need a slightly bigger font than English so that the Kanji is legible. The one language I know of that is significantly more dense is Chinese.
The only way mobile internet works on compact phones is when the website is designed for it. In Japan, a website would be mad not to support mobile phones directly, but in the US this hasn't caught on nearly as much. I think that might start to change soon though.
Good, now can you do Acrobat next?
I, Fudan, welcome our new intelligent robot overlords.
Google has never called it the "gPhone"; Bloggers and press came up with that name since they needed to call it something. Google's name for the platform is Android.
The most important thing is that the algorithms are written up and published in peer-reviewed journals. That understanding is more important than the code itself. My RoboCup robootic soccer team published all of its source code one year, and not much came of it; Some people used it but they didn't really understand it. It's also hard to take the code and make it work with a different robot, as all the customized hardware on the robot means a lot of porting, and uncovering bugs and design limitations. Also, competition code often has its design stretched to the limit by the time the competition arrives, and if you redid it you might design it differently to make it cleaner. So, our papers have probably helped many more people than our code ever did. I did release a library along with some papers explaining it, and that worked well. But that's just a small part of the overall codebase.
Of course, it would be nice to see the code out there, but the science is more important than the implementation. However, if we were talking about an off-the-shelf robot such as a roomba or aibo, the situation is quite different.