I'm not sure what the term "programmer user group" means but on first reading I thought it referred to a social organization that meets monthly to hang out, have a blast, and possibly also discuss some technical stuff.
If so, then I don't think that concerns about sex jokes are in order any more than they would be at a local bar.
On the other hand, if it really refers to some monthly meeting at the workplace, then I'd agree that the concerns are valid.
In all of these discussions, the assumption is implicit that a group (whatever group is under discussion, programmers in this case) should change their behavior because others don't like it and are pushed away from the activity by it. But why? Presumably those who are there now are there because they enjoy that environment. If you change it so that someone else is more comfortable with it, then that destroys the enjoyment of those who were there to begin with. So why, exactly, is it imperative that things be as bland and unoffensive as possible? What makes the outsiders' wishes more important than those of the insiders?
Because we're not discussing a private social club here. This is a thread about possible sexual discrimination in the workplace. It's about whether a woman has equal opportunity to earn her daily bread as a programmer. I hope this helps you understand.
That was possibly intended and correct. "Gender" (masculine/feminine) is not "Sex" (male/female), although apparently recent usage has been tending more and more to erase the discrepancy.
The period under which consumers can withdraw from a sales contract is extended to 14 calendar days (compared to seven days legally prescribed by EU law today). This means that consumers can return the goods for whatever reason if they change their minds.
Extra protection for lack of information: When a seller hasn't clearly informed the customer about the withdrawal right, the return period will be extended to a year.
Consumers will also be protected and enjoy a right of withdrawal for solicited visits, such as when a trader called beforehand and pressed the consumer to agree to a visit. In addition, a distinction no longer needs to be made between solicited and unsolicited visits; circumvention of the rules will thus be prevented.
The right of withdrawal is extended to online auctions, such as eBay -- though goods bought in auctions can only be returned when bought from a professional seller.
The withdrawal period will start from the moment the consumer receives the goods, rather than at the time of conclusion of the contract, which is currently the case. The rules will apply to internet, phone and mail order sales, as well as to sales outside shops, for example on the consumer's doorstep, in the street, at a Tupperware party or during an excursion organised by the trader.
5) Better refund rights
Traders must refund consumers for the product within 14 days of the withdrawal. This includes the costs of delivery. In general, the trader will bear the risk for any damage to goods during transportation, until the consumer takes possession of the goods
He even orders bullets, instead of driving down to the damned gun shop. Seriously. There are two gun shops and a Dick's Sporting Goods on his way to work. When you need to shoot someone, you don't want to tell the rapist/murderer/robber to wait for a few days, because your bullets haven't showed up yet. And he ends up paying the same or more than he would if he bought locally.
I don't know whether to laugh, cry, or run and hide.
I was trying to suspend my disbelief while reading these articles about hooking the big fish "Sabu" until I hit a quote from a Fox News article that just about cemented that disbelief to the floor:
``He's a rockstar,'' a New York-based hacker with close ties to WikiLeaks said recently. ``All the girls, you buy them a drink, but all they want to talk about is Sabu, Sabu, Sabu.''
``And what really sucks is he really is that good.''
Sadly, I've seen software sold with half truths and bald-faced lies before. Why it hasn't led more of them into court, I will never understand.
At least in part because
(a) taking a corporation to court to enforce a contract costs more money, possibly even more than the contract breach itself and
(b) the people who understand what was promised and what was actually delivered have to be able to convice the executives in their own corporation that "equal << promised". Those who can sue on behalf of the wronged corporation often don't understand the technical issues and may even believe that their own technical staff was at fault for not adequately specifying or monitoring the contract.
If it's part of OS, why it's in/usr/local in first place? And users needing this distinction can always do a/random/custom/directory/bin and set syslinks in/usr/bin, or even set the path.
I carelessly did not order the directory names and (my view of) their intended functions respectively, but what I meant was that what's in/usr/local/bin (or/usr/local/sbin) isn't stuff that's part of the OS but rather stuff that I added. Sometimes I'll add something into/usr/local that is intended to cover over the same named command that's in/bin or/usr/bin, and have it selected preferentially via the order of directories in my path or even of the global path. That is occasionally a useful feature of having different directories for executables. While one can create a/random/custom/directory/bin to do the same thing, that's not quite as "standardized" as knowing to always look in/usr/local/{bin,sbin} for that type of stuff.
What it boils down to is that this work seems to me to be just polishing a diamond (you didn't think I'd call Fedora a turd, did you? I would not.) not solving one of the Grand Challanges that remain even for the lovely Linux OS.
Well, if you're going to be serious about this, then I'd guess that the "/bin" versus "/usr/bin" distinction might not mean much these days for a system with terabytes of disk space but maybe on small embedded systems it's valuable; e.g., a "standalone" boot using only the root filesystem. If so, then I think that maintaining the separation for all "*NIX" systems can be useful in a "I know where that is" type of way.
And for a class of commands that a typical "user" neither cares about nor would know what to do with, separating the "/bin" and "/usr/bin" from "/sbin" makes sense because one can leave "/sbin" out of the general user's path and avoid any possible confusion (remember those large multiuser systems with folks who have varying familiarity with *NIX?).
Finally, I definitely make use of "/usr/local/bin" and "/usr/local/sbin" as a very handy separation between "stuff that's part of the OS" and "stuff I put there myself". Usually via symlinks to stuff in/opt which I generally arrange via package-name directories.
Similarly for libraries ("/lib" versus "/usr/local/lib", etc.).
But really, for mindless stuff like this, I prefer to just leave a snarky comment:-)
That's too complicated and confusing.
Programs should be in "My Programs" and libraries should be in "My Other Files That I Don't Understand".
And what's with those totally incomprehensible command names like "ls", "cp", "mv", "tar"? Make them "Show Me My Files", "Make Another One of These Please", "Put it Over There", and, um, what's tape got to do with anything?
A US boycott of drugs, yes. That would be difficult to envision for the meth heads but plain ol' MJ smokers ought to be able to manage it. If only there were some way to capture their hearts and minds.
Just everybody - quit at once and don't show up. Let him man the kitchen and the rest of it all on his own. It's not going to be easy for him, you may even end up shutting him down (depending on his margins).
You are not suggesting, no, I can't believe you are recommending that workers form a collective bargaining group -- a union?
I am truly impressed with your courage to say that.
According to this Wikipedia article http://en.wikipedia.org/wiki/Anwar_al-Awlaki he was in fact tried and convicted within the Yemenite legal system for exactly the stuff he was reported to have been assasinated for doing:
Al-Awlaki was believed to be in hiding in Southeast Yemen in the last years of his life.[34] The Yemeni government began trying him in absentia in November 2010, for plotting to kill foreigners and being a member of al-Qaeda, and a Yemenite judge ordered that he be captured "dead or alive".[34][35]
The article you linked to used a misleading (and subsequently corrected) headline to further its anti-Israel propaganda agenda:
We should not have put the headline "Israel admits harvesting Palestinian organs" on a story about an admission, by the former head of the Abu Kabir forensic institute near Tel Aviv, that during the 1990s specialists at the institute harvested organs from the bodies of Israeli soldiers, Israeli citizens, Palestinians and foreign workers without getting permission from the families of the deceased (21 December, page 15). That headline did not match the article, which made clear that the organs were not taken only from Palestinians. This was a serious editing error and the headline has been changed online to reflect the text of the story written by the reporter.
Slashdot Mirror
He's wanted for bank robbery in 15 states. But with his hand covering his face, nobody will ever know he's there.
I'm not sure what the term "programmer user group" means but on first reading I thought it referred to a social organization that meets monthly to hang out, have a blast, and possibly also discuss some technical stuff.
If so, then I don't think that concerns about sex jokes are in order any more than they would be at a local bar.
On the other hand, if it really refers to some monthly meeting at the workplace, then I'd agree that the concerns are valid.
Because we're not discussing a private social club here. This is a thread about possible sexual discrimination in the workplace. It's about whether a woman has equal opportunity to earn her daily bread as a programmer. I hope this helps you understand.
That was possibly intended and correct. "Gender" (masculine/feminine) is not "Sex" (male/female), although apparently recent usage has been tending more and more to erase the discrepancy.
http://en.wikipedia.org/wiki/Gender
You must be joking, Monsieur!
http://europa.eu/rapid/pressReleasesAction.do?reference=MEMO/11/675&type=HTML
I don't know whether to laugh, cry, or run and hide.
But the malware already ran "touch -t 0101011337 ./malware.exe", so maybe you won't spot it with this.
Old school VM and MVS system programmers also had the source (in 370 assembler) available and they indeed used it.
http://www.foxnews.com/scitech/2012/03/06/exclusive-inside-lulzsec-mastermind-turns-on-his-minions/?intcmp=obinsite
Um, that should have read: "delivered << promised"
At least in part because
(a) taking a corporation to court to enforce a contract costs more money, possibly even more than the contract breach itself and
(b) the people who understand what was promised and what was actually delivered have to be able to convice the executives in their own corporation that "equal << promised". Those who can sue on behalf of the wronged corporation often don't understand the technical issues and may even believe that their own technical staff was at fault for not adequately specifying or monitoring the contract.
I carelessly did not order the directory names and (my view of) their intended functions respectively, but what I meant was that what's in /usr/local/bin (or /usr/local/sbin) isn't stuff that's part of the OS but rather stuff that I added. Sometimes I'll add something into /usr/local that is intended to cover over the same named command that's in /bin or /usr/bin, and have it selected preferentially via the order of directories in my path or even of the global path. That is occasionally a useful feature of having different directories for executables. While one can create a /random/custom/directory/bin to do the same thing, that's not quite as "standardized" as knowing to always look in /usr/local/{bin,sbin} for that type of stuff.
What it boils down to is that this work seems to me to be just polishing a diamond (you didn't think I'd call Fedora a turd, did you? I would not.) not solving one of the Grand Challanges that remain even for the lovely Linux OS.
Well, if you're going to be serious about this, then I'd guess that the "/bin" versus "/usr/bin" distinction might not mean much these days for a system with terabytes of disk space but maybe on small embedded systems it's valuable; e.g., a "standalone" boot using only the root filesystem. If so, then I think that maintaining the separation for all "*NIX" systems can be useful in a "I know where that is" type of way.
/opt which I generally arrange via package-name directories.
:-)
And for a class of commands that a typical "user" neither cares about nor would know what to do with, separating the "/bin" and "/usr/bin" from "/sbin" makes sense because one can leave "/sbin" out of the general user's path and avoid any possible confusion (remember those large multiuser systems with folks who have varying familiarity with *NIX?).
Finally, I definitely make use of "/usr/local/bin" and "/usr/local/sbin" as a very handy separation between "stuff that's part of the OS" and "stuff I put there myself". Usually via symlinks to stuff in
Similarly for libraries ("/lib" versus "/usr/local/lib", etc.).
But really, for mindless stuff like this, I prefer to just leave a snarky comment
That's too complicated and confusing. Programs should be in "My Programs" and libraries should be in "My Other Files That I Don't Understand". And what's with those totally incomprehensible command names like "ls", "cp", "mv", "tar"? Make them "Show Me My Files", "Make Another One of These Please", "Put it Over There", and, um, what's tape got to do with anything?
A US boycott of drugs, yes. That would be difficult to envision for the meth heads but plain ol' MJ smokers ought to be able to manage it. If only there were some way to capture their hearts and minds.
Or maybe this is a reverse Monty Python drag skit in the making?
http://www.washingtonpost.com/politics/rick-perry-ron-paul-have-mixed-record-on-energy-subsidies/2011/10/19/gIQA457kyL_story.html
``It's a wise man who knows his own father.'' -- Anon
I see somebody who didn't get an invitation to the tea party :-)
Oh shit, I thought it said the BofH was hacked!
Whew! Thankfully, though, that's not the case:
http://bofh.ntk.net/BOFH/
You are not suggesting, no, I can't believe you are recommending that workers form a collective bargaining group -- a union?
I am truly impressed with your courage to say that.
Stop making sense. You are interrupting the mass hysteria.
Whew! For a second there I thought you said you were "going to go off" and I flinched. You got me good.
The article you linked to used a misleading (and subsequently corrected) headline to further its anti-Israel propaganda agenda:
http://www.guardian.co.uk/theguardian/2009/dec/22/corrections-clarifications