With baited breath I await the first pull requests that removes offensive words like "master" and "slave". And then the incredible outage that occurs because disks don't work anymore.
Not all of us, bub. I'll be somewhere grabbing popcorn and switching systems to OpenBSD or something. The snowflakes haven't infected that project yet.
I'm looking forward to the shit-slinging on the mailinglists because someone made a comment that hurt some fee-fees. But yes. I'm of the same mind as my compilers and interpreters. They don't care. Neither do I.
Decisions, decisions.
Protect fragile ego's from entitled children and get nothing done, or state things like they are and/or come off as a jerk in the process, while getting shit fixed...
I'll take the latter.
No clue. But they could have cut out complete swaths of text just by stating "We don't care what you are, what you do, or what your opinions are. Just show us the code. If it's good, we'll take it. If it's not, we'll see what we can salvage". All this fluffy bullshit is just that. Fluffy bullshit.
Then you move the problem remotely. It would still be more efficient to run a native client over a VPN. Now you are doing a RDP session over a slow VPN in which you are doing another remote session in vSphere. They have clients for Mac OS X. Why do they leave out Linux? Or any other *nix variant for that matter? If they have any love for the community, they would port their client over, or give us very detailed protocol specs (or an API, for that matter), so we can write our own client.
That sucks. I would rather have a native client. Running a VM on your local box just to run vSphere is what I find a bit excessive. The vSphere is in.NET, it shouldn't be that hard to port that over to Mono or something...
Like others said, just go for Ubuntu. Easy to find, easy to install, and with WUBI easy to roll back from if the Ubuntu experience didn't convince her. If your mom doesn't like Unity, you can use the default gnome desktop (not gnome-shell) that it still ships with, or just avoid the issue alltogether and go for the other *buntu flavours. And yes, I hear good things about Mint too, because of the whole community driven software center they have had even before Ubuntu had it.
Slashdot Mirror
We're adding kernel contributed bios in the documentation now? Having to use a personal pronoun in a technical doc is incredibly rare.
The triplets are outliers. Statistically insignificant. Something you'd dismiss when you take a weighted average.
With baited breath I await the first pull requests that removes offensive words like "master" and "slave". And then the incredible outage that occurs because disks don't work anymore.
If I had mod points, I would upvote the crap out of this.
Not all of us, bub. I'll be somewhere grabbing popcorn and switching systems to OpenBSD or something. The snowflakes haven't infected that project yet.
I bet they assume you can do it by using a crap-ton of unicode emojis. Or something.
I'm looking forward to the shit-slinging on the mailinglists because someone made a comment that hurt some fee-fees. But yes. I'm of the same mind as my compilers and interpreters. They don't care. Neither do I.
Or, grow a skin and fix your damn code.
Decisions, decisions. Protect fragile ego's from entitled children and get nothing done, or state things like they are and/or come off as a jerk in the process, while getting shit fixed... I'll take the latter.
Both things are irrelevant. Compilers really don't care. Neither does hardware.
..or any other opinion that isn't politically correct or "hurts feewings".
We were here first. Get the hell off my lawn.
No clue. But they could have cut out complete swaths of text just by stating "We don't care what you are, what you do, or what your opinions are. Just show us the code. If it's good, we'll take it. If it's not, we'll see what we can salvage". All this fluffy bullshit is just that. Fluffy bullshit.
Patch rejected because the use of pointers is offensive. Pointing is rude, you know?
Here's a nickel. Go buy a real domain.
Then you move the problem remotely. It would still be more efficient to run a native client over a VPN. Now you are doing a RDP session over a slow VPN in which you are doing another remote session in vSphere. They have clients for Mac OS X. Why do they leave out Linux? Or any other *nix variant for that matter? If they have any love for the community, they would port their client over, or give us very detailed protocol specs (or an API, for that matter), so we can write our own client.
That sucks. I would rather have a native client. Running a VM on your local box just to run vSphere is what I find a bit excessive. The vSphere is in .NET, it shouldn't be that hard to port that over to Mono or something...
Wake me up when they have a working vSphere client for Linux.
Like others said, just go for Ubuntu. Easy to find, easy to install, and with WUBI easy to roll back from if the Ubuntu experience didn't convince her. If your mom doesn't like Unity, you can use the default gnome desktop (not gnome-shell) that it still ships with, or just avoid the issue alltogether and go for the other *buntu flavours. And yes, I hear good things about Mint too, because of the whole community driven software center they have had even before Ubuntu had it.
Seeing traffic on port 23 does not mean telnet is involved. I know some people who run their SSH daemon on that port to lessen the stupid ssh scans.
...and specifically the touch UI one for Symbian S60v5. It's PuTTy. Oh, you want an URL with that... Try http://bd.kicks-ass.net/koodaus/putty/
Hey! Don't shoot the messenger! :)
Just break something. You have 206 chances to fool the system.
That or it's the ultimate denial of service attack.
Priceless comment on that site: "At least we now know where all the bees have gone... "