douse the R's in the same shit they gave hillary. DROWN them in it. let them realize that any weapon you use, the other side will use, when its THEIR turn.
Nope. That's the same kind of thinking that gave rise to Fox News. Left-bias in mainstream media? We'll show them some biased reporting. Escalation ensues. Retaliation doesn't teach anything you intend it to teach.
Now parody and satire, they may be good for something. They may actually raise awareness if done skillfully. But responding in mindless kind just loses eyes and teeth.
The real Bechdel test for porn would portray a woman intimate with another woman, in a way that would actually turn on another woman.
I'm too busy to research it now but I suspect most porn would fail this test.
What would really answer the question, especially after this "got sloppy" speech, would be a statistically significant blip in the purging of hackers in North Korea, versus the level of giggling from hackers in Russia.
It's fashionable to cite the Dunning-Kruger effect as evidence of human dark natures: overconfidence, insecurity, or the foolish tendency of the masses to overvalue bravado. But what of the advantages?
If the optimal knowledge and skill to make a decision is not the same as maximal knowledge and skill, then there's a backside to the advantage curve. More than diminishing returns, competence beyond a certain point may hinder and hobble decision making. Mental resources are finite. There may be such a thing as knowing too much.
Maybe there's a mental organ that tries to guess when we've learned enough and it's time to act. In fine-tuning any sensibility, it's the misfiring that gains undue attention. Certainly the headlines of any age are rich with examples of right action flummoxed by call for more study. To the extent that a company or a family or a nation needs a leader at all, is the best party always the smartest duck in the room? To the extent not, the sliver of human nature that recognizes this could be branded Dunning-Kruger and yet may have deep worth.
The most effective team may have the first-rate thinkers second in command.
ImprovEverywhere needs to organize a mob of camera-wielding agents. The Parisian restaurant of late infamy would be ideal of course, but honestly, any old McDonalds would do. If they used solid state devices with stroboscopic illumination, then it would be a
I'm skeptical that environmental damage is really the primary export here. And that it's the only sinister one. My local landfill (Brunswick, Maine, US) charges for almost every kind of trash except e-trash, which they accept for free, off to the side in a special warehouse. I speculate someone, somewhere must be paying them for it. Picture some scrappy, third-world geek lord of the junkyard, who frankensteins together usable stuff. Now I'd love to hear his story. It's not just motherboards and memory chips and material tangibles he has to work with is it? There must be the occasional windfall from unerased hard drives.
I don't understand why so many SQL references contain separate sections for different DBMSs.... Dammit, SQL has been standardized for twenty years! Shouldn't I able to write just SQL by now? --bunratty
You know I really intended to make a comprehensive SQL reference from the start, covering MySQL, Microsoft, Oracle and possibly Postgre. And I stubbornly held onto that goal for 80% of the project. But I gave it up for two reasons. For one, researching MySQL took so long, I knew the release would delay another year if I researched Microsoft, Oracle and Postgre as well.
But the more compelling reason was the vast quantity of MySQL-only features. (Actually the delay was more compelling, but this incompatibility issue is a more noble-sounding justification.) Not just the quantity of unique features but their astonishing vitality (e.g. string comparison). Hardly any real world SQL application can avoid breaking with standards.
I think it's more accurate to say "the effort to standardize SQL has been going on for 20 years" rather than it was accomplished twenty years ago. And I don't think it will feel accomplished for many years hence.
I think there are many reasons for this long hard road, but one is that the cost/benefit of standards for SQL is unusually skewed. Getting a practical database application to work well is monumentally complex (so the benefits of advanced and intricate ad-hoc features are high). A lame database, unlike a lame rounded corner, can lose customer work and destroy goodwill (so the cost of diligent standardization can be high).
Furthermore, SQL development is rarely concerned with more than one engine at a time. Stored procedures, and other features supporting reusable code, are going through a tortured adolescence (so the benefits of portability are still low). Finally (for reasons related to the preceding, impacting industry maturity), every dialect today has a thriving single company or community in stewardship (so the costs of flaming individuality are low).
So as far as a cheatsheet, I don't think a universal SQL cheatsheet would be as valuable as one that presented all the powers of the specific SQL for the task at hand. MySQL came first because the most people asked for it. Especially passionately I might add.
Actually I don't recommend using this reference when developing Postgre SQL. The SQL implementations are just too different, and it would be more frustrating than empowering. I worked on this MySQL reference (and the underpinnings) on and off for two years. I'd love to do one for Postgre but at the moment the hue and cry is louder for a PHP reference.
I believe there's a very confusing error in the captions for tables 4 and 5 in the article, indicating rank. The captions say "higher is better" but it should be "lower is better". 1=best (green), 10=worst (red). Tables 6 and 7 do not say, but use the same numbers and colors, and lower is better there also. The article could have been more comprehensible if all the tables had indicated what's good and what's bad (tables 6-12 do not), not to mention done so accurately.
Somewhat obliquely related, I agree with frank249, that 14 days is not a statistically significant sample. How about a year.
Irony: a gorgeous inaccurate article about gorgeous inaccurate weather sites.
So one should also stop using metalic spoons during a thunderstorm, right? Wouldn't that increase the risk of being struck by lightning too? And one should not use cell phones on a public train because it increases the likelihood that, if the train were to crash, the cell phone could be rammed into one's yammering skull. Oh wait nevermind.
I remember designing with the PC/104 bus how naturally cube-shaped the results were. It was a serious limitation with packaging and mounting because no single dimension could be less than four inches. (E.g. some large flat areas were available but unusable.) Odd that a satellite might be the worlds most ideal packaging for PC/104 applications.
You know, I've been thinking about that, Mr. Smart...Guy.:-x:-D It will be hard fitting them with only 16 squares across, plus it's hard to get a triangle thing going, but maybe I can do something. The colors fit into shading series and there are 5,4,4,3,3,2,2,1,1 in each row. So in 15x9 I can fit four trinagles, kinda back-to-back, with black in between. That means the thing would have about 99 rows to fit the 42 hues.
Are you sure that would be useful? Having to scroll through all the hues? It would be hard to tell looking at the screen and the KiloChart which mapped to which, you know. (Unlike the VisoBone2 swatches in Photoshop matching the web-safe Color Chart for example, which map exactly.)
Thanks for your vote for a hexadecimal poster, Fuzzy, you're not the only one. I am hoping perhaps one day I can make a pair of Color KiloFoldouts, one in decimal and one in hex. Would you prefer a wall poster or a foldable reference?
Very clear point, Fuzzy One. I used the scandalous font tag only as the "before" portion of the example. Figure that makes it helpful to anyone using hex, whether in HTML or CSS. So I gather you agree that in every syntax that is not deprecated, it's possible to use decimal. The only syntaxes where someone is locked into hex have been deprecated.
The chart has only one type of code in order to fit a thousand colors on it. I chose decimal because more software accommodates it. There is no case I can think of where software accepts hex codes but not decimal, can you? With PhotoShop and ImageReady for example, the decimal windows are only a double-click away if I'm not mistaken.
Does that make sense and answer your implicit questions?
Nope, can't begin to pretend to imagine to solve the diversity-of-displays problem. But I can offer you a screen-color-matching system far superior to Hexachrome. In fact, that's not saying much. Although Hexachrome is what Pantone used in their ColorWeb product, it was certainly never designed to improve Web color matching (better skin tones and Irish-vivid foliage was its primary goals). It essentially adds vivid orange and green which are no help at all for the screen color furthest outside the CMYK gamut: electric blue. My eight-color system on the other hand was specifically designed to match computer screen color and does have a pretty darn decent electric blue (to wax technical). It doesn't compare to screen blue, you're very right. The physics can't support it. But I think if you can get a look you'll be at least a little surprised how good a job it does in the *relative* basis you speak of. That is, taking advantage of the eye-brain's ability to compensate for the ambient.
Slashdot Mirror
Where? I want to download Zootopia. All I could find were x-rated parodies.
It'll be something dumb like this that sets of the big sell-off and crypto-crash.
douse the R's in the same shit they gave hillary. DROWN them in it. let them realize that any weapon you use, the other side will use, when its THEIR turn.
Nope. That's the same kind of thinking that gave rise to Fox News. Left-bias in mainstream media? We'll show them some biased reporting. Escalation ensues. Retaliation doesn't teach anything you intend it to teach.
Now parody and satire, they may be good for something. They may actually raise awareness if done skillfully. But responding in mindless kind just loses eyes and teeth.
...some wag posts a sign somewhere: SPEED LIMIT -670,616,630 and then we're all screwed.
The real Bechdel test for porn would portray a woman intimate with another woman, in a way that would actually turn on another woman. I'm too busy to research it now but I suspect most porn would fail this test.
Sure, that looks almost fixed. Kind of in the way PayPal is almost e-money.
What would really answer the question, especially after this "got sloppy" speech, would be a statistically significant blip in the purging of hackers in North Korea, versus the level of giggling from hackers in Russia.
It's fashionable to cite the Dunning-Kruger effect as evidence of human dark natures: overconfidence, insecurity, or the foolish tendency of the masses to overvalue bravado. But what of the advantages?
If the optimal knowledge and skill to make a decision is not the same as maximal knowledge and skill, then there's a backside to the advantage curve. More than diminishing returns, competence beyond a certain point may hinder and hobble decision making. Mental resources are finite. There may be such a thing as knowing too much.
Maybe there's a mental organ that tries to guess when we've learned enough and it's time to act. In fine-tuning any sensibility, it's the misfiring that gains undue attention. Certainly the headlines of any age are rich with examples of right action flummoxed by call for more study. To the extent that a company or a family or a nation needs a leader at all, is the best party always the smartest duck in the room? To the extent not, the sliver of human nature that recognizes this could be branded Dunning-Kruger and yet may have deep worth.
The most effective team may have the first-rate thinkers second in command.
I think they should get more funding to put a great big running wheel on a busy Manhattan street corner.
... wait for it ...
Flash mob flashing on flash with flash.
Web-coding?! Hey I'll be glad to donate a set of my cheatsheets. Never more proud to point out the pages have ... ROUNDED CORNERS.
I'm skeptical that environmental damage is really the primary export here. And that it's the only sinister one. My local landfill (Brunswick, Maine, US) charges for almost every kind of trash except e-trash, which they accept for free, off to the side in a special warehouse. I speculate someone, somewhere must be paying them for it. Picture some scrappy, third-world geek lord of the junkyard, who frankensteins together usable stuff. Now I'd love to hear his story. It's not just motherboards and memory chips and material tangibles he has to work with is it? There must be the occasional windfall from unerased hard drives.
Want to live A LOT longer? Get rich enough to have a second wife, and then don't.
You're the first to find that easter egg. One of the more harder hidden.
I can tell you it sure feels great on this end.
You know I really intended to make a comprehensive SQL reference from the start, covering MySQL, Microsoft, Oracle and possibly Postgre. And I stubbornly held onto that goal for 80% of the project. But I gave it up for two reasons. For one, researching MySQL took so long, I knew the release would delay another year if I researched Microsoft, Oracle and Postgre as well.
But the more compelling reason was the vast quantity of MySQL-only features. (Actually the delay was more compelling, but this incompatibility issue is a more noble-sounding justification.) Not just the quantity of unique features but their astonishing vitality (e.g. string comparison). Hardly any real world SQL application can avoid breaking with standards.
I think it's more accurate to say "the effort to standardize SQL has been going on for 20 years" rather than it was accomplished twenty years ago. And I don't think it will feel accomplished for many years hence.
I think there are many reasons for this long hard road, but one is that the cost/benefit of standards for SQL is unusually skewed. Getting a practical database application to work well is monumentally complex (so the benefits of advanced and intricate ad-hoc features are high). A lame database, unlike a lame rounded corner, can lose customer work and destroy goodwill (so the cost of diligent standardization can be high).
Furthermore, SQL development is rarely concerned with more than one engine at a time. Stored procedures, and other features supporting reusable code, are going through a tortured adolescence (so the benefits of portability are still low). Finally (for reasons related to the preceding, impacting industry maturity), every dialect today has a thriving single company or community in stewardship (so the costs of flaming individuality are low).
So as far as a cheatsheet, I don't think a universal SQL cheatsheet would be as valuable as one that presented all the powers of the specific SQL for the task at hand. MySQL came first because the most people asked for it. Especially passionately I might add.
Actually you did already buy it. Sorry, the CC payment is not dead, just creaking a bit. All fixed, we'll ship your chart tomorrow.
Actually I don't recommend using this reference when developing Postgre SQL. The SQL implementations are just too different, and it would be more frustrating than empowering. I worked on this MySQL reference (and the underpinnings) on and off for two years. I'd love to do one for Postgre but at the moment the hue and cry is louder for a PHP reference.
I believe there's a very confusing error in the captions for tables 4 and 5 in the article, indicating rank. The captions say "higher is better" but it should be "lower is better". 1=best (green), 10=worst (red). Tables 6 and 7 do not say, but use the same numbers and colors, and lower is better there also. The article could have been more comprehensible if all the tables had indicated what's good and what's bad (tables 6-12 do not), not to mention done so accurately.
Somewhat obliquely related, I agree with frank249, that 14 days is not a statistically significant sample. How about a year.
Irony: a gorgeous inaccurate article about gorgeous inaccurate weather sites.
So one should also stop using metalic spoons during a thunderstorm, right? Wouldn't that increase the risk of being struck by lightning too? And one should not use cell phones on a public train because it increases the likelihood that, if the train were to crash, the cell phone could be rammed into one's yammering skull. Oh wait nevermind.
I remember designing with the PC/104 bus how naturally cube-shaped the results were. It was a serious limitation with packaging and mounting because no single dimension could be less than four inches. (E.g. some large flat areas were available but unusable.) Odd that a satellite might be the worlds most ideal packaging for PC/104 applications.
Are you sure that would be useful? Having to scroll through all the hues? It would be hard to tell looking at the screen and the KiloChart which mapped to which, you know. (Unlike the VisoBone2 swatches in Photoshop matching the web-safe Color Chart for example, which map exactly.)
-- Bob Stein, VisiBone, stein@visibone.com
Thanks for your vote for a hexadecimal poster, Fuzzy, you're not the only one. I am hoping perhaps one day I can make a pair of Color KiloFoldouts, one in decimal and one in hex. Would you prefer a wall poster or a foldable reference?
The chart has only one type of code in order to fit a thousand colors on it. I chose decimal because more software accommodates it. There is no case I can think of where software accepts hex codes but not decimal, can you? With PhotoShop and ImageReady for example, the decimal windows are only a double-click away if I'm not mistaken.
Does that make sense and answer your implicit questions?
-- Bob Stein, VisiBone, stein@visibone.com
-- Bob Stein, VisiBone, stein@visibone.com