1,301 karma · joined June 6, 2012
As 'tormeh said, single-threaded performance has not improved as much since 2005. For example, the Passmark single-thread rating for the Athlon 64 FX-57[1] is 832 and for the i7-5930K[2] is "only" 2081.
[1] http://www.cpubenchmark.net/cpu.php?cpu=AMD+Athlon+64+FX-57
[2] https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i7-5930K...
From 1980-ish to the mid 1990s this was how "3D" dungeon crawlers worked; anyone who played Wizardry, or the Bard's Tale, or Might and Magic, or the SSI Gold Box RPGs, etc., will feel right at home.
Next Big Language
I used to go for two weeks between fill-ups in a '78 Buick but that was mostly becuase it had a 24-gallon tank (and I only drove about 20 miles a day).
Something similar -- using functionally-equivalent machine language instructions instead of synonyms -- was (is?) used by the shareware A86 assembler[1] to detect unregistered use.
From the A86 manual:
A86 takes advantage of situations in which more than one set
of opcodes can be generated for the same instruction. [...]
A86 adopts an unusual mix of choices in such situations.
This creates a code-generation "footprint" that ... will
enable me to tell ... if a non-trivial object file has
been produced by A86.
FTA: there were about 1400 exit nodes each tested about 95 times (that's where the 100,000 number comes from). And in addition to the 16 logins, there were a number of page views without login that seem to also have come from exit nodes.
Why not just decrease the autosave interval in your editor :)
>What's the purpose committing more often than logical chunks of code which can be considered in some sense "done"?
There are different degrees of "doneness". For example, (1) code that isn't finished but you don't want to lose it if the power goes out, (2) code that you're not sure if you're going to keep, but you'd like to be able to refer back to it even if you later decide to change it, (3) code that completely accomplishes its purpose in a logical and coherent manner.
I use "Ctrl-S" for (1), "git commit" to a local branch for (2), and "git rebase/git push" for (3). Maybe I'm just a sloppy programmer, but my workflow often involves writing some code, making certain changes, then realizing that what I really need is the previous version but with different changes. So for me, frequent commits on a local branch have replaced frequent saves under different filenames (foo.c, foo_old.c, foo_tried_it_this_way.c)
Yes, but I'd bet that the connotations of "hafu" in a society where mixed race is the norm are very different from those where it is unusual.
So much so that you might consider it to be a different word, even if it happens to be spelled the same.
If you can control the boot media, aren't you already past the point where you need further exploits to control the machine?
In the other 43 states, different people will have different issuance dates depending on last name/SSN/case number.
On the one hand, using the same day for eyeryone gives stores the opportunity to make sure they are fully-stocked before the "surge"; on the other, and from personal experience, having the days spread out usually means you don't have to choose between lining up at midnight, or waiting a few days for the shelves to be restocked.
"You run 'git push --force'. You are likely to be eaten by a grue."
(then you'd know it was safe)
Is that going to make it trickier for GDC/LDC to stay in sync with DMD? (Either way, it's exciting news!)
Ironically, the dmd compiler is written in C++.
Well, the point of using special-purpose chips like the ATAES132, which has a hardware implementation of AES, is so you wouldn't have to implement the algorithm in AVR.
Instead of taking something like Mono that was pre-built to run on their system, they took the CoreClr source that did not have a working build for FreeBsd, and got it to the point that it did.
(At least two of the (non-chain, family owned) local drugstores where I live already do this. For example,
I only know about this because as a kid I read a lot of pre-space-age sci-fi, and there was a story either by Heinlein or Asimov where the solution to this "danger" was to put nuclear fusion plants in orbit.
Well, you did say:
"Who'd like to sponsor? Or should I just spin up a GitHub repo for the code and a kickstarter for the prize money?"
300 billion? No. There are only around 318 million people in the US.
>PS: I'm planning to use Java for this side-project.
One place to start might be to try and write an emulator for the DCPU-16. It's a simple made-up computer that Notch (creator of Minecraft) designed for the game 0x10c.
Although the game was never finished, many people wrote emulators based on the DCPU's specifications[1]; search Github for "DCPU Java" to see several examples in that language.
[1] https://raw.githubusercontent.com/gatesphere/demi-16/master/...
If the GPL is litigated to the point of a published decision, doesn't that give the legal team of the targeted company the ability to say "actually, we know we ARE using it correctly, so buzz off"?
According to the lwn link 'JoshTriplett provided upthread, corporate general counsels often contact the Conservancy to request GPL enforcement: "Their interest, instead, is in a demonstration that the GPL has teeth so that they can be taken seriously when they tell management that the company must comply with the license terms of the code it ships. "