My IQ goes up to eleven.
It is basically the same deal over and over. We need to reduce complexity in programming, so we build yet another abstraction layer. We hide the complexity from the programmer and deal with it in the infrastructure, thus creating more bugs and worse performance. The bugs get (very) slowly fixed and the performance issues are compensated by evolving hardware, which takes a few years. Such is life. If it were not for some initiatives like this one, SAP would be written in machine code.
That is not to say that this is the solution to all problems, neither that this is even the best alternative for anything, but it's just the way that software evolves, and as such, time will tell.
And an index. What the hell, give 'em all five fingers.
Link to Original Source
ROFL, I just spit my coffee all over my desk.
And here I thought that no one remembered that anymore.
Kudos to you, sir. Five-digit Slashdot UID megabonus included.
And not space travel, so unless you're already where you want to be, there's no use in being able to be when you want to be.
Especially if you're going as far back as to be in a time where long distance travel would be hard, time-consuming, or right down impossible.
If I'm nitpicking, please blame The Big Bang Theory, season 1, episode 14.
Not if the communication is not encrypted and there is any traffic at the time.
This is where I back your assumptions with the oblig. xkcd.
oh! Whoosh for me then!
(heads on to Wikipedia)
The way I see it, since it is a logical implication and not a condition, it would be better to use the "implies that" sign:
4+3+2=x+2 => 4+3+2-2=x => 4+3=x => 7=x
But I teach UNIX at my University, so I must be wrong.
You divided by zero in step five.