Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:No GPL if taxpayer funded (Score 1) 277

This is the FSF's position, but some people think the requirement to preserve the BSD license text is a "further restriction" relative to GPLv2.

Even if those people are correct (one might argue that the text the BSD license says must be preserved falls under "appropriate copyright notice", or is close enough that a court would not find it a substantial breach of the GPL), explicitly dual licensing is useful to satisfy said people's paranoia, especially if you want your code merged into their project.

Of course, if we're going to start interpreting the GPL that strictly to the letter, section 2a of GPLv2 gets violated constantly...

Comment Re:Poll Tax (Score 1) 390

Do they provide transportation to and from the office where you need to apply for such an ID?

What about people that are citizens, but lack the documents required to get a state ID? Not everyone is born in a hospital, and not all parents of home births are responsible enough to file the birth certificate -- especially for older births when such things weren't as important as they are today.

Adding barriers of any sort is going to depress legitimate turnout, so it had better be stopping enough fraud to be worth it. If you suppress more legitimate votes than illegitimate, you have failed in making the vote outcome better reflect the desires of those eligible to participate.

Such suppression disproportionately affects the fringes of society -- and we know who *they* vote for, so guess which party pushes voter ID laws...

Comment Re:WTF? (Score 1) 243

I need an investor to write software? Even if I have one, I need to burn valuable startup capital patenting every little aspect of my product that someone might want to patent?

Does "first to file" only make a difference with prior inventors that did not disclose, or does it interfere with prior art that has been made public by way other than patenting?

Personally, if there are multiple independent inventors within a short period of time (disclosed or otherwise, as long as you have evidence that it happened, and was independent), I think that should invalidate the patent altogether as being an obvious progression from the current state of the art. Or at least give joint rights to the patent to everyone involved.

Comment "it died but only after a huge upset" (Score 1) 509

So, they're operating with no good guidelines in a system that makes it hard for S corporations with highly variable income to avoid burdening themselves with fixed salary costs -- and they like it that way, since they opposed the proper fix, which is to recognize that this is all ordinary income, and should be treated as such -- just as the profits of an unincorporated business would be.

Comment Re:So who then loses out when the computer goes do (Score 1) 498

What about time spent unable to work because of a restrictive IT environment? Time spent dealing with an out-of-date OS on which I cannot install newer application software that I need (no, I'm not talking about "time wasters")? Waiting for builds on slow hardware? Not being able to effectively work from home (include here the time I wasted trying, in vain, to get some sort of usable VNC setup on top of the old, IT-managed, company-owned Windows laptop that I'm allowed to VPN with, so I could get to my Linux desktop in the office? I eventually got it working, mostly, but it wasn't usable.)?

You can't treat all employees and all jobs the same.

Comment IT works for the company, not the other way around (Score 1) 498

That's just what I want, to support 30 or 40 different models, brands, or hell even architectures.

There's a difference between "let's have IT support everyone's personal equipment" and "let's not prohibit people from connecting their own computers to the network". Limit it to people considered technically competent, and feel free to reject support requests where the problem appears to not be on your end -- though don't be too quick to dismiss the idea that the problem might be on your end, particularly when dealing with developers and others who ought to have a clue.

To say nothing of when their own personal laptop that they used to surf horse porn last night brings some nasty viruses to work to test the corporate network.

If someone causes a problem due to carelessness, then maybe they lose the privilege of connecting their own stuff. But don't use the firewall as an excuse for crappy internal security.

And finally, what happens when I tell them "Sorry, you're going to need to downgrade your os/office suite/creativity suite/whatever to be compatable with the tools we've already paid thousands of dollars for and aren't going to get a new license just for your special snowflake hardware there".

Accommodating such differences is a separate question from restrictive policies, though I don't see why it's IT's business if some department wants to pay extra for a special license, or for extra IT manpower. If you're asked to pay for it out of your existing budget, that's another matter.

No thanks. I'm happy with standardized hardware.

I'm glad you're happy. Your users -- who may also be highly valued employees that the company wants to be happy -- may not be.

if you keep facebook and yahoo messenger off it (thank god for corporate virus protection that can prevent unauthorized installers/msi files), it'll run nice and quick.

"Runs nice and quick" is not something anyone would ever say about a Windows computer after IT loads their crap on it where I work. Their Linux boxes aren't slowed down quite as much, but they run old software with lots of weird local IT changes (e.g. they override the already old distribution's version of sed with an even older version. They said it was because they thought someone at some point might have depended on that old version, but they didn't seem to have a clue who or why).

We're not limited in the software we can install. We can, in some instances, wipe the OS and install whatever we want and manage it ourselves. But corporate policy prohibits us from connecting a piece of hardware not *owned* by the company to the network, not even to connect from home over the VPN, not even on a virtual machine dedicated to the task.

Seriously, a 5 year old pendium D with 2gb of ram running XP will tear the fuck out of office 2003 or 2007.

My job doesn't involve running "office 2003 or 2007". Or Windows, for that matter. It does involve compiling large codebases, with compilers that grow ever slower in their efforts to make the generated code faster. It also involves a variety of development and communication tasks that benefit from running up-to-date software.

This is work. Do work.

So, does "Fri Jan 14, '11 03:31 PM CST" translate into work hours in your time zone?

Seriously, it's not IT's job to determine the extent to which employees should be allowed to take a break, or what constitutes "work".

Slashdot Top Deals

"Gravitation cannot be held responsible for people falling in love." -- Albert Einstein

Working...