To be fair, that doesn't counter his argument, amd64 has more registers than i386 and they do make a big difference. Repeat the tests with 32-bit pointers and 64 bit registers and then get back to us.
As of today, the method he mentions would probably provide a bit better performance, assuming the processor optimizations didn't break when their expectations weren't met.
However, I think it is very short-sighted to miss the fact that about the only thing increasing these days is memory and that apps tend to grab all the address space they can get. By 2050 I can see machines with 1TB ram, but I can't see apps keeping themselves under 0xFFFFFFFF.
Furthermore, thanks to ASLR, which is a feature available now on most OSes, address space fragmentation is a problem today even for programs well under the 4Gb mark. The future is 64:64. 32 bit architectures are already dead, they just haven't realized it yet.
If Neanderthals and Humans could interbreed I'd say we both were subspecies of our common ancestor. I can't see how can they be a subspecies of us when we didn't exist yet. So either rename homo rhodesiensis to homo sapiens, or hss and hn to homo rhodesiensis sapiens and homo rhodesiensis neanderthalensis respectively.
In any case, make it a cheap computer. I don't think the ipad would work for a toddler.
I used the "adult" version of the ZX Spectrum 48k when I was ~18 months old. I even learned enough SINCLAIR BASIC to LOAD "":). However, the only program I ran was an invaders-like BASIC game and the keyboard membrane didn't survive my space spider smashing for long.
I don't really know how sustainable Chinese characters are in Mainland China, especially after Comrade Mao simplified their etymologies out, believing the Western bullshit that they were too hard. In any case, they have been in use for a few thousand years if that means anything.
In Japanese at least, literacy is steadily increasing. Twenty years ago, with 8-bit computers, kanji were appearing to be on their way out. However, as soon as IME and modern OSes appeared people started using more kanji even if they never could have written them by hand. And that means more kanji regular people can read. Recently, the number of kanji considered to be needed for basic literacy was increased to account for that.
Handwriting is suffering(The only real usage cases in modern Japanese society are resumes[=], paperwork[vv], and kanji quizes/exams[^]), but kanji themselves are here to stay.
Nah, the US military uses "military grade encryption" and "one time pads" while the white collar criminals use real algorithms created by some of the best mathematicians and triple-checked by all of the best mathematicians.
Unlike GCC as a compiler, GDB really sucks as a debugger. It is a source player, nice for high level "debugging", but as soon as you try to follow code that cannot be statically extracted from the ELF and DWARF data you are left with a blinking light and a feature-set comparable to the APPLE I MONITOR.
I doubt LLDB will fix the latter, but it'll probably wipe GDB's ass as a source player because Clang already gets a lot more and better errors and warnings than GCC.
Still, supported platforms: Mac OS X x86 and amd64. So it isn't really here yet. No need to worry.
Better yet, just buy a Sharp Netwalker, now also in tablet form, and get Linux on ARM with better specs. You can then spend your time trying to run Debian or a recent Ubuntu version from the SD card.
Your real-world usage is what exactly? Playing badly designed games?
I want to play badly designed games *while* I am compiling, listening to some music and possibly leaving my browser on with some badly written JavaScript running. I also want my CPU not to melt.
You would need at least a 5GHz CPU to match a current dual-core CPU in this area. The ongoing trend is to have more and more things running and getting updated in real time. An it has been for a long time.
Files getting indexed, illegal files getting downloaded, stupid GUIs getting rendered, music getting played, Interpreted languages getting JIT-compiled...
Gamers are still stuck in the microcomputer era. The real world isn't. And there isn't really a choice in the first place, the choice is more cores and a better experience or getting stuck at XGHz and having to pipe liquid Hydrogen into your home.
I think we will see more CPUs with more cores and likely more storage units to avoid resource starvation. More speed is just not possible.
Well, what is the efficiency of one of those sails once space garbage has poked a few holes on it?
Without knowing much, I would think that thrust is directly proportional to surface. So minus the hole, it wouldn't be that bad in principle.
However, an impact into a hair-thin layer of tin-foil spells massive damage even for tiny objects. And the larger the sail, the larger the chances it meets some macroscopic particle.
I hope this works. This would be our best chance if not for travel per se, at least to accelerate probes into unknown space up to reasonable speed.
The whole point in the original Mario games was discovering and remembering unlikely routes and timings. Random levels have to be either easier or based on sheer luck.
In fast-paced FPS(of the Q3A type) knowing the terrain is something the obviously will play in your favor. Like in Mario, it is also part of what allows players to concentrate on actually having fun instead of having to figure if there is a power-up or a bottomless pit.
Even for realistic FPS, randomness sucks. Real armies don't go into the battlefield without a briefing on the terrain. This is because locals know it perfectly and you want to kill them, not waste your time climbing what looked like a good sniping position and turned out to be an active volcano.
Being dropped to some random site in Vietnam's jungle is not fun, even in a game.
If randomness is only used to generate the levels and then they never change, that could work, and be a nice AI experiment. Otherwise, my opinion is that it would suck. Hack(6) has been always better than the clones that are completely random.
Actually lactose intolerance isn't a disease. Basically anyone not from European descent or a few African tribes becomes unable to digest lactose right after childhood. That isn't that terrible either, the lactic bacteria in your guts turn the lactose into yoghurt's, with the little side effect of CO2 production.
That said, even if you are a regular human, you can drink a cup of regular cow milk a day with no side effects.
More interesting is the fact is that Mongolians are intolerant but(used to) drink large amounts of lactose-rich mare milk, probably aided by some strain of lactase producing bacteria, just like the Japanese with their algae-decomposing ones.
No it is not, the GPL is forcing users(with users defined as people who actually have an use for the code) to release their derivative works under a crappy license.
The GPL is not only unfree, but it is also a pain in the ass for anyone distributing anything(including private mindless mass sub-users). Making a copy of a GPL BIOS for a friend, makes you no less of a criminal than copying an Apple BIOS. You have to "release" him the code and the license or face an expensive lawsuit.
They haven't come after you yet so you think you are safe? I trust them as much as I trust Microsoft with their Mono.
Like the freedom of speech the FSF purports to like so much, software freedom means you cannot say what others must do with it. I am all for software freedom. I think that knowledge has to be shared for the humankind to advance. But the GPL is yet another boulder in freedom's path. It blesses the same immoral copyright laws that cause most knowledge to be lost for all except the rich and privileged.
At this point they could as well merge with the Media Mafia and rename it to the Disney Public License DRM-certified freedom.
That said, that doesn't mean I think this violation should be unpunished. The conditions were clear before the fact. The violators must be punished. And hopefully the next time they will contribute to an actually free project.
It took me a weekend a few months ago to write a "Hello world+cat+string manipulation+malloc+free+argv+envp" program for amd64 that worked on Linux, OpenBSD and FreeBSD with the same exact binary and no emulation using mostly C code and about a dozen lines of assembly. It later degraded into a posix cross-platform mini-c and objective-c 2.0 runtime library, but you can do far more amazing things than calling the exit(2) syscall in an obsolete architecture.
Still, nontrivial programs only compile in PCC in x86 if nothing has changed as PCC doesn't really work with the old OpenBSD version of GAS for amd64 and other back-ends aren't mature enough.
Clang is great for a C++ app, but some optimizations and deviations from GCC behavior are weird and could create new bugs silently. They did for some of my programs. Many times the optimizations are technically right, relying on undefined behavior, but they still kill without a warning. They helped me to improve my code, but I for one wouldn't like to be an early adopter.
Technically it is. In addition to that, it is cognate with the Japanese word for sweetness, which doesn't make for a very good etymology. In English, on the other hand, it is a good term that won't be confused with anything else.
I don't agree that assembly is a better choice. One thing basic had that few other languages have was an easy API for quick results(graphics and text) at a level where complexity is to be frowned at.
However, I do agree that BASIC set me up to learn assembly(and by extension C, Java and all other languages I learnt) far better than C would if I had been exposed to it first. From what I see in sites like Stackoverflow, most people starting in Java or even C, nevermind functional languages, have problems understanding the most basic fundamentals of computer architecture.
Sometimes they won't understand why their O(n) algorithm doesn't run in linear time because they know nothing about garbage collection and the data types they are using. You would think C programmers would have a good understanding of the problems involved, but in the end many new timers don't quite get pointers(They are able to use a subset, but more as if it was magic) because they were never exposed to unstructured programming.
I wouldn't touch BASIC again, but it was useful to me to set a mindset.
A good way of recognizing your host from a new machine is using the visual fingerprints *and* the normal fingerprint.
You can check them using : $ ssh-keygen -lv -f ~/.ssh/known_hosts
And enable them by setting VisualHostKey.
It doesn't do anything if you are connecting to a host for the first time, though. In the end it all depends on the sort of setup you want. You always have to compromise.
approach to fighting malware. Your idea will not work. Here is why it won't work.
(x) The program running on the VM/jail/sandbox still has access to all the data you stream through it.
Specifically, your plan fails to account for
(x) L337 H4X0RZ (x) The fact that you are already running the malware (x) Who is responsible for setting the permissions (x) The fact that the sandbox needs to have some side-effect.
and the following philosophical objections may also apply:
(x) Ideas similar to yours are easy to come up with, yet none have ever been shown practical
Furthermore, this is what I think about you:
(x) This is a stupid idea, and you're a stupid person for suggesting it.
The same commands you would use for a wired network ignoring wpa-specific options, which means you can find them in the same manpage. I'd love a Linux distribution with this level of user-friendliness.
By that logic Wine is copyright Microsoft, BSD is copyright AT&T and Linux is copyright Tanebaum. None of GNU is possibly free because it all is based on pre-existing software *and* all original developers had seen AT&T code. Derivative work is work including other people's copyrighted work else you can already dump your GPL and start torrenting Windows 7 like everyone else.
If your question is, implements as many security features for exploit mitigation as OpenBSD? The answer is no. pf and openssh should work all the same but given a vulnerability, OpenBSD has a better chance of surviving it unharmed until it is fixed.
Still, FreeBSD, like Linux, is faster and scales better than OpenBSD. So you have to factor that in if you plan on running something that needs it.
Finally, in my opinion, and always from the command line, OpenBSD ~= FreeBSD > ? > Linux as far as ease of use is concerned.
Slashdot Mirror
A 3D T-Rex chased people around on ZX-81s with 1024 bytes of RAM two years before Elite was published.
http://en.wikipedia.org/wiki/3D_Monster_Maze
To be fair, that doesn't counter his argument, amd64 has more registers than i386 and they do make a big difference. Repeat the tests with 32-bit pointers and 64 bit registers and then get back to us.
As of today, the method he mentions would probably provide a bit better performance, assuming the processor optimizations didn't break when their expectations weren't met.
However, I think it is very short-sighted to miss the fact that about the only thing increasing these days is memory and that apps tend to grab all the address space they can get. By 2050 I can see machines with 1TB ram, but I can't see apps keeping themselves under 0xFFFFFFFF.
Furthermore, thanks to ASLR, which is a feature available now on most OSes, address space fragmentation is a problem today even for programs well under the 4Gb mark. The future is 64:64. 32 bit architectures are already dead, they just haven't realized it yet.
If Neanderthals and Humans could interbreed I'd say we both were subspecies of our common ancestor. I can't see how can they be a subspecies of us when we didn't exist yet. So either rename homo rhodesiensis to homo sapiens, or hss and hn to homo rhodesiensis sapiens and homo rhodesiensis neanderthalensis respectively.
In any case, make it a cheap computer. I don't think the ipad would work for a toddler.
I used the "adult" version of the ZX Spectrum 48k when I was ~18 months old. I even learned enough SINCLAIR BASIC to LOAD "" :). However, the only program I ran was an invaders-like BASIC game and the keyboard membrane didn't survive my space spider smashing for long.
I don't really know how sustainable Chinese characters are in Mainland China, especially after Comrade Mao simplified their etymologies out, believing the Western bullshit that they were too hard. In any case, they have been in use for a few thousand years if that means anything.
In Japanese at least, literacy is steadily increasing. Twenty years ago, with 8-bit computers, kanji were appearing to be on their way out. However, as soon as IME and modern OSes appeared people started using more kanji even if they never could have written them by hand. And that means more kanji regular people can read. Recently, the number of kanji considered to be needed for basic literacy was increased to account for that.
Handwriting is suffering(The only real usage cases in modern Japanese society are resumes[=], paperwork[vv], and kanji quizes/exams[^]), but kanji themselves are here to stay.
Nah, the US military uses "military grade encryption" and "one time pads" while the white collar criminals use real algorithms created by some of the best mathematicians and triple-checked by all of the best mathematicians.
Unlike GCC as a compiler, GDB really sucks as a debugger. It is a source player, nice for high level "debugging", but as soon as you try to follow code that cannot be statically extracted from the ELF and DWARF data you are left with a blinking light and a feature-set comparable to the APPLE I MONITOR.
I doubt LLDB will fix the latter, but it'll probably wipe GDB's ass as a source player because Clang already gets a lot more and better errors and warnings than GCC.
Still, supported platforms: Mac OS X x86 and amd64. So it isn't really here yet. No need to worry.
Better yet, just buy a Sharp Netwalker, now also in tablet form, and get Linux on ARM with better specs.
You can then spend your time trying to run Debian or a recent Ubuntu version from the SD card.
Your real-world usage is what exactly? Playing badly designed games?
I want to play badly designed games *while* I am compiling, listening to some music and possibly leaving my browser on with some badly written JavaScript running. I also want my CPU not to melt.
You would need at least a 5GHz CPU to match a current dual-core CPU in this area. The ongoing trend is to have more and more things running and getting updated in real time. An it has been for a long time.
Files getting indexed, illegal files getting downloaded, stupid GUIs getting rendered, music getting played, Interpreted languages getting JIT-compiled ...
Gamers are still stuck in the microcomputer era. The real world isn't. And there isn't really a choice in the first place, the choice is more cores and a better experience or getting stuck at XGHz and having to pipe liquid Hydrogen into your home.
I think we will see more CPUs with more cores and likely more storage units to avoid resource starvation. More speed is just not possible.
I don't think Loongson is dead just yet.
MIPS64 for you. They even bought a license after doing it the arr way.
http://en.wikipedia.org/wiki/Loongson
Well, what is the efficiency of one of those sails once space garbage has poked a few holes on it?
Without knowing much, I would think that thrust is directly proportional to surface. So minus the hole, it wouldn't be that bad in principle.
However, an impact into a hair-thin layer of tin-foil spells massive damage even for tiny objects. And the larger the sail, the larger the chances it meets some macroscopic particle.
I hope this works. This would be our best chance if not for travel per se, at least to accelerate probes into unknown space up to reasonable speed.
Do you actually play games?
The whole point in the original Mario games was discovering and remembering unlikely routes and timings. Random levels have to be either easier or based on sheer luck.
In fast-paced FPS(of the Q3A type) knowing the terrain is something the obviously will play in your favor. Like in Mario, it is also part of what allows players to concentrate on actually having fun instead of having to figure if there is a power-up or a bottomless pit.
Even for realistic FPS, randomness sucks. Real armies don't go into the battlefield without a briefing on the terrain. This is because locals know it perfectly and you want to kill them, not waste your time climbing what looked like a good sniping position and turned out to be an active volcano.
Being dropped to some random site in Vietnam's jungle is not fun, even in a game.
If randomness is only used to generate the levels and then they never change, that could work, and be a nice AI experiment. Otherwise, my opinion is that it would suck. Hack(6) has been always better than the clones that are completely random.
Actually lactose intolerance isn't a disease. Basically anyone not from European descent or a few African tribes becomes unable to digest lactose right after childhood. That isn't that terrible either, the lactic bacteria in your guts turn the lactose into yoghurt's, with the little side effect of CO2 production.
That said, even if you are a regular human, you can drink a cup of regular cow milk a day with no side effects.
More interesting is the fact is that Mongolians are intolerant but(used to) drink large amounts of lactose-rich mare milk, probably aided by some strain of lactase producing bacteria, just like the Japanese with their algae-decomposing ones.
No it is not, the GPL is forcing users(with users defined as people who actually have an use for the code) to release their derivative works under a crappy license.
The GPL is not only unfree, but it is also a pain in the ass for anyone distributing anything(including private mindless mass sub-users). Making a copy of a GPL BIOS for a friend, makes you no less of a criminal than copying an Apple BIOS. You have to "release" him the code and the license or face an expensive lawsuit.
They haven't come after you yet so you think you are safe? I trust them as much as I trust Microsoft with their Mono.
Like the freedom of speech the FSF purports to like so much, software freedom means you cannot say what others must do with it. I am all for software freedom. I think that knowledge has to be shared for the humankind to advance. But the GPL is yet another boulder in freedom's path. It blesses the same immoral copyright laws that cause most knowledge to be lost for all except the rich and privileged.
At this point they could as well merge with the Media Mafia and rename it to the Disney Public License DRM-certified freedom.
That said, that doesn't mean I think this violation should be unpunished. The conditions were clear before the fact. The violators must be punished. And hopefully the next time they will contribute to an actually free project.
Good try, but actually it is 92.951% +-0.0003. You can find the source here.
It took me a weekend a few months ago to write a "Hello world+cat+string manipulation+malloc+free+argv+envp" program for amd64 that worked on Linux, OpenBSD and FreeBSD with the same exact binary and no emulation using mostly C code and about a dozen lines of assembly.
It later degraded into a posix cross-platform mini-c and objective-c 2.0 runtime library, but you can do far more amazing things than calling the exit(2) syscall in an obsolete architecture.
Still, nontrivial programs only compile in PCC in x86 if nothing has changed as PCC doesn't really work with the old OpenBSD version of GAS for amd64 and other back-ends aren't mature enough.
Clang is great for a C++ app, but some optimizations and deviations from GCC behavior are weird and could create new bugs silently. They did for some of my programs. Many times the optimizations are technically right, relying on undefined behavior, but they still kill without a warning. They helped me to improve my code, but I for one wouldn't like to be an early adopter.
Technically it is.
In addition to that, it is cognate with the Japanese word for sweetness, which doesn't make for a very good etymology.
In English, on the other hand, it is a good term that won't be confused with anything else.
I don't agree that assembly is a better choice. One thing basic had that few other languages have was an easy API for quick results(graphics and text) at a level where complexity is to be frowned at.
However, I do agree that BASIC set me up to learn assembly(and by extension C, Java and all other languages I learnt) far better than C would if I had been exposed to it first. From what I see in sites like Stackoverflow, most people starting in Java or even C, nevermind functional languages, have problems understanding the most basic fundamentals of computer architecture.
Sometimes they won't understand why their O(n) algorithm doesn't run in linear time because they know nothing about garbage collection and the data types they are using. You would think C programmers would have a good understanding of the problems involved, but in the end many new timers don't quite get pointers(They are able to use a subset, but more as if it was magic) because they were never exposed to unstructured programming.
I wouldn't touch BASIC again, but it was useful to me to set a mindset.
A good way of recognizing your host from a new machine is using the visual fingerprints *and* the normal fingerprint.
You can check them using :
$ ssh-keygen -lv -f ~/.ssh/known_hosts
And enable them by setting VisualHostKey.
It doesn't do anything if you are connecting to a host for the first time, though.
In the end it all depends on the sort of setup you want. You always have to compromise.
Your post advocates a
(x) technical ( ) legislative ( ) market-based ( ) vigilante
approach to fighting malware. Your idea will not work. Here is why it won't work.
(x) The program running on the VM/jail/sandbox still has access to all the data you stream through it.
Specifically, your plan fails to account for
(x) L337 H4X0RZ
(x) The fact that you are already running the malware
(x) Who is responsible for setting the permissions
(x) The fact that the sandbox needs to have some side-effect.
and the following philosophical objections may also apply:
(x) Ideas similar to yours are easy to come up with, yet none have ever
been shown practical
Furthermore, this is what I think about you:
(x) This is a stupid idea, and you're a stupid person for suggesting it.
In OpenBSD you would do:
# ifconfig wpi0 -wpa -wpapsk `wpa-psk network password`
# dhclient wpi0
The same commands you would use for a wired network ignoring wpa-specific options, which means you can find them in the same manpage. I'd love a Linux distribution with this level of user-friendliness.
By that logic Wine is copyright Microsoft, BSD is copyright AT&T and Linux is copyright Tanebaum. None of GNU is possibly free because it all is based on pre-existing software *and* all original developers had seen AT&T code.
Derivative work is work including other people's copyrighted work else you can already dump your GPL and start torrenting Windows 7 like everyone else.
If your question is, implements as many security features for exploit mitigation as OpenBSD? The answer is no. pf and openssh should work all the same but given a vulnerability, OpenBSD has a better chance of surviving it unharmed until it is fixed.
Still, FreeBSD, like Linux, is faster and scales better than OpenBSD. So you have to factor that in if you plan on running something that needs it.
Finally, in my opinion, and always from the command line, OpenBSD ~= FreeBSD > ? > Linux as far as ease of use is concerned.
In Soviet Russia, Shakespeare misspells THEE!