I have absolutly no amount of expertise in this, but I would guess that the yellow pigments are chosen because yellow is a color of warning. Maybe it also suffers from less photodegradation as well? A combination of the two possibly makes yellow the ideal choice. I dunno, but either way I'm guess it has something to do with how yellow pigments react to light.
From our perspective, we (humans) chose yellow as a color of warning because there were lots of nasty critters with yellow/red on them that killed us. Well, technically, that killed other people while we (as a species) watched, since the dead make very few social color recommendations.
Ctrl+Break = break out of a console program or script (interrupt signal).
Pause = Stop the initial BIOS startup text from disappearing from view before I've had a chance to read it.
...
You have to be kidding, right? How often do you have to STOP THE BIOS STARTUP TEXT (note: all caps accomplished through the cunning use of the SHIFT key) that you need a dedicated key for this? By definition its no more than once per boot cycle. And since this is a new piece of hardware with a new OS, presumably there'd be another way to accomplish this, no?
To generate an interrupt signal, most shells use CTRL-C anyway. Your other comments are equally either unlikely or very, very niche-oriented (KVM switch? Whatever, this is a laptop keyboard! How many laptop keyboards go through a KVM before seeing their server). If you can't see that...
In a business someone once told me to look at how far away you were from the money. Are you making decisions by selling something or buying something? You're probably "level 1" in that organization. Providing support to that person? Working with them to determine what to sell next, perhaps? Level two. Engineering the design of that item? Level three. Building bits that go into it? Level four.
In many cases you may be wonderful, but you're not business-critical. There's a difference. And most people aren't business-critical,
...but 100% predictable and almost maintenance free like SVN...
SVN is neither.
Ooh, tres trendy. In reality, SVN has powered a staggeringly large number of software projects, as did CVS before it. In the same way that 'ant' (or heck, even 'make') remains remarkably effective for many projects. When you look at 10-500 dev years in a project, your source code control and build maintenance costs can often be in the 10-20 hour range (over the project lifetime). Try that with ClearCase and its brethren. And yes, I've worked on several projects in the 3-10 million LOC range that did just fine with 'make'. Decent templates make almost anything just work - if you have a dedicated 'build expert' or 'sccs maintainer', or those hours/dollars actually show up as something other than noise, then you're doing it wrong.
The reality is that most software projects aren't dramatically unique. They really aren't. Reinventing the wheel is almost always silly, using the 'old' boring solution almost always works and lets you concentrate on the actual innovative software you're designing, rather than having a great innovative code control / translation layer / build system and software that never quite gets shipped.
It would actually be interesting if you could cast your one vote for (+1) or against (-1) any candidate. That would allow a candidate who a small number of people preferred but nobody really disliked to prevail rather than just the "other" candidate - if you want to "throw the bum out," you vote against them rather than for their opponent. Far simpler a change than many suggestions.
ClearCase identified and solved all these problems in the commercial world long before Free software. The problem is that the sort of people who do kernel work don't work for the sort of companies that can afford the ClearCase licensing fees - or at least *mostly* don't.
Well, I'll go with that if you expand the definition to include those who's companies went with ClearCase and who learned first hand how much of a royal PITA it is.
It remains that for many smaller organizations (or teams), something boring but 100% predictable and almost maintenance free like SVN gets the job done just fine. But its not sexy/expensive...
Watching the 5.56 impact on the cinderblock without effect while the 7.62x39 goes clean though is all the evidence I need to make an effective decision.
Don't forget weighing the guns and ammo too, knowing that you may have to be carrying both for a few of days with no opportunity to resupply...
Yes, but they've been charging government mandated fees (totaling in the billions, literally) to deliver on that promise. We've already paid them for it, as an involuntary tax on services provided. So they should indeed deliver to you. They work around it be defining "broadband" as some tiny number like anything over 33kbps (don't recall exactly, anyone can google for the details).
If you assume that the average vessel pollutes 1/10 as much as the largest, dirtiest container ship, ass TFA does, then you've made one hell of an assumption.
Not that it's not a problem, but - really - saying that 10 small coastal vessels equals one massive container ship undermines what sounded like a reasonable point and makes me question everything about their maths. And I'm generally in agreement with them!
And to those of you here who claim "half a brain": please remember that you yourselves may someday need to do something (legal, financial, educational, even technical) for which you are less than half competent. Yes, you have achieved a "win" in humilating a sincere poster, but it's the cheap victory enjoyed only by the pusillanimous.
Here's the deal. Either this person is administering a smallish number of machines, in which case he/she can simply go 'round and install certificates on all of them, or they're administering an assload of them, in which case they do indeed deserve the scorn for not being willing to do a modicum of research and choose the standard approach.
Your defense only works if they're in charge of too many machines to administer manually, but yet have no experience doing so - a situation which is highly unlikely. It might be a temporary situation due to turnover, but in that case they shouldn't be implementing a "convenience" feature like this one themselves.
If they were making that much money, why not invest in them? Most are public companies, after all.
The truth of the matter is that the average insurance company (not talking medical here, just "normal" insurance) sucks a bunch of money out of the system in terms of salaries, etc, but typically pays out as much or more money in claims as they take in in premiums. They make their profit and pay their expenses by holding "float", investing the premium money until they need to pay it back out.
From a business standpoint, you expect to pay about as much in insurance premiums as you get back in benefits - what you're "buying" is the smoothing of events - pay a bit each month instead of a lot every decade.
I wish I could text pictures or video from the highway.... I sometimes pull up next to them and take a picture with them with my phone.... Taking the picture isn't distracting to me as I drive....
Ah... so when other people do it, its dangerous and they deserve to be reported to the police. But you, on the other hand, are a safe responsible phone user. Now it all makes sense.
It could also be that the design docs were from the manufacturing process rather than the product itself. The process engineering behind a plant could easily be worth significantly more than even $100M because the plants today cost upwards of $1B to design, build, and furnish and the lifetime efficiency gains for a well engineered plant can also reach into the billions.
That, and its a lot harder to buy one of your competitors' manufacturing plants and reverse engineer it. Plus you have to pay customs getting the plant off the boat into the country... its just a big mess.
Really. Well I guess its not like in the U.S. where a sports athlete will be fined at least 20 grand for posting nothing out of the ordinary. AKA Terrel Owens, Randy Moss
There's a pretty massive difference between being fined by the State and being fined under an agreement that you signed with a private organization that's involved in paying you massive amounts of money to represent them on the playing field.
Better yet, if you think your kid has a love for science, tell him that both "coolness" and "hero worship" are antithetical to real science.
They are not, however, antithetical to real scientists, especially considering that many of the best managed to have a lot of "non-science-based" hobbies, know lots of friends, and go to some pretty wild parties. Being a scientist doesn't have to mean that you do all science all the time - in fact, that attitude won't help your budding scientist grow into a well-rounded adult, and may discourage your well-rounded kid from pursuing a lifetime of science.
Oh my god, shut up. You've clearly never had to write code to order, quickly. Yeah, just write your gui from scratch for every application.
Not really - and yes, I write code to order and have been doing so for the last, oh, 20 years or so.
Writing a poor, non-compliant product that doesn't solve the problem (which includes usability, if its a GUI), is a FAIL. If you write that poor software twice as fast, its still a FAIL.
Put it this way. If the GUI is the single most important and complex piece of your application, doesn't it deserve to be written to run correctly for the environment in which its used? And if it isn't, then why does it matter so much if you have one GUI for OSX and another one for Windows?
Besides, you may find it far faster to write a Windows GUI using nice, complete Windows tools and libraries, plus an OSX GUI using nice, complete OSX tools and libraries, than trying to write a one-size-fits-all version using nothing more than a single "multi-platform" toolset. Not using your native platform libraries (and toolkits written by others and freely (or expensively) available is the single most crippling thing you can do during software development.
Before you mention it, I am a big fan of cross-platform languages where they make sense. In my current gig we've got a lot of high-performance server side Java, for example, and there are many other great platforms out there. But when writing a highly usable GUI the usage requirements differ depending on your OS, and until a toolkit platform correctly takes that into consideration I'll stick with native apps, thanks.
Slashdot Mirror
You'd look even more like a Simpsons character. That wouldn't be good for anyone.
I dunno - might be a good warning to others.
I have absolutly no amount of expertise in this, but I would guess that the yellow pigments are chosen because yellow is a color of warning. Maybe it also suffers from less photodegradation as well? A combination of the two possibly makes yellow the ideal choice. I dunno, but either way I'm guess it has something to do with how yellow pigments react to light.
From our perspective, we (humans) chose yellow as a color of warning because there were lots of nasty critters with yellow/red on them that killed us. Well, technically, that killed other people while we (as a species) watched, since the dead make very few social color recommendations.
Yes, I do use them all.
Ctrl+Break = break out of a console program or script (interrupt signal).
Pause = Stop the initial BIOS startup text from disappearing from view before I've had a chance to read it.
You have to be kidding, right? How often do you have to STOP THE BIOS STARTUP TEXT (note: all caps accomplished through the cunning use of the SHIFT key) that you need a dedicated key for this? By definition its no more than once per boot cycle. And since this is a new piece of hardware with a new OS, presumably there'd be another way to accomplish this, no?
To generate an interrupt signal, most shells use CTRL-C anyway. Your other comments are equally either unlikely or very, very niche-oriented (KVM switch? Whatever, this is a laptop keyboard! How many laptop keyboards go through a KVM before seeing their server). If you can't see that...
Very well said.
In a business someone once told me to look at how far away you were from the money. Are you making decisions by selling something or buying something? You're probably "level 1" in that organization. Providing support to that person? Working with them to determine what to sell next, perhaps? Level two. Engineering the design of that item? Level three. Building bits that go into it? Level four.
In many cases you may be wonderful, but you're not business-critical. There's a difference. And most people aren't business-critical,
All that's needed is a good cheap design that doesn't depend on too many exotic materials.
Oh, is that all? Although the good news is that that's all we need to solve world hunger as well...
SVN is neither.
Ooh, tres trendy. In reality, SVN has powered a staggeringly large number of software projects, as did CVS before it. In the same way that 'ant' (or heck, even 'make') remains remarkably effective for many projects. When you look at 10-500 dev years in a project, your source code control and build maintenance costs can often be in the 10-20 hour range (over the project lifetime). Try that with ClearCase and its brethren. And yes, I've worked on several projects in the 3-10 million LOC range that did just fine with 'make'. Decent templates make almost anything just work - if you have a dedicated 'build expert' or 'sccs maintainer', or those hours/dollars actually show up as something other than noise, then you're doing it wrong.
The reality is that most software projects aren't dramatically unique. They really aren't. Reinventing the wheel is almost always silly, using the 'old' boring solution almost always works and lets you concentrate on the actual innovative software you're designing, rather than having a great innovative code control / translation layer / build system and software that never quite gets shipped.
Yup. That won't buy you much in the way of cutting-edge superconductive wiring.
Actually, Safari defaults to not allowing 3rd party cookies, including on the iPhone. Not sure about the others.
It would actually be interesting if you could cast your one vote for (+1) or against (-1) any candidate. That would allow a candidate who a small number of people preferred but nobody really disliked to prevail rather than just the "other" candidate - if you want to "throw the bum out," you vote against them rather than for their opponent. Far simpler a change than many suggestions.
ClearCase identified and solved all these problems in the commercial world long before Free software. The problem is that the sort of people who do kernel work don't work for the sort of companies that can afford the ClearCase licensing fees - or at least *mostly* don't.
Well, I'll go with that if you expand the definition to include those who's companies went with ClearCase and who learned first hand how much of a royal PITA it is.
It remains that for many smaller organizations (or teams), something boring but 100% predictable and almost maintenance free like SVN gets the job done just fine. But its not sexy/expensive...
Watching the 5.56 impact on the cinderblock without effect while the 7.62x39 goes clean though is all the evidence I need to make an effective decision.
Don't forget weighing the guns and ammo too, knowing that you may have to be carrying both for a few of days with no opportunity to resupply...
It wasn't a day on which nothing happened, simply the day on which the lowest quantity of interesting things[0] happened.
Sheesh.
[0] As defined by the people who actually did the work
Yes, but they've been charging government mandated fees (totaling in the billions, literally) to deliver on that promise. We've already paid them for it, as an involuntary tax on services provided. So they should indeed deliver to you. They work around it be defining "broadband" as some tiny number like anything over 33kbps (don't recall exactly, anyone can google for the details).
If you assume that the average vessel pollutes 1/10 as much as the largest, dirtiest container ship, ass TFA does, then you've made one hell of an assumption.
Not that it's not a problem, but - really - saying that 10 small coastal vessels equals one massive container ship undermines what sounded like a reasonable point and makes me question everything about their maths. And I'm generally in agreement with them!
And to those of you here who claim "half a brain": please remember that you yourselves may someday need to do something (legal, financial, educational, even technical) for which you are less than half competent. Yes, you have achieved a "win" in humilating a sincere poster, but it's the cheap victory enjoyed only by the pusillanimous.
Here's the deal. Either this person is administering a smallish number of machines, in which case he/she can simply go 'round and install certificates on all of them, or they're administering an assload of them, in which case they do indeed deserve the scorn for not being willing to do a modicum of research and choose the standard approach.
Your defense only works if they're in charge of too many machines to administer manually, but yet have no experience doing so - a situation which is highly unlikely. It might be a temporary situation due to turnover, but in that case they shouldn't be implementing a "convenience" feature like this one themselves.
Why go to the trouble? Buy a single wildcard cert from RapidSSL (they're not expensive), and install it everywhere. Just sayin'.
If they were making that much money, why not invest in them? Most are public companies, after all.
The truth of the matter is that the average insurance company (not talking medical here, just "normal" insurance) sucks a bunch of money out of the system in terms of salaries, etc, but typically pays out as much or more money in claims as they take in in premiums. They make their profit and pay their expenses by holding "float", investing the premium money until they need to pay it back out.
From a business standpoint, you expect to pay about as much in insurance premiums as you get back in benefits - what you're "buying" is the smoothing of events - pay a bit each month instead of a lot every decade.
I wish I could text pictures or video from the highway .... I sometimes pull up next to them and take a picture with them with my phone .... Taking the picture isn't distracting to me as I drive ....
Ah... so when other people do it, its dangerous and they deserve to be reported to the police. But you, on the other hand, are a safe responsible phone user. Now it all makes sense.
It better be 100% free and work with txting blocked and even if you have no sim.
If you think you need to make a 911 contact, but wouldn't if it would cost you a dime, then you don't need to make a 911 contact.
Problem solved.
It could also be that the design docs were from the manufacturing process rather than the product itself. The process engineering behind a plant could easily be worth significantly more than even $100M because the plants today cost upwards of $1B to design, build, and furnish and the lifetime efficiency gains for a well engineered plant can also reach into the billions.
That, and its a lot harder to buy one of your competitors' manufacturing plants and reverse engineer it. Plus you have to pay customs getting the plant off the boat into the country... its just a big mess.
Really. Well I guess its not like in the U.S. where a sports athlete will be fined at least 20 grand for posting nothing out of the ordinary. AKA Terrel Owens, Randy Moss
There's a pretty massive difference between being fined by the State and being fined under an agreement that you signed with a private organization that's involved in paying you massive amounts of money to represent them on the playing field.
No, that would be \. This is /. - obviously right-leaning.
They are not, however, antithetical to real scientists, especially considering that many of the best managed to have a lot of "non-science-based" hobbies, know lots of friends, and go to some pretty wild parties. Being a scientist doesn't have to mean that you do all science all the time - in fact, that attitude won't help your budding scientist grow into a well-rounded adult, and may discourage your well-rounded kid from pursuing a lifetime of science.
Just sayin'.
Yet another obXKCD...
Not really - and yes, I write code to order and have been doing so for the last, oh, 20 years or so.
Writing a poor, non-compliant product that doesn't solve the problem (which includes usability, if its a GUI), is a FAIL. If you write that poor software twice as fast, its still a FAIL.
Put it this way. If the GUI is the single most important and complex piece of your application, doesn't it deserve to be written to run correctly for the environment in which its used? And if it isn't, then why does it matter so much if you have one GUI for OSX and another one for Windows?
Besides, you may find it far faster to write a Windows GUI using nice, complete Windows tools and libraries, plus an OSX GUI using nice, complete OSX tools and libraries, than trying to write a one-size-fits-all version using nothing more than a single "multi-platform" toolset. Not using your native platform libraries (and toolkits written by others and freely (or expensively) available is the single most crippling thing you can do during software development.
Before you mention it, I am a big fan of cross-platform languages where they make sense. In my current gig we've got a lot of high-performance server side Java, for example, and there are many other great platforms out there. But when writing a highly usable GUI the usage requirements differ depending on your OS, and until a toolkit platform correctly takes that into consideration I'll stick with native apps, thanks.