"If you have a powerful enough machine then Vista's advantages remain while by far most of its disadvantages disappear. And by "powerful enough" I mean a $900 HP you could have picked up at a retail store 6 months ago. Nothing crazy."
By the time you add the cost of 3 years antivirus, 3 years other malware/bugware, etc., its cheaper to buy an iMac.
Or for that same $900, buy a lower-spec box + 2 22" lcd displays m($180 ea @tigerdirect), run linux and STILL have change left over.
The infinite monkey theorem states that a monkey hitting keys at random on a typewriter keyboard for an infinite amount of time will almost surely type a particular chosen text, such as the complete works of William Shakespeare. In this context, "almost surely" is a mathematical term with a precise meaning, and the "monkey" is not an actual monkey; rather, it is a metaphor for an abstract device that produces a random sequence of letters ad infinitum. The theorem illustrates the perils of reasoning about infinity by imagining a vast but finite number, and vice versa. The probability of a monkey typing a given string of text as long as, say, Hamlet is so tiny that, were the experiment conducted, the chance of it actually occurring during a span of time of the order of the age of the universe is minuscule but not zero.
Variants of the theorem include multiple and even infinitely many typists, and the target text varies between an entire library and a single sentence. The history of these statements can be traced back to Aristotle's Metaphysics and Cicero's De natura deorum, through Blaise Pascal and Jonathan Swift, and finally to modern statements with their iconic typewriters. In the early 20th century, Émile Borel and Arthur Eddington used the theorem to illustrate the timescales implicit in the foundations of statistical mechanics. Various Christian apologists on the one hand, and Richard Dawkins on the other, have argued about the appropriateness of the monkeys as a metaphor for evolution.
Today, popular interest in the typing monkeys is sustained by numerous appearances in literature, television and radio, music, and the Internet. A "Monkey Shakespeare Simulator" website got as far as 24 characters with "RUMOUR. Open your ears; ". In 2003 a humorous experiment was performed with six Sulawesi crested macaques, but their literary contribution was five pages consisting largely of the letter S.
"since I have never heard of a 'code monkey in boston'.
You must be new here, if you never heard, for example, the term "code monkey" or "web monkey". It has nothing to do with race (there's no such thing as "race") or ethnic origin, or geographic location.
here.
It relates to any drudge-work job, such as the hell-desk (aka help desk to the overly optimistic).
MySQL Enterprise is more than just the monitoring software...
MySQL Enterprise
Database. Monitoring. Support.
The MySQL Enterprise subscription is the only comprehensive offering of production support, monitoring tools and MySQL database software to deliver optimal performance, reliability, security, and uptime. MySQL Enterprise includes:
MySQL Enterprise Server
The MySQL Enterprise Server software is the most reliable, secure and up-to-date version for cost-effectively delivering production database applications. Subscribers receive monthly rapid updates and quarterly service packs with the latest fixes.
MySQL Enterprise Monitor
The MySQL Enterprise Monitor software provides a "Virtual DBA that monitors production database applications and minimizes security vulnerabilities, improves replication, and optimizes performance.
MySQL Production Support
MySQL Production Support enables you to maximize the availability of your database applications. Plus, with Consultative Support, receive practical advice on how to optimize your configuration, replication set-up, schema, and queries for better performance.
Contrary to what the article summary might have led some to believe, its not just a piece of software that's being made available. If you follow the link, you'll find additional links and information. Hope this helps make things a bit clearer:-)
But the name. Oh my god, the name. Anything with "my" in front of it sounds like the intended audience is a four year old. "it's mine! my computer. my space. my toybox! I'm special. This is mine!"
No, as per the quote they're offering a proprietary, non-free software product. Hence the criticism.
The proprietary, non-free software product is part of their "better support." Not all support is a monkey on the phone with an Indian accent going "Hi, my name is Mike, how may I help you?"
Most people would rather have a nice piece of software that helps them do a better job, than have to wait on the phone.
Never. There are too many incompetent lawyers out there. Too many times I've had to fire them and finish the job myself (and I'm not the only one to notice this).
Funny how you mention doctors and lawyers - lawyers keep on trying to do the same thing, to polish their turd-like image, but the public rates them closer to used car salesmen than to doctors.
How about lawyers take responsibility for their bad advice for a change? Or better yet, lets replace them with software.
"No other industry can say "you can't sue us if the product you purchased from us does not do what it was intended to do""
And here's where the GPL comes in handy.
There's the difference - you don't have to purchase free/libre open-source software; if you want to be indemnified, you can buy a distro from RedHat, Novell, Oracle, and (soon) Sun.
A contract requires a "consideration", usually payment, in return for the "good" or "service". There is no contractual arrangement between someone who downloads a free copy of linux and the authors, as the recipient of the good or service doesn't enter into an agreement to give a "consideration" for what they obtained.
I research things that will make my company perform better, or I educate myself so I can perform better for the company myself
You really ARE new here.
Besides, you are more productive if you take a break every now and then. So what you're saying is that you would rather LOOK like you're brown-nosing, while you're in fact making yourself LESS efficient, rather than taking time to talk with co-workers, etc., which improves the lines of communications in a company, and ultimately contributes more to the bottom line in terms of increased efficiencies.
Don't forget those new TPS reports. And your 35 pieces of flair.
Code doesn't just exist in some parallel universe by itself, unless its something trivial, like "hello.c".
Good code has never been hurt by the presence of good documentation, proper specifications, decent planning, frequent communications between all the parties involved, etc.
At least with crappy code and decent docs, you have a road map. Without the docs, its more a case of "you can't get there from here."
The process of speccing and documenting code forces you to think about what you're doing, rather than "hey, I know just how to code that!" Its also a good way to slow down "feature creep." "You want that feature - draw up the specs first, so we're both on the same page and understand what you want done."
I for one refuse to take part in any more conversations that start with "wouldn't it be nice if..." and end with "so it shouldn't take more than a day to implement..."
Nine times out of ten (heck, more like 99 times out of 100), the proposal doesn't even make sense from a real-world business point of view. Every coder who takes on the ultimate responsibility for a project should know how to deflect such stupidity by directing their would-be tormentor into a discussion of market gap analysis as a first step in deciding if there's a need for "feature x".
Please explain why you think its bad advice to abandon a ship when its already sinking?
If you've ever been in a situation where you've had a mess of crap code thrown at you, you'd know that that crap code didn't "just happen." It was caused by bad practices, bad management, bad leadership, bad communications, and bad vision.
Changing the coder isn't going to change any of that.
Ah, the old "if you don't like the message, blame the messenger" trick.
There's nothing that sucks the lifeblood out of a coder more than having to try to polish a turd.It is almost always quicker AND cheaper to rewrite from scratch - especially when there are no docs, no specs, and the code is crap.
When you get confronted with WTFs like code where people have over time severely modified a variable or function, but haven't bothered to change its name, so that it does something completely different from what you would expect, because they were just too lazy to do a global search-and-replace, or call the same function from 100 different places, always with the same HUGE list of parameters and structures, with different actions and side effects depending on which parameters were actually filled in... and an idiot source file naming convention... and the few comments that exist were never updated to actually reflect what the code does... and an addiction to cut-n-paste coding, with the same files and filenames in different directories doing completely different things... ALL because of the perceived need to look productive by "cutting code"...
Throw it out. Just throw it all the fuck out and start over properly. Nothing else works.
If there's no documentation, you're better off to just throw it all out.
If it wasn't adequately documented, commented, etc., it was written by people who don't understand the need for proper planning, specs, etc., and its just going to be one ungodly time sink.
Really, just toss the entire pile of shit. And start looking for another job, because you'll only end up hating yourself and feeling unclean.
I was thinking that maybe one way to defeat all this myminicity spam-linking crap would be to just repeatedly wget the same spam link. Eventually, they'll set up a block list, and then I'll be myminicity-proof until my IP changes.
I'm going to test it this weekend at home (cable IP only changes once in a blue moon) - unless someone has already tried this.
If that doesn't work, the next step would be to automatically visit every one of them - "give them too much of what they want and hope they choke on it".
Sort of like repeatedly sending large attachments to a spammer.
Crowds don't flee from burning cars any more than they flee from the scene of a burning building
They certainly do, if they are inside.
... and how the fsck do you get a crowd into a car? Round up a bunch of midgets at the local circus, stuff them in, toss some gasoline on them, and light it? That'll attract a crowd, for sure...
Crowds don't flee from burning cars any more than they flee from the scene of a burning building - they stand around and gawk. Just look at the traffic jams as rubberneckers slow down to look at a car on fire on the highway, or even just smoke coming out from under the hood.
Slashdot Mirror
"If you have a powerful enough machine then Vista's advantages remain while by far most of its disadvantages disappear. And by "powerful enough" I mean a $900 HP you could have picked up at a retail store 6 months ago. Nothing crazy."
By the time you add the cost of 3 years antivirus, 3 years other malware/bugware, etc., its cheaper to buy an iMac.
Or for that same $900, buy a lower-spec box + 2 22" lcd displays m($180 ea @tigerdirect), run linux and STILL have change left over.
Screwed up the link - need more coffee:
http://en.wikipedia.org/wiki/Infinite_monkey_theorem
"since I have never heard of a 'code monkey in boston'.
You must be new here, if you never heard, for example, the term "code monkey" or "web monkey". It has nothing to do with race (there's no such thing as "race") or ethnic origin, or geographic location.
here.
It relates to any drudge-work job, such as the hell-desk (aka help desk to the overly optimistic).
You might want tocheck it out a bit more ... TFA isn't all that accurate.
MySQL Enterprise is more than just the monitoring software ...
Contrary to what the article summary might have led some to believe, its not just a piece of software that's being made available. If you follow the link, you'll find additional links and information. Hope this helps make things a bit clearer :-)
So bug fixes, updates, etc., aren't "support"??!!!??
Your notion of support is comparatively trivial.
So my guess is you would refuse treatment for tuberculosis with mycomycin because it sounds childish?
While we're at it, why not tell the former Burmese that calling their country Myanmar was a bad ideaBut hey, I'd rather say MySQL than MS-SQL any day of the week. MS - its a debilitating disease.
The proprietary, non-free software product is part of their "better support." Not all support is a monkey on the phone with an Indian accent going "Hi, my name is Mike, how may I help you?"
Most people would rather have a nice piece of software that helps them do a better job, than have to wait on the phone.
"Leave law to the lawyers, kid."
Never. There are too many incompetent lawyers out there. Too many times I've had to fire them and finish the job myself (and I'm not the only one to notice this).
Funny how you mention doctors and lawyers - lawyers keep on trying to do the same thing, to polish their turd-like image, but the public rates them closer to used car salesmen than to doctors.
How about lawyers take responsibility for their bad advice for a change? Or better yet, lets replace them with software.
"No other industry can say "you can't sue us if the product you purchased from us does not do what it was intended to do""
And here's where the GPL comes in handy.
There's the difference - you don't have to purchase free/libre open-source software; if you want to be indemnified, you can buy a distro from RedHat, Novell, Oracle, and (soon) Sun.
A contract requires a "consideration", usually payment, in return for the "good" or "service". There is no contractual arrangement between someone who downloads a free copy of linux and the authors, as the recipient of the good or service doesn't enter into an agreement to give a "consideration" for what they obtained.
"Any of these would have been much more understandable: specialist, expert, buff, genius, nerd, advocate, certified authority, professional."
"Head may be important, but if children are desired, he'll need fork."
"tail" works.
Warning- the link in the parent poster's signature will break your heart.
And for all you who don't have display signatures turned on, here it is: Please help foster pets in need of medical care!. For once, not a myminicity link!
You really ARE new here.
Besides, you are more productive if you take a break every now and then. So what you're saying is that you would rather LOOK like you're brown-nosing, while you're in fact making yourself LESS efficient, rather than taking time to talk with co-workers, etc., which improves the lines of communications in a company, and ultimately contributes more to the bottom line in terms of increased efficiencies.
Don't forget those new TPS reports. And your 35 pieces of flair.
Code doesn't just exist in some parallel universe by itself, unless its something trivial, like "hello.c".
Good code has never been hurt by the presence of good documentation, proper specifications, decent planning, frequent communications between all the parties involved, etc.
At least with crappy code and decent docs, you have a road map. Without the docs, its more a case of "you can't get there from here."
The process of speccing and documenting code forces you to think about what you're doing, rather than "hey, I know just how to code that!" Its also a good way to slow down "feature creep." "You want that feature - draw up the specs first, so we're both on the same page and understand what you want done."
I for one refuse to take part in any more conversations that start with "wouldn't it be nice if ..." and end with "so it shouldn't take more than a day to implement ..."
Nine times out of ten (heck, more like 99 times out of 100), the proposal doesn't even make sense from a real-world business point of view. Every coder who takes on the ultimate responsibility for a project should know how to deflect such stupidity by directing their would-be tormentor into a discussion of market gap analysis as a first step in deciding if there's a need for "feature x".
Please explain why you think its bad advice to abandon a ship when its already sinking?
If you've ever been in a situation where you've had a mess of crap code thrown at you, you'd know that that crap code didn't "just happen." It was caused by bad practices, bad management, bad leadership, bad communications, and bad vision.
Changing the coder isn't going to change any of that.
"Lose all hope ye who enter therein."
Ah, the old "if you don't like the message, blame the messenger" trick.
There's nothing that sucks the lifeblood out of a coder more than having to try to polish a turd.It is almost always quicker AND cheaper to rewrite from scratch - especially when there are no docs, no specs, and the code is crap.
When you get confronted with WTFs like code where people have over time severely modified a variable or function, but haven't bothered to change its name, so that it does something completely different from what you would expect, because they were just too lazy to do a global search-and-replace, or call the same function from 100 different places, always with the same HUGE list of parameters and structures, with different actions and side effects depending on which parameters were actually filled in ... and an idiot source file naming convention ... and the few comments that exist were never updated to actually reflect what the code does ... and an addiction to cut-n-paste coding, with the same files and filenames in different directories doing completely different things ... ALL because of the perceived need to look productive by "cutting code" ...
Throw it out. Just throw it all the fuck out and start over properly. Nothing else works.
If there's no documentation, you're better off to just throw it all out.
If it wasn't adequately documented, commented, etc., it was written by people who don't understand the need for proper planning, specs, etc., and its just going to be one ungodly time sink.
Really, just toss the entire pile of shit. And start looking for another job, because you'll only end up hating yourself and feeling unclean.
It's checkm8! He's p0wn3d!
LG LRA-850 - $99.00 just before christmas, so I bought 3.
Easy to use:
- stick blank dvd in (I use rewriteables)
- asks if you want to initialize disk - hit "ok"
- show starts - hit record button
- show's over - hit eject
Wait a minute while it creates the menus and finalizes the disc, and you're done.As a bonus, it also plays divx files just fine.
"So, you are moded (sic) troll by default?"
Yeah, but that's okay ...
I was thinking that maybe one way to defeat all this myminicity spam-linking crap would be to just repeatedly wget the same spam link. Eventually, they'll set up a block list, and then I'll be myminicity-proof until my IP changes.
I'm going to test it this weekend at home (cable IP only changes once in a blue moon) - unless someone has already tried this.
If that doesn't work, the next step would be to automatically visit every one of them - "give them too much of what they want and hope they choke on it".
Sort of like repeatedly sending large attachments to a spammer.
Parent is another one of those lame myminicity spams.
If you want to consider that Cain killed off 1/4 of the human population, how about this: Adam fucked the ugliest ho in the known universe.
"how a crowd flees from a burning car"
Crowds don't flee from burning cars any more than they flee from the scene of a burning building - they stand around and gawk. Just look at the traffic jams as rubberneckers slow down to look at a car on fire on the highway, or even just smoke coming out from under the hood.