Whether or not an expression is an insult has everything to do with the speaker's intent. "homo" clearly was an insult, as the speaker's tone suggests, unless he was making a joke.
If you want to harass someone, get to the root cause: the politicians who created the TSA and who approve, even demand, its invasive practices. Blaming the TSA employee for the abusive system is like blaming a hospital orderly for the high costs of health care.
I think you need to back up just a bit further, to the voters.
So, what does it say when the Google CEO who reportedly tied all Googlers' bonuses to social networking apparently finds it too dangerous to permit the head of Google+ to participate in social networking?
What it says is that corporate officers need to be measured in all of their communications, much more so than most other persons. Twitter, in contrast, seems to tempt its users to make spontaneous postings.
It's not inconsistent for Google to say that Google+ is a good service for many, but not all, persons.
"But the relative complexity of the installation process, including lack of closed-source drivers, reminded me of the rough edges that Ubuntu smooths over."
Ubuntu: Ancient African word for "Can't install Debian".
There's a big difference between "can't" and "don't feel like taking the time to when another option exists". Some of us have a lot of things to get done, and that puts a premium on our time. As long as the downsides to using Mint (vs. Debian) don't outweigh the benefits of a simple and quick installation, I'm going with Mint.
Actually, my discontent with recent Ubuntu releases has driven me not to Debian, but to Mint.
When I was recently frustrated with Ubuntu, I did attempt OSS purity by installing Debian. But the relative complexity of the installation process, including lack of closed-source drivers, reminded me of the rough edges that Ubuntu smooths over.
Fortunately, Mint smooths over what I consider to be the rough edges that Ubuntu introduces.
I think that was the point made in this story. Microsoft has worked hard over the years to make its systems not interoperable with others', so that customers had to buy the whole collection of enterprise services from just them.
Now that their products are apparently a worse deal in some cases than competing products from other vendors and/or open source software, their all-or-nothing strategy is at risk of backfiring spectacularly.
The tragedy, if one can call it that when Microsoft is suffering, is that this appears to be almost a play-for-play repeat of IBM's mistakes in the 1980's and 1990's, if I recall correctly. Microsoft should have seen this coming miles and miles away.
Knid of both. In the early 2000's I was a pretty intensively developing and tuning databases in MS SQL Server. Then in my master's work I worked on the design and guts of a non-relational database, which eventually became StreamBase.
Although I haven't yet worked on the guts of a relational database, I think I probably have enough database knowledge and programming skills to become a useful contributor to an OSS database project within a reasonable time frame.
It's kind of a combination of all those things. My situation is:
I've been wanting to contribute on an OSS project for a while, but haven't had the time. That should change once I'm done with grad school this spring.
I'm an experienced C++ developer (~ 18 years). I haven't worked on the internals of an OSS database yet, but (non-relational) databases were the focus of my Master's degree work. I also did MS SQL Server database design and optimization for a few years, so I'm not totally clueless.
I need to have good job prospects in western Europe in a few years, so however I spend me out-of-work time until then, I need it to help towards that.
I'm probably looking at living in a semi-rural area, where the only city within a reasonable daily commute isn't huge. So there's not likely to be a really hopping software scene near where I live. This means that I probably need to focus on databases which are very commonly used. I think this means MySQL of PostgreSQL.
I guess another alternative is that I work on whichever database project is most interesting without regard to geographically limited job-finding requirements, and hope I can telecommute. But that seems like a risky assumption.
For most of the games to which I've pledged, it's been to encourage the development of Linux games. I'm trying to do my small part to stimulate that market, even if it's a bit of a long shot.
For Defense Grid Containment, I figured it was likely to succeed, I love the game, and one of their tiers (not achieved) was Linux support. So it was a no-brainer.
Actually, I started looking at it when people mentioned it in this conversation.
After skimming their website, I'm still a bit sketchy on why MariaDB exists. It sounds like a fork, except that they seem to periodically re-sync with Oracle's MySQL releases. Is the idea to just keep on developing open-source versions of whichever features Oracle adds to MySQL?
Though I have to say I dislike the "let's go 'contribute' so I can fill up the old resume and get laid^Wa job"
That's not precisely where I'm coming from. It's more that I only have enough free time to contribute to one OSS project. But I also need to position myself for getting database work in Europe. I'm trying to find some OSS DB project that resides in a happy intersection of those two goals.
The problems with MySQL aren't bugs, they're decisions. Decisions that can't be reversed for the sake of backwards compatibility.
Agreed. Or at least, that was my impression. That's what led me to assume that my sensibilities would be seriously mismatched with whichever person(s) decide the design of MySQL.
According to my design and development sensibilities, a lot of things in that video would have been high-priority bugs. The fact that they're still present in whichever, I assume recent, version of MySQL was shown in that video, suggests to me that the leaders of that project have a different definition of "bug" than I do.
Slashdot Mirror
Whether or not an expression is an insult has everything to do with the speaker's intent. "homo" clearly was an insult, as the speaker's tone suggests, unless he was making a joke.
If you want to harass someone, get to the root cause: the politicians who created the TSA and who approve, even demand, its invasive practices. Blaming the TSA employee for the abusive system is like blaming a hospital orderly for the high costs of health care.
I think you need to back up just a bit further, to the voters.
I find it hard to learn dense material (specific kinds of math, etc.) unless I care about the problem that needs to be solved.
So how about trying to find (or start) some project which develops an app you'd like to use?
Actually, my impression is that people with DUI's just get used to being convicted of DUI's.
What it says is that corporate officers need to be measured in all of their communications, much more so than most other persons. Twitter, in contrast, seems to tempt its users to make spontaneous postings.
It's not inconsistent for Google to say that Google+ is a good service for many, but not all, persons.
If it turns out that the AIDS virus took 50 years off of the timeline to finding a cure for cancer, I wonder if the AIDS epidemic was worth it.
"But the relative complexity of the installation process, including lack of closed-source drivers, reminded me of the rough edges that Ubuntu smooths over."
Ubuntu: Ancient African word for "Can't install Debian".
There's a big difference between "can't" and "don't feel like taking the time to when another option exists". Some of us have a lot of things to get done, and that puts a premium on our time. As long as the downsides to using Mint (vs. Debian) don't outweigh the benefits of a simple and quick installation, I'm going with Mint.
You have issues with some aspects of Ubuntu, so you use Mint which simply parasitizes off of Ubuntu.
Well yeah, but why shouldn't I?
Actually, my discontent with recent Ubuntu releases has driven me not to Debian, but to Mint.
When I was recently frustrated with Ubuntu, I did attempt OSS purity by installing Debian. But the relative complexity of the installation process, including lack of closed-source drivers, reminded me of the rough edges that Ubuntu smooths over.
Fortunately, Mint smooths over what I consider to be the rough edges that Ubuntu introduces.
Like I'm going to ever watch another Cameron movie that tries to explain human origins.
Let me know when they build a full-scale replica of the TARDIS.
Which side?
I see what you did there, you classy fella'.
I think that was the point made in this story. Microsoft has worked hard over the years to make its systems not interoperable with others', so that customers had to buy the whole collection of enterprise services from just them.
Now that their products are apparently a worse deal in some cases than competing products from other vendors and/or open source software, their all-or-nothing strategy is at risk of backfiring spectacularly.
The tragedy, if one can call it that when Microsoft is suffering, is that this appears to be almost a play-for-play repeat of IBM's mistakes in the 1980's and 1990's, if I recall correctly. Microsoft should have seen this coming miles and miles away.
Well, at least when W. was the President of the U.S., the Justice Department was their friend.
Not sure what that means now that Obama / Holder are running things.
Actually, given the way things are going, I'm quite content with him staying.
You should be gentle with the poster. His view is a phase.
Inventions are almost always the result of collaboration. When hundreds of thousands of peers around the planet.
Knid of both. In the early 2000's I was a pretty intensively developing and tuning databases in MS SQL Server. Then in my master's work I worked on the design and guts of a non-relational database, which eventually became StreamBase.
Although I haven't yet worked on the guts of a relational database, I think I probably have enough database knowledge and programming skills to become a useful contributor to an OSS database project within a reasonable time frame.
It's kind of a combination of all those things. My situation is:
I guess another alternative is that I work on whichever database project is most interesting without regard to geographically limited job-finding requirements, and hope I can telecommute. But that seems like a risky assumption.
Thanks, I'll have a look. What about those issues raised in the video I linked to - the issues which I'd call correctness issues.
Has anything / will anything be done about that behaviors, or are they now permanent fixtures in the software?
For most of the games to which I've pledged, it's been to encourage the development of Linux games. I'm trying to do my small part to stimulate that market, even if it's a bit of a long shot.
For Defense Grid Containment, I figured it was likely to succeed, I love the game, and one of their tiers (not achieved) was Linux support. So it was a no-brainer.
Actually, I started looking at it when people mentioned it in this conversation.
After skimming their website, I'm still a bit sketchy on why MariaDB exists. It sounds like a fork, except that they seem to periodically re-sync with Oracle's MySQL releases. Is the idea to just keep on developing open-source versions of whichever features Oracle adds to MySQL?
That's not precisely where I'm coming from. It's more that I only have enough free time to contribute to one OSS project. But I also need to position myself for getting database work in Europe. I'm trying to find some OSS DB project that resides in a happy intersection of those two goals.
The problems with MySQL aren't bugs, they're decisions. Decisions that can't be reversed for the sake of backwards compatibility.
Agreed. Or at least, that was my impression. That's what led me to assume that my sensibilities would be seriously mismatched with whichever person(s) decide the design of MySQL.
According to my design and development sensibilities, a lot of things in that video would have been high-priority bugs. The fact that they're still present in whichever, I assume recent, version of MySQL was shown in that video, suggests to me that the leaders of that project have a different definition of "bug" than I do.
I didn't mean it as a troll, but thanks very much for pointing out that some of the video's issues are fixed in MySQL 5.x.