A good biblical scholar will also recognize that, while it may be inspired by God, it was still written by men, and the men holding the pen almost certainly interpreted it to suit their current world view.
Not really - one of the basic ideas of inspiration is that the authors of scripture were not scribes, blindly copying down the words of God (well, unless you're talking about a direct quote:-) They were moved by the Spirit of God, and their own personalities, experiences, inclinations, vocabulary, mannerisms, etc. were taken into account by God and used to produce what God wanted inscrupturated.
In other words: God inspired them, and knew how to inspire them such that they would end up writing exactly what he wanted them to write. If there is any interpretation being done to fit a certain world view, it is not present because the human author inserted it - it is there because the inspiring author, God, desired and intended that particular interpretation.
God can inspire the writing and translation of the bible so that it is the true word of God..
That's where most people go wrong - the vast majority (99.9%) of Biblical theologians will tell you that it's the original writings (the autographa) that are inspired word of God, and that inspiration has nothing at all to do with translation. Those that disagree and think that translations are also inspired are so far out on the fringe that even the most conservative Christian believers consider them, um, "out there", to be polite. So revisions in a translation aren't a critical issue - you want a good translation, surely, and you want that translation to be based on accurately preserved copies of the autographa. A good Biblical scholar will recognize the problems and pitfalls present in using any translation, and base his or her study in the original languages (Greek, Hebrew, Aramaic) instead, in order to catch nuances and implications in the original languages that are lot or distorted by translation into a different language.
They can't just have an XML feed; noooo, they have to post XML-formatted articles to a usenet server, adding an extra layer of complexity.
Ha! You think that's annoying? You should have seen their file formats before they moved to XML. In the early 90's, I had to write an NT service that would listen to their news feed and properly classify incoming stories. Based on what I had to deal with there, I can only conclude that they entered their story headers by means of repeatedly striking a keyboard with a spastic orangtan.
Well, OK, it wasn't quite that bad. I would have killed to have gotten the data in a semi-reasonable format like XML, though.
I took a look at the coreutils mailing list last night, to see if there had been any discussion about this sort of thing in the past. The impression I got was that standards compliance is pretty important - I don't think that breaking the connection between -f and interactivity would be possible, unless the relevant upstream standards were changed as well. Adding a specific extension like --preserve-sanity should be doable, though.
It couldn't be made the default for rm without requiring every single sysadmin script ever to be rewritten, but I think that this is a good compromise.
My opinion is that it should be the default, period. Personal experience is that I've only once had a bad rm -rf experience from an interactive shell... but I've had buggy scripts, Makefiles, etc. come back and bite me more than once. It's real easy to forget to set a variable, or set it in most cases, or just have a typo. Consider a makefile where you end up with a "clean" target that does rm -rf $(INSTALL_ROOT)/bin, and you mistakenly do a make INTSALL_ROOT=/tmp/foo clean. Ouch.
IMHO, admin scripts that want to recursively remove directories like ~, bin, etc, and so on are probably much less common than scripts that don't intend to have that behavior. But again, the requiement to adhere to standards means that it's unlikely that --preserve-sanity or its kin would ever become part of the standard, precisely for the reson you laid out - it would change the behavior of rm and potentially break existing scripts. Never mind that it's brain-damaged behavior to begin with... sigh. Maybe a compromise could be to have rm check for an environment variable ("RM_SANITY") and change its default behavior if set... though that just feels like an ugly hack.
Here you hint at the real prolem - the '-f' switch actually means 'ignore nonexistent files, never prompt'. If combines what should otherwise be two distinct aspects of behavior, how vigorous the command is at removing files, and whether or not the command is run interactively.
Because of this combining of aspects of behavior, the only two possibilities the command offers is to always prompt the user, and never prompt the user. You have the choice of absolute paranoid safety, or performing without a net - nothing in between. How safe you want the command to be is linked directly to how interactive you want the command to be. If you want the command to be non-interactive (using -f), then you must forego safety.
Ideally, rm would support options like the following:
-f, --force
ignore nonexistent files
-i, --interactive
prompt before any removal
-n, --non-interacive
never prompt (default)
-p, --preserve-critical
fail to operate recursively on critical directories (/, ~,/bin,/lib,/etc) (default)
-x, --remove-critical
allow recursive operation on critical directories (/, ~,/bin,/lib,/etc)
Note the seperation - you can now choose how interactive the command should be seperately from how, um, vigorously it should obey your commands. So someone doing 'rm -rf ~/random-file' (note the space) with this version of rm would get a message like:
rm: it is dangerous to operate recursively on `~'
rm: use -x to override this failsafe
rm: cannot remove `/random-file': No such file or directory
Sure, you can do the same thing with the immutable attribute for ext2/3, but that still leaves you out in the cold if you're using a different type of filesystem. Likewise, you can use the '--preserve-root' argument with newer versions of rm, but you have to explictly set this option - so the default is to allow the user to delete root! Explictly requiring the user to say '--no-preserve-whatever' would be safer overall, at the cose of affecting some scripts that legitimately want to clear out '~', '/', or other such directories.
I'm sure this has been brought up elsewhere, and there are reasons why 'rm' doesn't behave this way (POSIX compliance, I'd bet.) Still, I think it would be a nice enhancement.
You will note that while companies love BSD-licensed projects (since they can just steal code from them)...
Someone who uses the BSD license isn't "stealing" code. They're using the code in a manner consistent with the license it was provided under. Since it was the original author's choice to allow them to use the code in this way (making changes without requiring them to re-distribute the source), then what they're doing isn't "stealing", in any way, shape, or form. They're abiding by the terms of the license. The fact that you don't like those license terms, or the options that it gives someone, is irrelevant.
Besides - if you want to characterize the use of BSD code, in accordance with the license, as "stealing", then you'll need to accuse several prominent open-source projects of "stealing" code as well, since they include source code licensed under new-style (no advertising clause) BSD licenses.
And here is the fallacy in your argument.
That indian tech may be getting a fraction of what YOU make per year. But, he is getting MANY TIMES as much as as the average Indian worker.
And here's the fallacy in your argument - that same difference in pay scale/cost of living means that the $350K US that they made off with was worth a whole heck of a lot more to them than it would be to you.
Would I risk something like this for 10 years' salary? Nope.
Would I risk something like this for 50 years' salary? I'd like to think no, but I've never been tempted like this...
Would I risk something like this for for more money than I could otherwise reasonably expect to earn in my lifetime? Maybe. Imagine yourself in a situation where a few minutes effort would net you $10 million of someone else's money. Can you be sure that you wouldn't consider that at all tempting?
I'm not sure where these guys ended up on that scale, but I suspect that you're still talking about enough money to live comfortably for 20-30 years. The cynical part of me says that their real problem was that they didn't steal enough. If it had been a few hundred million, then they wouldn't be thieves, just international market speculators...
Take a look at Pudge's comment about the authorship of this slashback. He started it, Timothy finished it. Complain about the the behavior of the Republicans and Democrats all you like, but the both/.'s token conservative and leading liberal poster had a hand in the article blurb.
Just liek the english words "automobile", "table", and "apple" all have definitions of what they mean, such is the case for hebrew words.
And just like English, Hebrew words - words in any language - can have contextual meanings apart from their definitions. I'm not even talking about language constructs like similies and metaphors. For example, you can reliably assume that a Roman senator was male. It's not part of the definition of the word, but a reflection of the culture of the times and the context in which the word was used. You could have made the same assertion (sentor == male) in the US until this century as well.
I have to admit that I find it ironic that I am often accused of interpreting the Bible (OT and new) too literally, and here I am being harangued by you for not being literal enough.
You keep pressing that point, but aren't even trying to back it up. The connotations of the term certainly do imply virgiinity, in the same way referring to a "little girl" in modern English would imply virginity, or using "Miss" to address a woman in Victorian England would imply that she was unmarried and, presumably, a virgin.
A 14 year old wife would definitely be an almah, but would not be a virgin (betulah.)
No, she wouldn't be almah - read up a bit more; that term was never used for a married woman. It might be used for a woman who was betrothed, but not for a woman who's marriage had been consumated. In that case, she was neither almah nor betulah
Second, we know that a group of Rabbis translated the Torah into greek, and that was the foundation of the Septuagint. History is silent on who translated the rest - it could have been rabbis, assimilated jews, non-jews, etc.
Regardless of who did the translating: the translation of almah as parthenos was accepted by Alexandrian Jews and others who made use of the Septuagint. This seems to indicate that even if almah did not, specifically, mean "virgin", there was considerable overlap between the words.
Was she a virgin? Absolutely not. That shows us that parthenos also does not mean virgin.
The meaning of the Greek word is not determined by it's usage in the Septuagint; it's determined from it's usage in the Greek language. One of the more significant meanings of parthenos is virgin - Athena's two most prominent titles were Pallas Athena and Parthenos, specifically because she was the virgin goddess.
(BTW, if you could point me at a reference to the use of parthenos w/respect to Dinah, I'd appreciate it.)
I don't know where you christians get your info from regarding the meanings of various hebrew and greek words, but it's always amusing
From Liddel-Scott's Greek-English Lexicon, among others. Take a look at the various definitions for parthenos, and it's pretty clear that it means a virgin, or by implication, an unmaried woman presumed to be a virgin.
And all this is moot anyway, since the hewbrew word there does not denote viriginity. It means "young woman", and nothing more.
It definitely implies virginity. There are only 7 references to 'almah' in the OT, and four of those uses (Gen 24:43, Ex 2:8, Song 1:3, Song 6:8) refer to a "young woman" in a way that implies sexual innocence - someone who may be sexually experienced, but is generally assumed to be virginal; as one reference puts it, "the word clearly denotes a young woman who is not married but is of marriageable age... It is important to remember that in the Bible, a young Jewish woman of marriageable age was presumed to be chaste."
It's worth noting that the Septuagint translates "almah" in Isaiah 7:16 using "parthenos"; so, at least in some sense, the Alexandria Jews who translated the OT scriptures into Greek thought that the proper translation of "almah" in this case was, indeed, "virgin".
Build a standard rack with hollow piping, and pipe cold water through the rack itself. Use it as a huge heat sink for the servers - heck, you could probably figure out a way to make a direct connection from the rack to the CPUs with a strip of copper or aluminum. At the very least, you end up with the servers at least partially in contact with a big, cold, water-cooled hunk of metal. Get additional eco-points by using the now-warmed water as input for the building's hot water heater.
I'll second this - P4 is a great SCCS. We torture it daily (125+ distinct kernel branches for various embedded systems, plus corresponding root filesystem sources), and we've had only a handful of extremely minor problems over the past three years.
If the folks over at Perforce are smart, they'll jump in and offer a free, no-strings attached agreement that would contibute a pool of perpetual P4 licenses to the Linux community that can be used for hosting Linux source trees under P4. Linus may decline the offer, but just making the offer would be great publicity and cost Perforce nothing.
For three days the world had watched while chirpsithtra executioners smothered four men slowly to death. In some nations it had even been televised. "Don't you see, we don't *do* things like that. We've got laws against cruel and unusual punishment."
"How do you deal with cruel and unusual crimes?"
I shrugged.
"Cruel and unusual crimes require cruel and unusual punishment. You humans lack a sense of proportion, Rick Schumann."
...learning to write your own, comprehensive, thought-out documentation is a very valuable skill that most don't have.
It sounds like you've never used one of these tools. There are multiple types of documentation: design, end user, man pages, etc. Doxygen and other auto documentation tools help developers deal with a single, specific documentation problem - how to keep developer documentation in sync with the code. These tools make it easy to develop documentation on API usage, show the actual (not designed) interrelations between internal components, and do all the other documentation work that generally makes it much easier for a new developer to come up to speed in a particular area on a project.
That's it, really. The purpose is to automate an otherwise tedious task, and consolidate documentation in one location with the idea that having a single source for code and code documentaion will help prevent errors from creeping in. There's nothing character-building about hand-editing these sorts of docs, any more than it would be character building to execute all your build commands one by one on the command line instead of using a makefile.
Somewhere along the line, you will find yourself having to hack out code in a text editor, or use a less-than-top-of-the-line development environment, at which point you will have to fall back on your own skills and not those of an auto-documentation program.
Most of these auto-documentation tools work quite well on the command line, apart from any sort of IDE. A good number of them can produce decent documentation even if the source code wasn't written with the documentation tool in mind. These tools aren't complex, fancy whiz-bang sorts of things; they do a pretty straightforward job, do it well, and often are no more difficult to use than any other single-purpose tool. Whats more, most of them (Doxygen in particular) allow you to create links into your "real" (higher-level) documentation, so you can do interesting things like include pointers in the source code back to the features and requirements that it was written to support (and vice-versa).
I'm working in Eclipse right now, trying to debug a userland NFS server, and it's a pretty nice product. I may be biased, though, because my company sells an IDE based on Eclipse + CDT, so try it for yourself.
You'll need to install the CDT plugins for C/C++ work, but that's not a liability. In fact, it's really Eclipse's strength - there are literally hundreds of plugins (commercial and OSS) that can be integrated into the environment to give you exactly what you want.
Well said... I had much the same thoughts. Right now, I have a good job that pays well. What I find myself lacking is time. Being able to telecomute, to me, would mean not just the ability to spend an additional 5-6 hours a week with my family, but also the ability to spend those hours meaningfully - taking 15 minutes to go out and play catch with my oldest, for example, or rock my youngest when it's time for her nap.
I'm not sure I'd take a pay cut to telecommute, but forego a pay raise? Sure. Even if I wasn't missing on my commute time, the added flexibility would more than make up for a few extra dollars in each paycheck.
I'd go a step further and throw a semantic error if suffeciant comment's were not found before certain constructs.
Then you'd get comments like...
/*
* I needed to put a comment here to satisfy
* the stupid lameness filter. Next time, maybe
* I'll just copy and paste a comment off of
* slashdot instead of typing my fingers to the
* bone to satisfy the stupid comment length
* validator. Grr, still not enough text. So,
* Four score and seven years ago our forefathers
* brought forth a nation... that should do it,
* I think. Maybe. Almost there...
*/
Heh. I broke with a long tradition of "hardware for Valentines day", and got my wife Zuma instead. She's downstairs obsessing over beating level 9 even as I type this:-) Zuma wouldn't be too good for a head mouse - there's too much rapid-fire clicking going on.
On the other hand, my personal favorite so far is Rocket Mania. RM has a "strategy mode" where play is turn-based, and just as fun (if not more so) than the arcade-style variations. It's worth noting that the strategy-type game variations are a common feature of Popcap games - Noah's Ark, Big Money, and Dinomite all seem to have it, though you may have to pay for the "deluxe" version to get the strategy version of the games.
GPL has an important restriction -- you MUST give your changes back to the community if you want to distribute them.
<disclaimer type="IANAL">
Nope. The GPL says nothing about giving changes back to some "community". It does say that when you distribute a binary to someone, you must make the source code for that binary avilable to them (either as part of the distribution of the binary, or on request within a limited period of time.)
Practially speaking, this does mean that changes can and do make it back to "the community" in a lot of instances. However, it isn't required by the GPL.
To use your own analogy - the GPL doesn't force you to put your changes on the village green. It allows you to put them on the village green, and it also allows anyone who receives them from you (directly or indirectly) to put them on the village green. That allowance greatly increases the chance that someone will put your changes on the village green, but it doesn't make it a requirement.
Cell Phones : The amounts people dump on these is stupendous.
My wife & I have been using TracFone for a couple of years. There are a lot of other popular prepaid plans out there.
XM/Sirius : Can't get reception unless you pay.
Don't see much advantage over a CD player, really. I might if I travelled a lot, but even then, I think I'd be more likely to spend money for books on tape or something similar.
Cable/Satellite : Same again. Sure you can get it another way but your paying for a package.
Don't have it. Frankly, there are only two channels that we ever watched - the History channel and the Bug channel (er, I mean the Discovery channel.) Other than that, the TV pretty much just exists as a display device for the VCR/DVD player.
Aside from being an actual technology-loving geek type, I can guarantee an immediate increase in profits if you hire me.
How? Well, I'm willing to work for a measly one million dollars a year. No need for stock grants or options, either, though I will expect a good health care plan (I've got a family to take care of, after all).
Think about it, will you? I mean, I can't possibly be any worse for your company than Ms. Fiorina was. I have a five year old daughter I can bounce ideas off of, so that should help me avoid "pulling a Carly" - you know, doing something collosally stupid and "visionary", like buying Compaq and killing off core parts of the business.
Be honest, now: even if I sat in the office twiddling my thumbs all day, my tenure would still to be a net improvment over the past few years.
Slashdot Mirror
Not really - one of the basic ideas of inspiration is that the authors of scripture were not scribes, blindly copying down the words of God (well, unless you're talking about a direct quote :-) They were moved by the Spirit of God, and their own personalities, experiences, inclinations, vocabulary, mannerisms, etc. were taken into account by God and used to produce what God wanted inscrupturated.
In other words: God inspired them, and knew how to inspire them such that they would end up writing exactly what he wanted them to write. If there is any interpretation being done to fit a certain world view, it is not present because the human author inserted it - it is there because the inspiring author, God, desired and intended that particular interpretation.
That's where most people go wrong - the vast majority (99.9%) of Biblical theologians will tell you that it's the original writings (the autographa) that are inspired word of God, and that inspiration has nothing at all to do with translation. Those that disagree and think that translations are also inspired are so far out on the fringe that even the most conservative Christian believers consider them, um, "out there", to be polite. So revisions in a translation aren't a critical issue - you want a good translation, surely, and you want that translation to be based on accurately preserved copies of the autographa. A good Biblical scholar will recognize the problems and pitfalls present in using any translation, and base his or her study in the original languages (Greek, Hebrew, Aramaic) instead, in order to catch nuances and implications in the original languages that are lot or distorted by translation into a different language.
Ha! You think that's annoying? You should have seen their file formats before they moved to XML. In the early 90's, I had to write an NT service that would listen to their news feed and properly classify incoming stories. Based on what I had to deal with there, I can only conclude that they entered their story headers by means of repeatedly striking a keyboard with a spastic orangtan.
Well, OK, it wasn't quite that bad. I would have killed to have gotten the data in a semi-reasonable format like XML, though.
Heh. I like --preserve-sanity :-)
I took a look at the coreutils mailing list last night, to see if there had been any discussion about this sort of thing in the past. The impression I got was that standards compliance is pretty important - I don't think that breaking the connection between -f and interactivity would be possible, unless the relevant upstream standards were changed as well. Adding a specific extension like --preserve-sanity should be doable, though.
My opinion is that it should be the default, period. Personal experience is that I've only once had a bad rm -rf experience from an interactive shell... but I've had buggy scripts, Makefiles, etc. come back and bite me more than once. It's real easy to forget to set a variable, or set it in most cases, or just have a typo. Consider a makefile where you end up with a "clean" target that does rm -rf $(INSTALL_ROOT)/bin, and you mistakenly do a make INTSALL_ROOT=/tmp/foo clean. Ouch.
IMHO, admin scripts that want to recursively remove directories like ~, bin, etc, and so on are probably much less common than scripts that don't intend to have that behavior. But again, the requiement to adhere to standards means that it's unlikely that --preserve-sanity or its kin would ever become part of the standard, precisely for the reson you laid out - it would change the behavior of rm and potentially break existing scripts. Never mind that it's brain-damaged behavior to begin with... sigh. Maybe a compromise could be to have rm check for an environment variable ("RM_SANITY") and change its default behavior if set... though that just feels like an ugly hack.
Here you hint at the real prolem - the '-f' switch actually means 'ignore nonexistent files, never prompt'. If combines what should otherwise be two distinct aspects of behavior, how vigorous the command is at removing files, and whether or not the command is run interactively.
Because of this combining of aspects of behavior, the only two possibilities the command offers is to always prompt the user, and never prompt the user. You have the choice of absolute paranoid safety, or performing without a net - nothing in between. How safe you want the command to be is linked directly to how interactive you want the command to be. If you want the command to be non-interactive (using -f), then you must forego safety.
Ideally, rm would support options like the following:
Someone who uses the BSD license isn't "stealing" code. They're using the code in a manner consistent with the license it was provided under. Since it was the original author's choice to allow them to use the code in this way (making changes without requiring them to re-distribute the source), then what they're doing isn't "stealing", in any way, shape, or form. They're abiding by the terms of the license. The fact that you don't like those license terms, or the options that it gives someone, is irrelevant.
Besides - if you want to characterize the use of BSD code, in accordance with the license, as "stealing", then you'll need to accuse several prominent open-source projects of "stealing" code as well, since they include source code licensed under new-style (no advertising clause) BSD licenses.
Wow! Are you telling me RMS knows Vince Eirene?
(OK, OK, it's an obscure reference. Anyone who attended CMU in the late 80's - early 90's should get it, though.)
And here's the fallacy in your argument - that same difference in pay scale/cost of living means that the $350K US that they made off with was worth a whole heck of a lot more to them than it would be to you.
Would I risk something like this for 10 years' salary? Nope.
Would I risk something like this for 50 years' salary? I'd like to think no, but I've never been tempted like this...
Would I risk something like this for for more money than I could otherwise reasonably expect to earn in my lifetime? Maybe. Imagine yourself in a situation where a few minutes effort would net you $10 million of someone else's money. Can you be sure that you wouldn't consider that at all tempting?
I'm not sure where these guys ended up on that scale, but I suspect that you're still talking about enough money to live comfortably for 20-30 years. The cynical part of me says that their real problem was that they didn't steal enough. If it had been a few hundred million, then they wouldn't be thieves, just international market speculators...
Take a look at Pudge's comment about the authorship of this slashback. He started it, Timothy finished it. Complain about the the behavior of the Republicans and Democrats all you like, but the both /.'s token conservative and leading liberal poster had a hand in the article blurb.
Heatpipes? First I've ever heard of the term... what are they?
Not well. Back at you - do you read Greek?
And just like English, Hebrew words - words in any language - can have contextual meanings apart from their definitions. I'm not even talking about language constructs like similies and metaphors. For example, you can reliably assume that a Roman senator was male. It's not part of the definition of the word, but a reflection of the culture of the times and the context in which the word was used. You could have made the same assertion (sentor == male) in the US until this century as well.
I have to admit that I find it ironic that I am often accused of interpreting the Bible (OT and new) too literally, and here I am being harangued by you for not being literal enough.
You keep pressing that point, but aren't even trying to back it up. The connotations of the term certainly do imply virgiinity, in the same way referring to a "little girl" in modern English would imply virginity, or using "Miss" to address a woman in Victorian England would imply that she was unmarried and, presumably, a virgin.
No, she wouldn't be almah - read up a bit more; that term was never used for a married woman. It might be used for a woman who was betrothed, but not for a woman who's marriage had been consumated. In that case, she was neither almah nor betulah
Regardless of who did the translating: the translation of almah as parthenos was accepted by Alexandrian Jews and others who made use of the Septuagint. This seems to indicate that even if almah did not, specifically, mean "virgin", there was considerable overlap between the words.
The meaning of the Greek word is not determined by it's usage in the Septuagint; it's determined from it's usage in the Greek language. One of the more significant meanings of parthenos is virgin - Athena's two most prominent titles were Pallas Athena and Parthenos, specifically because she was the virgin goddess.
(BTW, if you could point me at a reference to the use of parthenos w/respect to Dinah, I'd appreciate it.)
From Liddel-Scott's Greek-English Lexicon, among others. Take a look at the various definitions for parthenos, and it's pretty clear that it means a virgin, or by implication, an unmaried woman presumed to be a virgin.
It definitely implies virginity. There are only 7 references to 'almah' in the OT, and four of those uses (Gen 24:43, Ex 2:8, Song 1:3, Song 6:8) refer to a "young woman" in a way that implies sexual innocence - someone who may be sexually experienced, but is generally assumed to be virginal; as one reference puts it, "the word clearly denotes a young woman who is not married but is of marriageable age... It is important to remember that in the Bible, a young Jewish woman of marriageable age was presumed to be chaste."
It's worth noting that the Septuagint translates "almah" in Isaiah 7:16 using "parthenos"; so, at least in some sense, the Alexandria Jews who translated the OT scriptures into Greek thought that the proper translation of "almah" in this case was, indeed, "virgin".
Build a standard rack with hollow piping, and pipe cold water through the rack itself. Use it as a huge heat sink for the servers - heck, you could probably figure out a way to make a direct connection from the rack to the CPUs with a strip of copper or aluminum. At the very least, you end up with the servers at least partially in contact with a big, cold, water-cooled hunk of metal. Get additional eco-points by using the now-warmed water as input for the building's hot water heater.
Whoops! You say that it's already been done? Dang. Just when I thought I was smart...
I'll second this - P4 is a great SCCS. We torture it daily (125+ distinct kernel branches for various embedded systems, plus corresponding root filesystem sources), and we've had only a handful of extremely minor problems over the past three years.
If the folks over at Perforce are smart, they'll jump in and offer a free, no-strings attached agreement that would contibute a pool of perpetual P4 licenses to the Linux community that can be used for hosting Linux source trees under P4. Linus may decline the offer, but just making the offer would be great publicity and cost Perforce nothing.
For three days the world had watched while chirpsithtra executioners smothered four men slowly to death. In some nations it had even been televised. "Don't you see, we don't *do* things like that. We've got laws against cruel and unusual punishment."
"How do you deal with cruel and unusual crimes?"
I shrugged.
"Cruel and unusual crimes require cruel and unusual punishment. You humans lack a sense of proportion, Rick Schumann."
No, no, no... haven't you read The Seven Habits of Highly Effective Pirates?
It sounds like you've never used one of these tools. There are multiple types of documentation: design, end user, man pages, etc. Doxygen and other auto documentation tools help developers deal with a single, specific documentation problem - how to keep developer documentation in sync with the code. These tools make it easy to develop documentation on API usage, show the actual (not designed) interrelations between internal components, and do all the other documentation work that generally makes it much easier for a new developer to come up to speed in a particular area on a project.
That's it, really. The purpose is to automate an otherwise tedious task, and consolidate documentation in one location with the idea that having a single source for code and code documentaion will help prevent errors from creeping in. There's nothing character-building about hand-editing these sorts of docs, any more than it would be character building to execute all your build commands one by one on the command line instead of using a makefile.
Most of these auto-documentation tools work quite well on the command line, apart from any sort of IDE. A good number of them can produce decent documentation even if the source code wasn't written with the documentation tool in mind. These tools aren't complex, fancy whiz-bang sorts of things; they do a pretty straightforward job, do it well, and often are no more difficult to use than any other single-purpose tool. Whats more, most of them (Doxygen in particular) allow you to create links into your "real" (higher-level) documentation, so you can do interesting things like include pointers in the source code back to the features and requirements that it was written to support (and vice-versa).
I'm working in Eclipse right now, trying to debug a userland NFS server, and it's a pretty nice product. I may be biased, though, because my company sells an IDE based on Eclipse + CDT, so try it for yourself.
You'll need to install the CDT plugins for C/C++ work, but that's not a liability. In fact, it's really Eclipse's strength - there are literally hundreds of plugins (commercial and OSS) that can be integrated into the environment to give you exactly what you want.
Well said... I had much the same thoughts. Right now, I have a good job that pays well. What I find myself lacking is time. Being able to telecomute, to me, would mean not just the ability to spend an additional 5-6 hours a week with my family, but also the ability to spend those hours meaningfully - taking 15 minutes to go out and play catch with my oldest, for example, or rock my youngest when it's time for her nap.
I'm not sure I'd take a pay cut to telecommute, but forego a pay raise? Sure. Even if I wasn't missing on my commute time, the added flexibility would more than make up for a few extra dollars in each paycheck.
Then you'd get comments like...
* I needed to put a comment here to satisfy
* the stupid lameness filter. Next time, maybe
* I'll just copy and paste a comment off of
* slashdot instead of typing my fingers to the
* bone to satisfy the stupid comment length
* validator. Grr, still not enough text. So,
* Four score and seven years ago our forefathers
* brought forth a nation... that should do it,
* I think. Maybe. Almost there...
*/
Heh. I broke with a long tradition of "hardware for Valentines day", and got my wife Zuma instead. She's downstairs obsessing over beating level 9 even as I type this :-) Zuma wouldn't be too good for a head mouse - there's too much rapid-fire clicking going on.
On the other hand, my personal favorite so far is Rocket Mania. RM has a "strategy mode" where play is turn-based, and just as fun (if not more so) than the arcade-style variations. It's worth noting that the strategy-type game variations are a common feature of Popcap games - Noah's Ark, Big Money, and Dinomite all seem to have it, though you may have to pay for the "deluxe" version to get the strategy version of the games.
<disclaimer type="IANAL">
Nope. The GPL says nothing about giving changes back to some "community". It does say that when you distribute a binary to someone, you must make the source code for that binary avilable to them (either as part of the distribution of the binary, or on request within a limited period of time.)
Practially speaking, this does mean that changes can and do make it back to "the community" in a lot of instances. However, it isn't required by the GPL.
To use your own analogy - the GPL doesn't force you to put your changes on the village green. It allows you to put them on the village green, and it also allows anyone who receives them from you (directly or indirectly) to put them on the village green. That allowance greatly increases the chance that someone will put your changes on the village green, but it doesn't make it a requirement.
</disclaimer>
My wife & I have been using TracFone for a couple of years. There are a lot of other popular prepaid plans out there.
Don't see much advantage over a CD player, really. I might if I travelled a lot, but even then, I think I'd be more likely to spend money for books on tape or something similar.
Don't have it. Frankly, there are only two channels that we ever watched - the History channel and the Bug channel (er, I mean the Discovery channel.) Other than that, the TV pretty much just exists as a display device for the VCR/DVD player.
Aside from being an actual technology-loving geek type, I can guarantee an immediate increase in profits if you hire me.
How? Well, I'm willing to work for a measly one million dollars a year. No need for stock grants or options, either, though I will expect a good health care plan (I've got a family to take care of, after all).
Think about it, will you? I mean, I can't possibly be any worse for your company than Ms. Fiorina was. I have a five year old daughter I can bounce ideas off of, so that should help me avoid "pulling a Carly" - you know, doing something collosally stupid and "visionary", like buying Compaq and killing off core parts of the business.
Be honest, now: even if I sat in the office twiddling my thumbs all day, my tenure would still to be a net improvment over the past few years.