Indeed. There is a major school of thought (Linus Torvalds and Brian Kernighan spring to mind) that debuggers are an evil waste of time. I've always found that thinking about the problem (and reading the code again) and maybe a well-placed printf was far faster and more valuable than a debugger session.
...I read slashdot and I feel like everything is going wrong-
I think you'll find that a ridiculous percentage of us are chess players - people who can think a few moves ahead about the consequences of our actions, and possible repercusions.
It's an old trick used by companies to get rid of cybersquatters - ask the squatter how much they want for the domain, and then when they name a price, claim they're "acting in bad faith".
The OpenLazlo TFA mentioned in passing looks kind of interesting, at least enough to check out further. The source for their demos looks pretty clean and straightforward.
That's really funny. This whole campaign reminds me of nothing so much as when they were cranking up IE and telling everyone "What with ALL the sites using Active-X, (there were none) you're gonna want to be using IE, or you'll miss out on the whole Internet experience". For a while there, it became a self-fufilling prophecy, at least until everyone realized that Active-X was crap, Netscape was dead, and the net was full of sites relying on IE's "I know what you mean, you don't have to write well-formed HTML" behavior.
1. Prepare the soil.
2. Plant the wheat.
3. Weed, fertilize, water.
4. Harvest.
5. Build a flour mill.
6. Grind wheat into flour.
7. Cultivate some wild yeast.
8. Build a brick oven.
9. Mix flour, yeast and water.
10. Bake dough to make bread.
11. Make a knife.
12. Slice bread.
13. Insert bread into *NIX toaster.
Two Democratic precint captains are going through the cemetary, writing down names.
(Most non-Chicagoans laugh here, but that's not the joke.)
They come to one tombstone that's weathered and worn, so one of them stoops to rub it off.
"Come on", the other one says, "there's plenty more here".
"No", the first one says, "This guys got just as much a right to vote as everyone else".
Companies that are frequent targets of patent-infringement claims urged the Supreme Court to overturn the Federal Circuit test. The group included Intel, Cisco, Microsoft, Time Warner Inc., Viacom Inc., Micron Technology Inc. and automakers General Motors Corp., Ford Motor Co. and DaimlerChrysler AG.
And what, pray tell, is Time Warner getting patent infringement suits over? Or patenting themselves for that matter?
OK, since you answered honestly and respectfully, I'll do the same. I'll ignore that all your examples are nostalgia games, and not "Apps", which require LESS performance than games do. In those days, the top-of-the-line gaming rig was what? A 486DX @50Mhz or a P133? Running what? Direct-X 5 or 6? I'll be generous, I'll give you a 500 MHz Pentium-3 running Direct-X 7. Do you suppose a 3 GHz Prescott running Direct-X 9 could emulate 10 years ago hardware at better the performance than you had then? Never mind the order of magnititude increase in memory size at the same price, never mind the difference between the -arch386 and -arch586 compiler switches, assuming the same instruction set, do you think a processor running at (let's say) 6.5 times the speed you had back then could emulate what you had back then? Well enough not to be able to tell the difference? Me, I think yes.
The miniscule number of registers everyone complains about is irrelevant
Were it not for the opcode fetches to register-dance (because only certain registers can do certain things), or having to use memory to store intermediate results (because there aren't enough registers), or stack-based parameter passing, (not enough registers) or, again, the single accumulator (more opcode fetches and more register dancing) you might have a point. But what you're suggesting (in the rest of your post) is that having 1000 horsepower on bicycle tires is the same as having 500 horsepower on real tires - and I can't agree.
...30-year old software unmodified...
Can you name any 30-year old software that is worth running unmodified? Hell, I'll give you a break. Can you name any 10-year old software that is worth running unmodified?
Slashdot Mirror
Indeed. There is a major school of thought (Linus Torvalds and Brian Kernighan spring to mind) that debuggers are an evil waste of time. I've always found that thinking about the problem (and reading the code again) and maybe a well-placed printf was far faster and more valuable than a debugger session.
I bet they'd be interested in my design for a chair cannon.
I got to the photos before the site got borked.borked.borked - it shows solder traces cracking after repeated flexing - huge surprise.
Don't worry about it. Market forces will make it such that only the richest 3% of the population can afford the treatment.
My greatest fear for the upcoming election is that she wins the Democratic nomination - and gets clobbered in the general election.
It's an old trick used by companies to get rid of cybersquatters - ask the squatter how much they want for the domain, and then when they name a price, claim they're "acting in bad faith".
"Hilary threatened by black man" - too true. At least he's electable, which is more than can be said for Hilary.
No kidding. This just in: "Monkeys like to fuck". More at 11:00.
"Damnit Jim, I'm a doctor, not a _________!"
The OpenLazlo TFA mentioned in passing looks kind of interesting, at least enough to check out further. The source for their demos looks pretty clean and straightforward.
That's really funny. This whole campaign reminds me of nothing so much as when they were cranking up IE and telling everyone "What with ALL the sites using Active-X, (there were none) you're gonna want to be using IE, or you'll miss out on the whole Internet experience". For a while there, it became a self-fufilling prophecy, at least until everyone realized that Active-X was crap, Netscape was dead, and the net was full of sites relying on IE's "I know what you mean, you don't have to write well-formed HTML" behavior.
And the other usual tool: denial.
Making toast the *NIX way:
1. Prepare the soil.
2. Plant the wheat.
3. Weed, fertilize, water.
4. Harvest.
5. Build a flour mill.
6. Grind wheat into flour.
7. Cultivate some wild yeast.
8. Build a brick oven.
9. Mix flour, yeast and water.
10. Bake dough to make bread.
11. Make a knife.
12. Slice bread.
13. Insert bread into *NIX toaster.
Two Democratic precint captains are going through the cemetary, writing down names.
(Most non-Chicagoans laugh here, but that's not the joke.)
They come to one tombstone that's weathered and worn, so one of them stoops to rub it off.
"Come on", the other one says, "there's plenty more here".
"No", the first one says, "This guys got just as much a right to vote as everyone else".
Ah. Forgot about the cable business. Thanks.
I've voted for the TARDIS 8 or 9 times already from the same logged-in account. Then again, I'm from Chicago.
Of course, "readable" was referring to the charts, not the Perl, which, as everyone knows, is write-only.
OK, since you answered honestly and respectfully, I'll do the same. I'll ignore that all your examples are nostalgia games, and not "Apps", which require LESS performance than games do. In those days, the top-of-the-line gaming rig was what? A 486DX @50Mhz or a P133? Running what? Direct-X 5 or 6? I'll be generous, I'll give you a 500 MHz Pentium-3 running Direct-X 7. Do you suppose a 3 GHz Prescott running Direct-X 9 could emulate 10 years ago hardware at better the performance than you had then? Never mind the order of magnititude increase in memory size at the same price, never mind the difference between the -arch386 and -arch586 compiler switches, assuming the same instruction set, do you think a processor running at (let's say) 6.5 times the speed you had back then could emulate what you had back then? Well enough not to be able to tell the difference? Me, I think yes.
HAHAHAHAHAHAHAHAHA - so which one of those hasn't been recompiled in the last 10 years?