We can't compete with asian workers. They're young, well trained (if not experienced), eager beavers and they work for 10-20%, not 50-80% of our salaries.
If your company decides that your post can be handled by a guy in Bhopal - or two, or five guys- then you're boned. No argument that you make will effect the bottom line. Management view outsourcing like a cut price buffet. Sure, it might be all bone and gristle, but it's really cheap bone and gristle!
Keep your skills up to date if you like, try and move into areas that asian companies aren't strong in yet, but with two billion people in China and India coming up fast, your career is going to be a constant struggle to keep your head above water.
Sorry for the negativity, but you have to see the way these guys work before you can really grasp the scale of the problem. They pack developers in like chickens, and throw ten, twenty, fifty people at a task that we might do with a team of two or three. Even if half of them are just randomly pecking at the keyboards, the sheer volume of output that they produce is enough to convince management that they must be doing a good job.
An email is a message in a well known format composed a sequence of TCP/IP packets, usually but not always sent via a port 25 socket on an SMTP server, and usually but not always retrieved from a POP3 or IMAP server.
As the expressed intent is not to to punish recipients, the notion of taxing retrieval of emails is dismissed out of hand. Only the sending and relaying will be considered.
An SMTP server can be configured to handle email from anybody (an open relay) either deliberately or through incompetence or malice. Some SMTP server can be configured to require authorisation before handling email. Some SMTP servers are configured to only accept or send email to certain domains. Some SMTP servers are hidden (successfully or otherwise) on non-standard ports, behind firewalls, or are only accessible via (e.g.) SSH encrpyted connections. Some SMTP servers handle email only for a specific organisation, or for a specific machine.
SMTP servers are freely available for most computer platforms. Most linux distributions, for example, come with one or more SMTP servers as standard, there are several free SMTP servers avaiable for Windows, many email viruses contain their own SMTP servers to propagate themselves, or a simple SMTP server can be written in a few dozen lines of code or script.
Anyone connected to the internet anywhere in the world can set up an SMTP server and provide services to anyone they like. This may be against the acceptable use policy of their internet service provider (ISP), and their ISP may try to prevent it by technical means such as blocking the well known SMTP port 25, but there are ways to disguise the traffic or bypass these restrictions, including relaying to open SMTP servers on non standard ports and/or using SSH tunnels. Spammers can set up their own SMTP servers rather than using their ISP's servers, or can find and use open SMTP relays based anywhere in the world.
There is no practical way to oblige or enforce taxation on the administrator of an email server. Large US based ISPs could conceivably be taxed, but spammers commonly use open relays or their own SMTP servers. These can be based anywhere in the world. How will US legislation enforce taxation in Russia, for example? As a futher issue, at what level does email attract taxation? When it is being sent anywhere in the world? When it is being sent within the US? When it is sent from outside the US to servers inside the US? When it is sent within a subset of the internet, like a corporate or academic network, which can comprise tens of thousands of users? At the individual machine level?
Email is relayed across SMTP servers. In theory, it would be possible to tax the receiving SMTP servers of US based, large corporate ISPs and have them bill the sender. In practice, ISPs would be unable to collect this, and would in any case have to have accounts for every possible sender. This would lead to them either: rejecting email from the vast majority of non-US ISPs and being rejected in turn, effectively cutting the US off from the email network; or more likely, passing the costs on to the US based individual recipient either directly or indirectly.
In summary, Senator Dayton, the only practical way to keep the internet safe for Americans is to wall off part of it and declare a Fortress USA.
Any ISP who wanted to do that could do it right now. AOL could do it tomorrow. They have, for example, repeatedly experimented with rejecting email that appears to come from SMTP servers that don't appear to match the registered SMTP servers (well, their IP addresses) for the apparent sender's domain name. The reason why I repeat "apparent" is that these factors can be faked by malicious spammers, but that they catch out many legitimate senders, to the point where this policy has been unenforcable.
Thank you, Senator Dayton, for your interest in these matters, and for taking the time to suggest a superficial knee jerk solution that would wreck the internet as we know it beyond repair. I suggest that you sack whatever idiot nephew you employ as a researcher and take some actual advice on this issue before you do some real damage.
Please fuck off and die. Or better yet, go and read the DMCA, and then fuck off and die. It requires NOTHING from the service provider. It offers them an OPPORTUNITY to avoid the possibility of being liable for contributory infringement if they CHOOSE to remove the content. Find your own links and do your own reading, you lazy pussweed.
Every time an ill informed yakker like you shoots his clueless mouth off here, another lawyer gets his wings.
Did you read this part? "Under the terms of the D.M.C.A., we will have an obligation to remove such information as we become aware of it."
Bull. Fucking. Shit. Under the terms of the DMCA, they are not liable for contributory infringement if they remove it. That's all the DMCA says. There's no obligation, only an opportunity for a clueless pussweed to cover up his pants-pissing by gambling (correctly, it seems) that everybody else is as uninformed as him.
As soon as that thing comes out, I'm doing a Phantom Edit with an added scene where Saruman falls and can't get up.
It's fair enough to cut things to make it fit, but that ass monkey is adding crap in at the same time. God damn tree hugging goose stepping robo-pixies, go to hell.
He took it out because he's a fucking faggot who can't resist putting things in to get a hard on. OK, leave in the elf totty, but cut that ass bandit Faramir, for fuck's sake, nobody likes him.
Slashdot Mirror
Ahahahahahaaaaaa haaaaaaaaaaaaaa hahahahaha, ah hahahahaaa, ah haaa, ah haa, ah, ah.
OMFG, you guys are funny. You like the pain. Admit it. You live for this stuff.
We can't compete with asian workers. They're young, well trained (if not experienced), eager beavers and they work for 10-20%, not 50-80% of our salaries.
If your company decides that your post can be handled by a guy in Bhopal - or two, or five guys- then you're boned. No argument that you make will effect the bottom line. Management view outsourcing like a cut price buffet. Sure, it might be all bone and gristle, but it's really cheap bone and gristle!
Keep your skills up to date if you like, try and move into areas that asian companies aren't strong in yet, but with two billion people in China and India coming up fast, your career is going to be a constant struggle to keep your head above water.
Sorry for the negativity, but you have to see the way these guys work before you can really grasp the scale of the problem. They pack developers in like chickens, and throw ten, twenty, fifty people at a task that we might do with a team of two or three. Even if half of them are just randomly pecking at the keyboards, the sheer volume of output that they produce is enough to convince management that they must be doing a good job.
You Have Been Trolled.
You Have Lost.
Have A Nice Day.
No, wait, not lawyers, those other soulless bloodsucking freaks of nature. Vampires, that's it.
Are you working in the private sector? Then take it from me: you won't be in the lucky half.
This code, according to SCO, is already there in lunix. I've got it on multiple hard drives right now.
If Darl tells me what it is, I will happily rip it out. If he doesn't tell me, I'll continue to use and duplicate it out of ignorance.
This does not bode well for an informed judgement.
You're a lazy, incompetent assrag. Get over it.
That should cure them of any open sores and lunix urges for life.
Look, if you've got 4-7 people and a few hours to spare, you could write your own game that would be in every way superior to BZflag.
Answer: Not anybody who matters. Pointy Haired Bosses just read the big media headlines. SCO have got away with this yet again.
YHBT. YHL. HAND.
There is an unshakably high probability that all extra-terrestrial intelligence that we can currently detect is hugely more advanced than our own.
When we can detect $ADVANCED_COMMUNICATION_METHOD, but we're still looking for good old RF as well, then we can perhaps review that.
+ Five minutes to implement.
+ It will fool spammers for five minutes.
+ Your ISP will disconnect you after five minutes.
Let's chalk this one up as yet another "nice try, shame about the lack of planning".
>There's quite a bit of compiler technology in the current driver releases from nVidia and ATI
Prove that. What's that? You can't? Thought so.
Nothing. Now, what part of step 2 are you having trouble understanding?
Then they can resign. $45K starting salary rising to $90K for a 4 day week? Fuck them. Let's subcontract the whole lot to India.
>Noone wants to get involved in litigation, no matter how fun it looks from the outside
No one except a company composed almost entirely of lawyers.
An email is a message in a well known format composed a sequence of TCP/IP packets, usually but not always sent via a port 25 socket on an SMTP server, and usually but not always retrieved from a POP3 or IMAP server.
As the expressed intent is not to to punish recipients, the notion of taxing retrieval of emails is dismissed out of hand. Only the sending and relaying will be considered.
An SMTP server can be configured to handle email from anybody (an open relay) either deliberately or through incompetence or malice. Some SMTP server can be configured to require authorisation before handling email. Some SMTP servers are configured to only accept or send email to certain domains. Some SMTP servers are hidden (successfully or otherwise) on non-standard ports, behind firewalls, or are only accessible via (e.g.) SSH encrpyted connections. Some SMTP servers handle email only for a specific organisation, or for a specific machine.
SMTP servers are freely available for most computer platforms. Most linux distributions, for example, come with one or more SMTP servers as standard, there are several free SMTP servers avaiable for Windows, many email viruses contain their own SMTP servers to propagate themselves, or a simple SMTP server can be written in a few dozen lines of code or script.
Anyone connected to the internet anywhere in the world can set up an SMTP server and provide services to anyone they like. This may be against the acceptable use policy of their internet service provider (ISP), and their ISP may try to prevent it by technical means such as blocking the well known SMTP port 25, but there are ways to disguise the traffic or bypass these restrictions, including relaying to open SMTP servers on non standard ports and/or using SSH tunnels. Spammers can set up their own SMTP servers rather than using their ISP's servers, or can find and use open SMTP relays based anywhere in the world.
There is no practical way to oblige or enforce taxation on the administrator of an email server. Large US based ISPs could conceivably be taxed, but spammers commonly use open relays or their own SMTP servers. These can be based anywhere in the world. How will US legislation enforce taxation in Russia, for example? As a futher issue, at what level does email attract taxation? When it is being sent anywhere in the world? When it is being sent within the US? When it is sent from outside the US to servers inside the US? When it is sent within a subset of the internet, like a corporate or academic network, which can comprise tens of thousands of users? At the individual machine level?
Email is relayed across SMTP servers. In theory, it would be possible to tax the receiving SMTP servers of US based, large corporate ISPs and have them bill the sender. In practice, ISPs would be unable to collect this, and would in any case have to have accounts for every possible sender. This would lead to them either: rejecting email from the vast majority of non-US ISPs and being rejected in turn, effectively cutting the US off from the email network; or more likely, passing the costs on to the US based individual recipient either directly or indirectly.
In summary, Senator Dayton, the only practical way to keep the internet safe for Americans is to wall off part of it and declare a Fortress USA.
Any ISP who wanted to do that could do it right now. AOL could do it tomorrow. They have, for example, repeatedly experimented with rejecting email that appears to come from SMTP servers that don't appear to match the registered SMTP servers (well, their IP addresses) for the apparent sender's domain name. The reason why I repeat "apparent" is that these factors can be faked by malicious spammers, but that they catch out many legitimate senders, to the point where this policy has been unenforcable.
Thank you, Senator Dayton, for your interest in these matters, and for taking the time to suggest a superficial knee jerk solution that would wreck the internet as we know it beyond repair. I suggest that you sack whatever idiot nephew you employ as a researcher and take some actual advice on this issue before you do some real damage.
Oh, great argument. If it applies outwith the hours that I'm contracted to work for Apple, why shouldn't it apply after my contract ceases?
By that argument, we can't even take knowledge with us to new jobs. Is that what you really mean?
"Microsoft, however, said the problem is relatively minor and that the company hasn't had many complaints."
becomes p>"Microsoft, however, said the problem is relatively minor because the company hasn't listened to many complaints."
Please fuck off and die. Or better yet, go and read the DMCA, and then fuck off and die. It requires NOTHING from the service provider. It offers them an OPPORTUNITY to avoid the possibility of being liable for contributory infringement if they CHOOSE to remove the content. Find your own links and do your own reading, you lazy pussweed.
Every time an ill informed yakker like you shoots his clueless mouth off here, another lawyer gets his wings.
Did you read this part? "Under the terms of the D.M.C.A., we will have an obligation to remove such information as we become aware of it."
Bull. Fucking. Shit. Under the terms of the DMCA, they are not liable for contributory infringement if they remove it. That's all the DMCA says. There's no obligation, only an opportunity for a clueless pussweed to cover up his pants-pissing by gambling (correctly, it seems) that everybody else is as uninformed as him.
As soon as that thing comes out, I'm doing a Phantom Edit with an added scene where Saruman falls and can't get up. It's fair enough to cut things to make it fit, but that ass monkey is adding crap in at the same time. God damn tree hugging goose stepping robo-pixies, go to hell.
He took it out because he's a fucking faggot who can't resist putting things in to get a hard on. OK, leave in the elf totty, but cut that ass bandit Faramir, for fuck's sake, nobody likes him.
"We haven't listened to a single user who has said they're using [open source] because it's better."
Words fail me. Soon, the only way I'll be able to get content that plays on my lunix box will be through P2P.