And even more irrelevant, nobody noticed the significance of the discovery until Columbus came back talking about all the gold he found. That's why we remember Columbus. Not because he found the place, but because he gave people a reason to remember that it's there.
I suppose the trains run on time, too.
As someone who runs a school district whose lunch time cash registers use wireless to communicate with the central server (against IT's express and repeated objections), you can take my 5 GHz bandwidth when you claw it from my cold, dead hands.
800 students all with smart phones and iPads connecting to the wireless network mean the 2.4 GHz spectrum is, at best, rather crowded. It's not uncommon to see 70 or 80 devices associated with a given AP during lunch. Combine that with the fact that half dozen the 1980s era industrial microwaves the cafeterias have sport shielding somewhat less effective than a wet paper sack and you can begin to understand the problem. Add to it register software that is so antiquated that it doesn't understand DNS (it was originally written for OS/2!) and communicates with sockets, FTP, file shares, and HTTP (yes, this is a single register application) and is significantly more susceptible to network traffic interruptions than VNC (which, of course, the vendor uses for end point support) and you have a nice little nightmare that I make every effort to ignore.
Well, clearly the answer is to hurl vague insults instead of looking for a solution.
When httpd runs a CGI script, it passes data to the script with bash environment variables. That means the code would be executed by httpd in whatever context it runs CGI scripts. The CGI script itself hasn't even been executed yet.
While that's true, it's still not a simple issue. If you look at the whole it looks like a big, pervasive problem, but having worked in several jobs in financial positions I can tell you that none of them used gender as criteria for salary. If you were in position X, you made $Y regardless of your gender. So it's largely not the case that men make more than women who are equally qualified and employed.
So what's going on?
First, many women stop work to have children. This interrupts their career progress, resets their salary, and prevents them from ascending as high as men. This is the reason that women who stop work to raise children and later divorce still get alimony. There is also a perception that women will do this, of course, and that is a problem.
Second, the careers that men choose tend to pay more. A carpenter, an electrician, a plumber, an engineer, a doctor, a tool and die machinist, a computer programmer or administrator, etc. The careers that women choose tend to pay less. A teacher, an administrative assistant, a nurse, a librarian, medical data entry, child care. Now the reason for this is actually pretty complicated. Professions that men worked were paid a salary to support an entire family wife and kids. That amount of money was simply what a man cost, since any job he took necessarily had to support his family due to cultural standards of the day. If he wasn't getting paid that amount, then he could neither support his existing family, nor could he marry a woman and start a family. Professions that women worked were paid a salary to support a single person or possibly a single person with one child. Today, those salaries remain affected by those historic amounts due to market forces. That's why professional jobs designed to attract men have reasonably good salaries even if they largely didn't exist when the workplace was divided on gender lines (i.e., computer programmers).
The key to take away here is: women and men are voluntarily choosing their own professions and we still see a salary discrepancy. The professions they choose have salaries determined by market forces, which includes how people were paid in the past. Programs exist which encourage women to take college paths that lead to better paying careers, but in spite of the fact that women now consistently and significantly outnumber men in annual college enrollment numbers, men still outnumber women in technical and professional degrees and women are still not choosing degrees which result in better paying careers.
So who is to blame? On the one hand you have people saying that women don't make as much and that's a problem for society as a whole. Women are also not taken as authoritatively as men are, so men tend to get hired into positions of higher authority which, of course, pay more. On the other, you have people saying that women made voluntary choices that resulted in them earning less so they should bear the responsibility for the consequences of their own choices rather than expecting society to fix it for them.
Fundamentally, none these problems can be easily solved through government policy or regulation. Are we expecting the government to step in an force salaries for jobs to be increased or decreased? That you have to pay a teacher and an engineer the same? That's not equality. That's parity. Are we going to say that the woman who worked 5 years, quit 10 to raise kids, and then returns deserves the same salary and opportunities as a man who has worked for 15 years? How is that fair to devalue 10 years of relevant experience? What about the increasingly common situation where the man quits his job to raise the kids? Does he deserve the same considerations?
Acute homeostatic deficiency disorder.
As opposed to if they had achieved independence, and an entirely new crop of politicians would renege on completely new promises while lining their own pockets.
Small governments are no panacea for corruption and lies. Indeed, evidence show quite the opposite is true.
Either this is a technology failure, or HP has been trying very hard to ensure that nobody could possibly find their documentation.
Well, HP is a Fortune 500 company, so it's probably both.
Why fail merely through incompetence or ineptness when you can do both? You can legitimately classify every minor bug as WONTFIX - As Designed, and every major bug can be fixed as a design error in the next version of your hardware that costs 10% more. Obsolescence through incompetence is the major business model of the modern world.
With Kickstarter, you're expected to produce what you get funded to do. Usually, what the backers get in return is a copy of the game, and little else. If the game sucks or doesn't sell, the backers are shit out of luck and the founders get a lot of bad press. That's about it.
Before Kickstarter, you had to seek out investors or venture capitalists. You know what they want in return? A monetary share of the profits with a value somewhat greater than their investment. You drop the ball and you end up in court. They want to see your account books. They want the source code and any assets you produced.
Guess what? Kickstarter's fad phase is over. Now you have to show your work. Too many projects didn't deliver, or didn't deliver on enough. Too many assholes have poisoned the well and people are going to be wary about drinking. I suspect Steam's Greenlight will do the same thing. Too many games get released as "early alpha" and then the devs get the money and stop development or development slows to a crawl. Greenlight now feels like "buy a prototype" and Kickstarter feels like "fund a pipe dream." People don't want dreams and prototypes. They want fully fleshed out games!
If your car has an interlock installed, any driver would need to use it to start the vehicle.
It's not meant to be convenient. That it's onerous is entirely intentional. It's meant to punish you by forcibly preventing illegal behavior. It provides an alternative between a fine and a suspended license. That's all. Interlocks aren't installed for first time offenders. It's likely this will be the same. Don't like it? Stop risking other peoples lives.
Which makes them not particularly different than Canonical. Or IBM. Or Microsoft, for that matter.
And what happens to the next guy? What happens when there isn't any truly indispensable software left? You just stop making new games?
1. POSIX environments have already been done on Windows, and they universally suck. SFU/Interix is shit. Cygwin is shit. MKS Toolkit is shit. MinGW/MSYS, which does a better job than any of them, is mostly shit. Even UnxUtils, which is just binaries modified for use with the actual Windows cmd shell are mostly shit. There are so many fundamental differences of philosophy that make working with a Windows system as though it were a POSIX system fundamentally untenable. You're stuck with mostly just munging text files in a binary world.
2. Powershell is what
Powershell is about 90% of what an administrator actually wants in a shell, and it's actually not that bad. Compared to cmd.exe or VBscript it's balls out fantastic. However, an administrator shouldn't need to learn about
Honestly I really love Powershell, but I wish the philosophy were geared more around getting shit done than getting shit done with
"February 2, 2009"? Wow, I didn't imagine it. The 90s did last forever.