Download now to continue keeping your computer secure. Microsoft's idea of security. It's really just as secure after the download and patch as it was before;) I stopped messing with patches a couple of years ago, and am probably much safer than anyone who is almost current.
We not only have the RIGHT to criticize our gov't, we have the DUTY. Good point. Probably many more honest, well-intentioned government officials than there are corrupt ones, but without scrutiny and public clammoring, the level of corruption tends to be monotonically increasing. Who watches the watchers? With or without the complainers: With the complainers, do something wrong and get caught at it. You just proved that the complainers were right all along. Get enough public outcry against what they haven't done yet, and they won't do it.
I have coworkers who have installed exactly no extra programs, who only use Word and Excel and IE Word and Excel and IE *are* extra programs, and likely major causes of instability. For hang on shut down, try the power key. Windows doesn't like it, but I've found it's a bit safer than letting Windows go through its shutdown sequence.
...concluded it was impossible to be both a good programer and a good musician. There's a skill set common to both that's something of a scarce resource. If you concentrate on one, you lose concentration on the other.
But our standards are good! We have so many to choose from! Wisecrack, but a lot of truth in there. Many standards. Better odds of being able to find a good fit. The real payout comes from such as using KDE apps on a GNOME desktop and using GNOME apps on a KDE desktop. The BSDs running native LINUX binaries, sometimes better than under LINUX it seems some claim. Anybody particularly concerned by internal confilicts will be buying support from such as Red Hat, IBM or Sun.
Then come marketing and promotion costs -- perhaps the most expensive part of the music business today. They include increasingly expensive video clips, public relations, tour support, marketing campaigns, and promotion to get the songs played on the radio. For example, when you hear a song played on the radio -- that didn't just happen! Labels make investments in artists by paying for both the production and the promotion of the album, and promotion is very expensive. New technology such as the Internet offers new ways for artists to reach music fans, but it still requires that some entity, whether it is a traditional label or another kind of company, market and promote that artist so that fans are aware of new releases.
Hmmmm. Two ways for the public to hear the music for free. P2P sharing or this very expensive promotion to get the songs played on the radio. Seems like maybe RIAA is complaining about being squeezed out of a very lucrative racket.
Methinks maybe the primary failure of teaching is the idea that there is one right way to do it. And that's what the student had better reproduce on quizes and exams.
Magic, art, engineering, science. Murky boundaries. There is a long thin tie between theory and practice. It stretches a long, long ways but not indefinitely. Engineering uses science, must be aware of theory, can be artistic (as in ugly is bad), but must always be practical. Given a problem, engineering is satisfied with one reasonable and doable answer. Mathematics, especially pure math, wants all answers, whether or not reasonable or doable. Look at Knuth's Art of Computer Programming. The content is very much "Engineering computer alogrithms", but the practice is sufficiently advanced from the theory that the author felt compelled to call it "Art". "Computer Art" would be even more misleading than "Computer Science". Physics is definitely one of the sciences. When pressed, the best one can say is that physics is what physicists do and physicists are the people who do physics. That definition is circular, unscientific, and artistic. There is definitely an artistic sense of what is and is not physics.
I've seen bizzare problems with errors and bugs, with solutions that sometimes resemble the artistic. Upon closer ananlysis the problems can be attributed to exact scientifically provable reasons, The thing is you have to get the programs working before you have the time and resources to do the closer analysis. There is some quote to the effect that any sufficiently advanced technology is indistinguishable from magic.
"Buzzwords" has the connotation of empty talk, but the concepts behind these terms are very strong. He's giving you an idea of how strong. Take a large complex problem. Chop it up into isolated almost non-interacting pieces. Use the worst possible language for each piece. Watch it outperform and be more robust than any single language. Such is the power of the factorial. I suspect he's right about factorial. Exponential is too much. Square or cube is too little. You never get rid of all the bugs. Single bugs often can't even show themselves. But watch out for when the bugs get together and breed.
Because it is appropriate and proper to black box the database from the front end developers. Oh, I very definitely see your point. MySQL gives you no protection from your front end developers, and its use should be restricted to situations where you do not need protection from your front end developers. It's a very different world-view.
Those bigger DB's run the biggest stuff for a reason. There's no way that MySQL (as it is today) could handle the loads that they do. MySQL is very fast because it does not have to deal with the complications of having multiple simultaneous versions of a table so that readers and writers can proceed simultaneously. Slow readers mix badly with writers, although it should be workable if you put the slow readers on a slaved mysql. Once you reach the point where MySQL becomes too congested, expect the cost to go up an order of magnitude. There's a reason mysql (the client) comes back with how long the query took, and it's not bragging rights.
Let's say that Database package A is made by a huge corp and package B is like MySQL, free, open source, etc.. Well, I can give you an example. dBASE5 has a problem that can destroy records in a database. This problem will never be fixed. The problem is reproducable, but not by anything small and simple. First determined by stepping through a program where looking up a shipto address would delete a recently entered Sales Order. The statement where the Sales order was deleted was not related to Sales Orders. Messing with CMDSPY I was able to determine that under some (unknown) circumstances dBASE5 would write out the initial 6 (IIRC) bytes of most OTHER databases. Given the practicalities, the only thing feasible is to recode to avoid the problem. With such as MySQL, any such bug would be traced, found, and obliterated. Using a full production system to trace down an elusive bug (which won't show up on anything small) is very viable if the time to fix it is no more than the time to work around it. For the vendor to fix it, the vendor has to be able to replicate it. If it fails on your machine and works on the vendor's machine, what *CAN* the vendor do?
The race is not always to the swift or the battle to the strong, but that's the way to bet. (or something like that)
It is not the case that EVERYTHING Microsoft does is completely bad. EVERYTHING Microsoft does IS NOT bad! Sure, they've done stuff in the past that WAS WRONG, Sure, they've done stuff in the past that you don't like, but it is possible that they might do something not wrong. but it doesn't mean everything they do is wrong.
How to make something 99.44% wrong sound like it's right THIS TIME.
It is not the case that EVERYTHING Microsoft does is completely bad. Surely there exists an example. Conspicouous by its absence.
Resolution. Serif fonts are very bad at low resolution. Sans-serif fonts are like cartoon stick figures and can be very readable at lousy resolutions. Good serif fonts depend on a continually varying line width which requires extremely high resolution to duplicate. (Shades of grey (Antialiasing) helps somewhat.) Look at newsprint under a compound magnifying glass sometime.
Methinks you're onto something with the idea of circular dependence. Views can ameliorate the effects of bad database design. Whether or not this is a good idea depends. Hiding implementation details can be good, but. Hiding soil conditions from architects does not make for good skyscrapers. IMNSHO MySQL does an excellent job of picking the right point of abstracting. Solving business logic within the database seems like it could get counterproductive in a hurry.
Hmmm... I also see Java being seven years old and.NET being essentially 0. Not a really fair comparison. It's a fair comparison if I've got to depend on it. Plus there's IBM and Sun to keep each other honest.
How much $$$ in taxes would the US loose if microsoft would be a much smaller company? The US would gain taxes from moneys saved, hence increasing taxable income, by companies not so adept at avoiding tax as Microsoft. A rather substantial gain I would imagine.
because it removes ownership from a single person. True. It's owned by each person who has the program. Not shared ownership, but each person fully owns it and can do anything they like with it (except depriving other owners of their rights). This increases, guess what? CAPITAL!
Slashdot Mirror
Download now to continue keeping your computer secure. ;) I stopped messing with patches a couple of years ago, and am probably much safer than anyone who is almost current.
Microsoft's idea of security. It's really just as secure after the download and patch as it was before
We not only have the RIGHT to criticize our gov't, we have the DUTY.
Good point.
Probably many more honest, well-intentioned government officials than there are corrupt ones, but without scrutiny and public clammoring, the level of corruption tends to be monotonically increasing. Who watches the watchers?
With or without the complainers: With the complainers, do something wrong and get caught at it. You just proved that the complainers were right all along. Get enough public outcry against what they haven't done yet, and they won't do it.
I have coworkers who have installed exactly no extra programs, who only use Word and Excel and IE
Word and Excel and IE *are* extra programs, and likely major causes of instability.
For hang on shut down, try the power key. Windows doesn't like it, but I've found it's a bit safer than letting Windows go through its shutdown sequence.
...concluded it was impossible to be both a good programer and a good musician.
There's a skill set common to both that's something of a scarce resource. If you concentrate on one, you lose concentration on the other.
Who *doesn't* use Word to code and edit configuration files?
So that's what screws up the Registry.
Lies, Damn Lies, Stastics, Benchmarks, Studies.
But our standards are good! We have so many to choose from!
Wisecrack, but a lot of truth in there.
Many standards. Better odds of being able to find a good fit.
The real payout comes from such as using KDE apps on a GNOME desktop and using GNOME apps on a KDE desktop. The BSDs running native LINUX binaries, sometimes better than under LINUX it seems some claim.
Anybody particularly concerned by internal confilicts will be buying support from such as Red Hat, IBM or Sun.
Then come marketing and promotion costs -- perhaps the most expensive part of the music business today. They include increasingly expensive video clips, public relations, tour support, marketing campaigns, and promotion to get the songs played on the radio. For example, when you hear a song played on the radio -- that didn't just happen! Labels make investments in artists by paying for both the production and the promotion of the album, and promotion is very expensive. New technology such as the Internet offers new ways for artists to reach music fans, but it still requires that some entity, whether it is a traditional label or another kind of company, market and promote that artist so that fans are aware of new releases.
Hmmmm. Two ways for the public to hear the music for free. P2P sharing or this very expensive promotion to get the songs played on the radio. Seems like maybe RIAA is complaining about being squeezed out of a very lucrative racket.
Reliability is not an issue in the Windows based systems that I build.
For most of us, reliability is very much an issue in anything we build.
Methinks maybe the primary failure of teaching is the idea that there is one right way to do it. And that's what the student had better reproduce on quizes and exams.
Magic, art, engineering, science. Murky boundaries.
There is a long thin tie between theory and practice. It stretches a long, long ways but not indefinitely.
Engineering uses science, must be aware of theory, can be artistic (as in ugly is bad), but must always be practical.
Given a problem, engineering is satisfied with one reasonable and doable answer. Mathematics, especially pure math, wants all answers, whether or not reasonable or doable.
Look at Knuth's Art of Computer Programming. The content is very much "Engineering computer alogrithms", but the practice is sufficiently advanced from the theory that the author felt compelled to call it "Art".
"Computer Art" would be even more misleading than "Computer Science".
Physics is definitely one of the sciences. When pressed, the best one can say is that physics is what physicists do and physicists are the people who do physics. That definition is circular, unscientific, and artistic. There is definitely an artistic sense of what is and is not physics.
I've seen bizzare problems with errors and bugs, with solutions that sometimes resemble the artistic. Upon closer ananlysis the problems can be attributed to exact scientifically provable reasons,
The thing is you have to get the programs working before you have the time and resources to do the closer analysis. There is some quote to the effect that any sufficiently advanced technology is indistinguishable from magic.
FORTRAN, at least on early IBM OS/360 didn't like the IO in the OS and did their own thing. Didn't exactly help matters.
"Buzzwords" has the connotation of empty talk, but the concepts behind these terms are very strong.
He's giving you an idea of how strong.
Take a large complex problem. Chop it up into isolated almost non-interacting pieces. Use the worst possible language for each piece. Watch it outperform and be more robust than any single language. Such is the power of the factorial.
I suspect he's right about factorial. Exponential is too much. Square or cube is too little.
You never get rid of all the bugs. Single bugs often can't even show themselves. But watch out for when the bugs get together and breed.
Because it is appropriate and proper to black box the database from the front end developers.
Oh, I very definitely see your point.
MySQL gives you no protection from your front end developers, and its use should be restricted to situations where you do not need protection from your front end developers. It's a very different world-view.
Those bigger DB's run the biggest stuff for a reason. There's no way that MySQL (as it is today) could handle the loads that they do.
MySQL is very fast because it does not have to deal with the complications of having multiple simultaneous versions of a table so that readers and writers can proceed simultaneously. Slow readers mix badly with writers, although it should be workable if you put the slow readers on a slaved mysql. Once you reach the point where MySQL becomes too congested, expect the cost to go up an order of magnitude. There's a reason mysql (the client) comes back with how long the query took, and it's not bragging rights.
I hate it when that happens.
Me too. I don't just mean I hate it when my code screws up. It has to do with the rightness of the code itself.
Let's say that Database package A is made by a huge corp and package B is like MySQL, free, open source, etc..
Well, I can give you an example. dBASE5 has a problem that can destroy records in a database. This problem will never be fixed. The problem is reproducable, but not by anything small and simple. First determined by stepping through a program where looking up a shipto address would delete a recently entered Sales Order. The statement where the Sales order was deleted was not related to Sales Orders. Messing with CMDSPY I was able to determine that under some (unknown) circumstances dBASE5 would write out the initial 6 (IIRC) bytes of most OTHER databases. Given the practicalities, the only thing feasible is to recode to avoid the problem.
With such as MySQL, any such bug would be traced, found, and obliterated. Using a full production system to trace down an elusive bug (which won't show up on anything small) is very viable if the time to fix it is no more than the time to work around it. For the vendor to fix it, the vendor has to be able to replicate it. If it fails on your machine and works on the vendor's machine, what *CAN* the vendor do?
The race is not always to the swift or the battle to the strong, but that's the way to bet. (or something like that)
It is not the case that EVERYTHING Microsoft does is completely bad.
EVERYTHING Microsoft does IS NOT bad!
Sure, they've done stuff in the past that WAS WRONG,
Sure, they've done stuff in the past that you don't like,
but it is possible that they might do something not wrong.
but it doesn't mean everything they do is wrong.
How to make something 99.44% wrong sound like it's right THIS TIME.
It is not the case that EVERYTHING Microsoft does is completely bad.
Surely there exists an example. Conspicouous by its absence.
Resolution. Serif fonts are very bad at low resolution. Sans-serif fonts are like cartoon stick figures and can be very readable at lousy resolutions. Good serif fonts depend on a continually varying line width which requires extremely high resolution to duplicate. (Shades of grey (Antialiasing) helps somewhat.) Look at newsprint under a compound magnifying glass sometime.
Methinks you're onto something with the idea of circular dependence. Views can ameliorate the effects of bad database design. Whether or not this is a good idea depends. Hiding implementation details can be good, but. Hiding soil conditions from architects does not make for good skyscrapers. IMNSHO MySQL does an excellent job of picking the right point of abstracting. Solving business logic within the database seems like it could get counterproductive in a hurry.
Exposure. Ridicule. Why listen to dead music? Try your grandparent's music. It might surprise you.
Guild of scribes blocking the printing press.
Whalers blocking kerosine.
Ferry boat operators blocking bridges.
Hmmm... I also see Java being seven years old and .NET being essentially 0. Not a really fair comparison.
It's a fair comparison if I've got to depend on it.
Plus there's IBM and Sun to keep each other honest.
How much $$$ in taxes would the US loose if microsoft would be a much smaller company?
The US would gain taxes from moneys saved, hence increasing taxable income, by companies not so adept at avoiding tax as Microsoft. A rather substantial gain I would imagine.
because it removes ownership from a single person.
True. It's owned by each person who has the program. Not shared ownership, but each person fully owns it and can do anything they like with it (except depriving other owners of their rights). This increases, guess what? CAPITAL!