MySQL is maybe more "primitive", but that keeps things simpler and there are fewer moving parts to break. If MySQL isn't ready for the corporate environment, what about COBOL?
The comparisons were done at some point in past history and are probably not all that accurate against moving targets. More a lack of interest in repeating the experiment than any attempt to mislead.
The master --> slaves replication is powerful. Cheap and effective backup, particularly offsite backup. Check the slaves periodically. There are ways of messing up the slaves that don't bother the master.
Cheap shot. Do a select before doing an update. The select is a much better place to discover that you have problems. The superfluous select has to be pretty cheap and in some contexts might have a negative cost in that it moves the overhead of reading the disks from write-time to read-time.
I wonder to what extent this exists in other languages?
Probably lots. Everywhere. As a crude approximation, 90% of the time is due to 10% of the code. Improving the "efficiency" of the 90% of the code that is responsible for only 10% of the time tends to be counter-productive. Of course there are no easy magic rules for how to improve the 10% of the code that is responsible for 90% of the time, or even identify exactly what that 10% really is. What does work is to have a sense of how long things should take and find and cure whatever is taking much longer than it should.
But what the accountants cannot and do not take into account is the PR value of a pissed off customer. Some of them have long memories and revenge is best served cold.
"Problem is, simulations are doomed to success." Like the difference between theory and practice. In theory there is no difference. In practice, there is. You simulate what you understand. The problem is in the areas that you do not understand, particularly in the areas where you do not know you do not understand. The whole point to KISS (and it's aimed at people who are NOT stupid) is that by keeping everything as simple as possible there is LESS room for Mother Nature to wreck her havok.
+ over integers, rationals, reals, complex numbers happens to be commutative, but in general + is used as the group operator for non-abelian groups.
And you were expecting.... ?? + on 16-bit integers violates closure. 32767 + 32767 = -2 (or overflow) For floating point, a+b=a+c does NOT mean that b=c. For floating point, (a+b)+c does NOT necessarily equal a+(b+c). For floating point, a*(b+c) does NOT necessarily equal (a*b)+(a*c). For floating point, sum(1/n) CONVERGES!
For instance, a carpenter with no real experience and no tools can build a table out of what they find lying around. Somehow I like that analogy.
Software engineers are embracing the engineer-on-the-fly paradigm, and that's a new idea that nobody really knows how to teach. [emphasis added]
The carpenter with no real experience and no tools must engineer-on-the-fly. And nobody taught him/her either. Somewhere in there is the essence of hacking and why there is a persistent resistance to turning the term "hacker" over to the media.
Software can be engineered, but usually is not. To be engineered, most all of the relevant factors have to be taken into account simultaneously. This has approximately the level of difficuly as solving simultaneous equations as opposed to solving the same number of equations sequentially.
Methinks that whoever invented any of the modernistic styles did exactly that, but phrased in whatever lingo the artists were using at the time. With Picasso at least, I have the impression that the artistry come through in spite of the style, not because of it. The convincer for me was in some art book, side by side, a Tolouse La Trek(sp?) and a Picasso done in that style. The difference: The Picasso was art, The Tolouse was not. You get the same effect with a workable program written in Intercal. Of course the wannabes will pick up on the style instead of the substance.
Wow, so it's either assembly or nuthin, huh? If you can code and debug effectively in assembler, you can code effectively in most other languages, even COBOL. As for the diff between a stack and a heap, how do you implement recursive coroutines without multiple stacks implemented in heap storage?
The record company spends $300,000 on independent radio promotion. You have to pay independent promotion to get your song on the radio; independent promotion is a system where the record companies use middlemen so they can pretend not to know that radio stations -- the unified broadcast system -- are getting paid to play their records.
Hmmm, smells like someone has a racket going and they don't want Napster etc. undercutting them.
Result the decisions that are made are loosely related to the original information.
There is the old game of "gossip" telephone game Probably everyone reading this has played the telephone game at one time or another. Loved by nursery school teachers everywhere, it usually goes like this: participants stand in a circle. The teacher whispers a sentence, word, or phrase into the ear of the first person in the circle. The first person whispers what they hear to the second person, the second person whispers what they hear to the third person and so on until everyone has had a turn and the last person announces what they heard. The phrase which started out "The mashed potatoes are dry" has morphed into "Last Thanksgiving, my grandmother put ex-lax in the sweet potato pie."
The more out-of-sight and automated a system is, the better is has to be. Just to break even. If anything is hidden, there is at least the perception that evil-doers *can* do things they shouldn't. While I don't necessarily trust either the Democrat or the Republican election officials, I do feel fairly safe trusting that both are in no mood to let the other side get away with much of anything. I don't have any answers, but unless anyone can at most anytime publicly ask any election official just what they are doing and expect an explanation, there will be at least a suspicion that there's "funny business" going on.
Whatever. While it may be possible to make secure software and be a "nice guy", I'll believe it when I see it (and maybe not even then;) Considering the territory, Theo actually seems pretty mellow.
that the building blocks used to build up the language must be as simple as possible.
Machine language is made up of bits. You can't get much simpler than that.
Multiplication is just a special case [of addition] And addition can be done by repitively adding one. Turing Machines are capable of computing any computable problem, but nobody acutally uses them. Way too slow!
The backtics allow strange column names in MySQL. It's actually useful for the few cases where the name that the column must be turns out to be a RESERVED WORD.
To pick a few nits. Packed decimal has no correspondence with packed C structures. IIRC, One-byte packed decimal: High-4-bits value 0 thru 9. A thru F are illegal. Low-4-bits Value C is +, D is -, F is + (unsigned). 0-9 are illegal. Two-byte packed decimal: Low-4-bits of rightmost byte is the sign as above. The left byte and the high-4-bits of the rightmost byte make up 3 decimal digits. Packed decimal always has an odd number of DECIMAL digits.
Slashdot Mirror
Good writeup.
MySQL is maybe more "primitive", but that keeps things simpler and there are fewer moving parts to break. If MySQL isn't ready for the corporate environment, what about COBOL?
The comparisons were done at some point in past history and are probably not all that accurate against moving targets. More a lack of interest in repeating the experiment than any attempt to mislead.
The master --> slaves replication is powerful. Cheap and effective backup, particularly offsite backup. Check the slaves periodically. There are ways of messing up the slaves that don't bother the master.
Cheap shot. Do a select before doing an update. The select is a much better place to discover that you have problems. The superfluous select has to be pretty cheap and in some contexts might have a negative cost in that it moves the overhead of reading the disks from write-time to read-time.
I wonder to what extent this exists in other languages?
Probably lots. Everywhere.
As a crude approximation, 90% of the time is due to 10% of the code. Improving the "efficiency" of the 90% of the code that is responsible for only 10% of the time tends to be counter-productive. Of course there are no easy magic rules for how to improve the 10% of the code that is responsible for 90% of the time, or even identify exactly what that 10% really is.
What does work is to have a sense of how long things should take and find and cure whatever is taking much longer than it should.
It is funny.
Microsoft's security is hilarious. Laugh.
History will eventually show electronic voting to be the most excellent means for subverting democracy ever invented.
Taken literally, gotta agree. If the procedures are very open it will take much longer and a lot more work to subvert the process.
But what the accountants cannot and do not take into account is the PR value of a pissed off customer. Some of them have long memories and revenge is best served cold.
"Problem is, simulations are doomed to success."
Like the difference between theory and practice. In theory there is no difference. In practice, there is.
You simulate what you understand. The problem is in the areas that you do not understand, particularly in the areas where you do not know you do not understand.
The whole point to KISS (and it's aimed at people who are NOT stupid) is that by keeping everything as simple as possible there is LESS room for Mother Nature to wreck her havok.
also violates a basic mathematical rule
.... ??
+ over integers, rationals, reals, complex numbers happens to be commutative, but in general + is used as the group operator for non-abelian groups.
And you were expecting
+ on 16-bit integers violates closure. 32767 + 32767 = -2 (or overflow)
For floating point, a+b=a+c does NOT mean that b=c.
For floating point, (a+b)+c does NOT necessarily equal a+(b+c).
For floating point, a*(b+c) does NOT necessarily equal (a*b)+(a*c).
For floating point, sum(1/n) CONVERGES!
if OSS will completely stall the world economy
It will.
It will completely stall Microsoft's world economy.
A lousy table, a lousy piece of software, that was my analogy.
Exactly!
Right.
Consider the term "escape artist". You know there is a lot of technical skill, but just technical skill is not enough.
For instance, a carpenter with no real experience and no tools can build a table out of what they find lying around.
Somehow I like that analogy.
Software engineers are embracing the engineer-on-the-fly paradigm, and that's a new idea that nobody really knows how to teach. [emphasis added]
The carpenter with no real experience and no tools must engineer-on-the-fly. And nobody taught him/her either. Somewhere in there is the essence of hacking and why there is a persistent resistance to turning the term "hacker" over to the media.
Software can be engineered, but usually is not. To be engineered, most all of the relevant factors have to be taken into account simultaneously. This has approximately the level of difficuly as solving simultaneous equations as opposed to solving the same number of equations sequentially.
Methinks that whoever invented any of the modernistic styles did exactly that, but phrased in whatever lingo the artists were using at the time. With Picasso at least, I have the impression that the artistry come through in spite of the style, not because of it. The convincer for me was in some art book, side by side, a Tolouse La Trek(sp?) and a Picasso done in that style. The difference: The Picasso was art, The Tolouse was not.
You get the same effect with a workable program written in Intercal. Of course the wannabes will pick up on the style instead of the substance.
Well, since you're tracing causality, what country does the U.S. have to thank most for its freedom? France.
(dons asbestos underwear)
Try England!
Joe Saudi might say what the cleric tells him to say vis a vis the U.S., but he does so while wearing a GAP shirt and Sketchers on his feet.
Methinks you're making his point. Joe Saudi (or Joe Redneck for that matter) buys into the "American Dream" and finds it not so satisfying.
Wow, so it's either assembly or nuthin, huh?
If you can code and debug effectively in assembler, you can code effectively in most other languages, even COBOL. As for the diff between a stack and a heap, how do you implement recursive coroutines without multiple stacks implemented in heap storage?
Hmmm, smells like someone has a racket going and they don't want Napster etc. undercutting them.
Result the decisions that are made are loosely related to the original information.
There is the old game of "gossip" telephone game
Probably everyone reading this has played the telephone game at one time or another.
Loved by nursery school teachers everywhere, it usually goes like this: participants stand in a circle. The teacher whispers a sentence, word, or phrase into the ear of the first person in the circle. The first person whispers what they hear to the second person, the second person whispers what they hear to the third person and so on until everyone has had a turn and the last person announces what they heard. The phrase which started out "The mashed potatoes are dry" has morphed into "Last Thanksgiving, my grandmother put ex-lax in the sweet potato pie."
That is WITHOUT hidden agenda and biases.
Try parallel parking.
(with a trailer;)
The more out-of-sight and automated a system is, the better is has to be. Just to break even.
If anything is hidden, there is at least the perception that evil-doers *can* do things they shouldn't.
While I don't necessarily trust either the Democrat or the Republican election officials, I do feel fairly safe trusting that both are in no mood to let the other side get away with much of anything.
I don't have any answers, but unless anyone can at most anytime publicly ask any election official just what they are doing and expect an explanation, there will be at least a suspicion that there's "funny business" going on.
french fries ---> freedom fries
french ---> freedom
Not original, but apropos.
It's not like they could fight off an invasion.
I don't think Canada is particularly worried about being invaded by Greenland.
Whatever.
While it may be possible to make secure software and be a "nice guy", I'll believe it when I see it (and maybe not even then;)
Considering the territory, Theo actually seems pretty mellow.
that the building blocks used to build up the language must be as simple as possible.
Machine language is made up of bits.
You can't get much simpler than that.
Multiplication is just a special case [of addition]
And addition can be done by repitively adding one.
Turing Machines are capable of computing any computable problem, but nobody acutally uses them. Way too slow!
The backtics allow strange column names in MySQL.
It's actually useful for the few cases where the name that the column must be turns out to be a RESERVED WORD.
To pick a few nits. Packed decimal has no correspondence with packed C structures.
IIRC, One-byte packed decimal:
High-4-bits value 0 thru 9. A thru F are illegal.
Low-4-bits Value C is +, D is -, F is + (unsigned). 0-9 are illegal.
Two-byte packed decimal:
Low-4-bits of rightmost byte is the sign as above.
The left byte and the high-4-bits of the rightmost byte make up 3 decimal digits.
Packed decimal always has an odd number of DECIMAL digits.