I'll give it a shot. Mostly I was put off when I tried googling for help on the situation and came across a "vi vs emacs" post which said something along the lines of "Emacs is the world's only completely self-documenting editor! The only command you'll ever need to memorize is 'emacs', after that the on-screen instructions tell you exactly what to do!".. that experience pretty much told me I wanted to stick with an editor where I needed the huge learning curve of memorizing THREE commands right off, but which I could actually use.
This was my second attempt at trying out emacs. First time I tried it, years ago, I tried XEmacs. This was before I'd ever tried vi/vim. I started it up and it asked for login information for a newsreader. Eventually I got as far as accidentally inserting an image and changing the font size. I determined that emacs was not a text editor, and moved on.
On starting emacs, I was presented with: "Get help C-h (Hold down CTRL and press h)"
This sequence acts as a backspace key and has no effect on emacs itself other than to delete the random sentences it seems to have filled its default buffer with. Neat trick!
It also seems to have a friendly menu at the top which cannot be reached by any key combination. Minimal browsing on the web suggests that emacs is actually a moded editor, but the normal mode only lasts one command before you need to press an obscure sequence to get back to it. Oops?
As a serious question, the ignorant wanting to be enlightened: Why don't wireless access points just use some well-known and tested public key encryption? What problem is being solved by WEP/WPA/etc which simply broadcasting (or for the paranoid: copying over with a USB key) a regular old public key wouldn't cover?
because what's really awesome is using inconsistent syntax all the time just to save the use of ONE process on a modern system where thousands of processes may be created/destroyed in a second.
I would much rather cat somefile | grep foo, or somecommand | foo, rather than re-typing "grep foo somefile" (or was it "grep somefile foo"? just to satisfy someone else's ideal. cat does one thing and does it well. There's no reason for grep to even have the ability to open files itself, rather than just reading off the stream.
-- Some guy who thinks the world would be a better place if File->Open dialog boxes were launched as a separate process
Anyone elected (for president, congress, senate, whatever) right now who _WOULDN'T_ raise taxes is not fit for the job. You don't get to keep spending "free money" unless you want to either
a) Cause a severe global recession. or
b) continue one already caused by such practices.
The Iraq war sucks and all, but.. "Horrific"? Name a war which is more-tame than Iraq and actually qualifies as a "war" (not a one-sided bombing campaign)
If McCain of the election cycle was anything like McCain of the past, I would have voted for him. I like McCain. I like the fact that he seems willing to actually TALK to people "on the other side", and has in the past shown that he can express himself well. The "even when I don't agree with him, it looks like he believes it and his point seems rational" factor was quite refreshing.
I haven't seen that in at least ten months.
Election reform is the last thing on any winner's mind, though.
At some point they may just go from saying "our method cannot distinguish between these two knots" to saying "our method has proven that these two knots are the same, on a fundamental level". When that happens, you're screwed.
If you've ever had to deal with a business (or person, for that matter) who doesn't live in the same time zone, you already know how meaningless that is.
Not everyone needs to do everything at the same time. It's easier for one company to change their schedule than for the whole nation to agree to do so, and there are in fact some companies which, noting the stupidity of DST, change their hours at certain times of the year. Noticing that the sun is setting earlier is not the time to say "Let's run with it and make it look like the sun is setting EVEN EARLIER!", it's the time to say "Hey, boss, mind if I start coming in at eight and leaving at four so I don't get hit by quite so many buses on the way home?"
A little known fact: Working from 8 to 4 (or 8 to 5, or 9 to 6, etc, etc) does NOT cause spontaneous combustion in humans! In fact, studies have proven that going to work at the same time every day doesn't even depend on what arbitrary number is being pointed to on ANY device, be it a thermostat, clock, or even altimeter.
But the things are still always behind some piece of furniture or another, and I don't know if anyone told you this, but.. your switches are all upside-down!
If you're managing a single, centralized, monolithic project which references no external projects, git is for you. Its simplicity can make basic operations a joy to use. Some things which in Subversion are just plain broken (like, say, updating your local copy) are handled sanely by git in ways which will never lose work.
If you're managing code which references external projects, or multiple inter-related projects, Subversion is still the winner. Git has very little support for such things (it's coming along, but is currently young, hack-y and broken). Git is not designed to manage the relationships between "different" projects, and having them all in one place with Git requires just as much kludge with Git as it would take to merge changes from one SVN repository to another. (which Git reportedly excels at, though it seems to handle the parts which are sticky in SVN by ignoring them)
I came out a bit pro-svn-leaning, I suppose. For the record: I use git at home and svn at work. Tried using git-svn at work but it was completely unusable with multiple interrelated projects. My point is: Git is good in one situation and svn in others. I would much prefer to use git for everything, it just doesn't cut it for everything.
As for the article:
Point 1.1: "Git creates a full repository with this command."
Not an advantage. Creating a full repository is a different way of working, but as git's only options are "the whole history of the world, full-featured OMGEverything" or "shallow copy with no features", I would call this even with SVN. If Git adds the ability to "fall back to fetching from remote" when it needs extra information from a shallow copy, Git will have an advantage here.
Point 1.2: "With each branch, no new files are created in the project file hierarchy on your system. Since you have a full local repository"
Here is a man who does not know how branches work in SVN. Just because SVN has a horrible interface is no excuse for using an even worse one. svn copy long-ass-url long-ass-url, followed by svn switch long-ass-url is not only "correct" here, but a more accurate pairing with what the git command is doing. (The "git way" of doing what the svn command does is to create a hard-linked copy of the local clone).
Git also has the "disconnected operation" advantage here.
Point 1.3: "With Git, we only push our work to the server AFTER collaboration (more below). With Subversion, it all hits the server."
There are several readings of what this means. Some interpretations mean "You have stupid workflow practices", while others are clear git advantages. I love not pushing every little change until I'm ready for a nice rolled-up commit which will show clean and meaningful diffs to anyone browsing through history. But he could mean "I don't know what branching is for and made a blog post about it". I'll go with the "git is awesome" interpretation, though.
Point 1.4: "Again, no file system work. Since we're using a local repository, we let Git handle the details of removing the branch."
I fail to see how "I deleted it from the history, so I want all my local changes to be fucked with" is an advantage.
Point 2.1: "The key thing to note in this and every step is how we switch between branches."
You're doing it wrong. But I won't go into it because Git is fucking awesome at this. You just did a really really really bad job of showing why.
Point 2.2: "Git will 'float' uncommitted changes."
Stop using convoluted terminology and say "Git makes branching easy. Oh wait I said that already."
Point 2.3: "Same as 2, but shows the 'git stash list' feature."
Uhm, thanks? This has nothing to do with "git vs svn". Also, you're still doing it wrong.
Point 3.1: "Git has a nice feature to create 'patches.'"
Given that the first listed step is "check your email for patch", the whole argument is invalid. I can e-mail
What about/useful/ work? If you're running N millions of instructions per second on one watt, but all but one instruction in that is Operating System Overhead.... Microsoft vs Google would report it if they knew how to measure it.
My computer has this new green invention called a "switch". It's on the back of the computer, (so you can't hit it accidentally) and you can reduce your computer's power usage to zero while it's not in use, just by toggling the "switch".
What is considered "off" for computers is often what is termed "standby mode" by the green-conscious when referring to any other appliance.
as a recent immigrant, I notice many wall sockets here in the U.K. have a switch right on them, rather than needing to unplug a device to stop it from drawing power. I assume that most natives here do not own furniture, since otherwise these switches would be completely useless to everybody.
Everything that has a switch on the device, I really don't mind reaching over and flipping off. I haven't used my PS2 in months, so the red light on it stays off.
Slashdot Mirror
Poit! Egad! Zog! Fjord!
I'll give it a shot. Mostly I was put off when I tried googling for help on the situation and came across a "vi vs emacs" post which said something along the lines of "Emacs is the world's only completely self-documenting editor! The only command you'll ever need to memorize is 'emacs', after that the on-screen instructions tell you exactly what to do!" .. that experience pretty much told me I wanted to stick with an editor where I needed the huge learning curve of memorizing THREE commands right off, but which I could actually use.
This was my second attempt at trying out emacs. First time I tried it, years ago, I tried XEmacs. This was before I'd ever tried vi/vim. I started it up and it asked for login information for a newsreader. Eventually I got as far as accidentally inserting an image and changing the font size. I determined that emacs was not a text editor, and moved on.
So you were obviously pressing something other than C-h
tqat's impossible! I tqink I am perfectly capable of finding tqe (copying and pasting here:)"C-h" key on my keyboard.
Seriously, how much of a dipwad are you? "Well, it worked for me... clearly he's pressing completely random key combinations!"
Obama won't be president until he's sworn in, in January.
THEN everything will magically and instantly be fixed.
On starting emacs, I was presented with:
"Get help C-h (Hold down CTRL and press h)"
This sequence acts as a backspace key and has no effect on emacs itself other than to delete the random sentences it seems to have filled its default buffer with. Neat trick!
It also seems to have a friendly menu at the top which cannot be reached by any key combination. Minimal browsing on the web suggests that emacs is actually a moded editor, but the normal mode only lasts one command before you need to press an obscure sequence to get back to it. Oops?
As a serious question, the ignorant wanting to be enlightened: Why don't wireless access points just use some well-known and tested public key encryption? What problem is being solved by WEP/WPA/etc which simply broadcasting (or for the paranoid: copying over with a USB key) a regular old public key wouldn't cover?
Security through shit just plain not working in the first place? That's innovative, I like it.
because what's really awesome is using inconsistent syntax all the time just to save the use of ONE process on a modern system where thousands of processes may be created/destroyed in a second.
I would much rather cat somefile | grep foo, or somecommand | foo, rather than re-typing "grep foo somefile" (or was it "grep somefile foo"? just to satisfy someone else's ideal.
cat does one thing and does it well. There's no reason for grep to even have the ability to open files itself, rather than just reading off the stream.
-- Some guy who thinks the world would be a better place if File->Open dialog boxes were launched as a separate process
Anyone elected (for president, congress, senate, whatever) right now who _WOULDN'T_ raise taxes is not fit for the job. You don't get to keep spending "free money" unless you want to either
a) Cause a severe global recession.
or
b) continue one already caused by such practices.
The Iraq war sucks and all, but.. "Horrific"? Name a war which is more-tame than Iraq and actually qualifies as a "war" (not a one-sided bombing campaign)
If McCain of the election cycle was anything like McCain of the past, I would have voted for him. I like McCain. I like the fact that he seems willing to actually TALK to people "on the other side", and has in the past shown that he can express himself well. The "even when I don't agree with him, it looks like he believes it and his point seems rational" factor was quite refreshing.
I haven't seen that in at least ten months.
Election reform is the last thing on any winner's mind, though.
that number sounds inflated. What about the 32,000,000 people who read the reviews and didn't BOTHER downloading / buying spore?
At some point they may just go from saying "our method cannot distinguish between these two knots" to saying "our method has proven that these two knots are the same, on a fundamental level". When that happens, you're screwed.
Goodness I hope there still stamps in the future :)
for fuck's sake.. I hope there aren't!
If you've ever had to deal with a business (or person, for that matter) who doesn't live in the same time zone, you already know how meaningless that is.
Not everyone needs to do everything at the same time. It's easier for one company to change their schedule than for the whole nation to agree to do so, and there are in fact some companies which, noting the stupidity of DST, change their hours at certain times of the year. Noticing that the sun is setting earlier is not the time to say "Let's run with it and make it look like the sun is setting EVEN EARLIER!", it's the time to say "Hey, boss, mind if I start coming in at eight and leaving at four so I don't get hit by quite so many buses on the way home?"
When businesses "strike", it's called extortion.
A little known fact: Working from 8 to 4 (or 8 to 5, or 9 to 6, etc, etc) does NOT cause spontaneous combustion in humans! In fact, studies have proven that going to work at the same time every day doesn't even depend on what arbitrary number is being pointed to on ANY device, be it a thermostat, clock, or even altimeter.
I could get excited about The Phantom Menace all over again!
you haven't watched that movie recently, have you?
But the things are still always behind some piece of furniture or another, and I don't know if anyone told you this, but.. your switches are all upside-down!
If you're managing a single, centralized, monolithic project which references no external projects, git is for you. Its simplicity can make basic operations a joy to use. Some things which in Subversion are just plain broken (like, say, updating your local copy) are handled sanely by git in ways which will never lose work.
If you're managing code which references external projects, or multiple inter-related projects, Subversion is still the winner. Git has very little support for such things (it's coming along, but is currently young, hack-y and broken). Git is not designed to manage the relationships between "different" projects, and having them all in one place with Git requires just as much kludge with Git as it would take to merge changes from one SVN repository to another. (which Git reportedly excels at, though it seems to handle the parts which are sticky in SVN by ignoring them)
I came out a bit pro-svn-leaning, I suppose. For the record: I use git at home and svn at work. Tried using git-svn at work but it was completely unusable with multiple interrelated projects. My point is: Git is good in one situation and svn in others. I would much prefer to use git for everything, it just doesn't cut it for everything.
As for the article:
Point 1.1: "Git creates a full repository with this command."
Not an advantage. Creating a full repository is a different way of working, but as git's only options are "the whole history of the world, full-featured OMGEverything" or "shallow copy with no features", I would call this even with SVN. If Git adds the ability to "fall back to fetching from remote" when it needs extra information from a shallow copy, Git will have an advantage here.
Point 1.2: "With each branch, no new files are created in the project file hierarchy on your system. Since you have a full local repository"
Here is a man who does not know how branches work in SVN. Just because SVN has a horrible interface is no excuse for using an even worse one. svn copy long-ass-url long-ass-url, followed by svn switch long-ass-url is not only "correct" here, but a more accurate pairing with what the git command is doing. (The "git way" of doing what the svn command does is to create a hard-linked copy of the local clone).
Git also has the "disconnected operation" advantage here.
Point 1.3: "With Git, we only push our work to the server AFTER collaboration (more below). With Subversion, it all hits the server."
There are several readings of what this means. Some interpretations mean "You have stupid workflow practices", while others are clear git advantages. I love not pushing every little change until I'm ready for a nice rolled-up commit which will show clean and meaningful diffs to anyone browsing through history. But he could mean "I don't know what branching is for and made a blog post about it". I'll go with the "git is awesome" interpretation, though.
Point 1.4: "Again, no file system work. Since we're using a local repository, we let Git handle the details of removing the branch."
I fail to see how "I deleted it from the history, so I want all my local changes to be fucked with" is an advantage.
Point 2.1: "The key thing to note in this and every step is how we switch between branches."
You're doing it wrong. But I won't go into it because Git is fucking awesome at this. You just did a really really really bad job of showing why.
Point 2.2: "Git will 'float' uncommitted changes."
Stop using convoluted terminology and say "Git makes branching easy. Oh wait I said that already."
Point 2.3: "Same as 2, but shows the 'git stash list' feature."
Uhm, thanks? This has nothing to do with "git vs svn". Also, you're still doing it wrong.
Point 3.1: "Git has a nice feature to create 'patches.'"
Given that the first listed step is "check your email for patch", the whole argument is invalid. I can e-mail
Don't worry, I'm sure it made it here then, too.
10:04? 4:33? Sounds like somebody doesn't know which type of graph to use for which types of data.
"Could you average them?"
"Yes. I could also multiply them."
What about /useful/ work? If you're running N millions of instructions per second on one watt, but all but one instruction in that is Operating System Overhead.... Microsoft vs Google would report it if they knew how to measure it.
My computer has this new green invention called a "switch". It's on the back of the computer, (so you can't hit it accidentally) and you can reduce your computer's power usage to zero while it's not in use, just by toggling the "switch".
What is considered "off" for computers is often what is termed "standby mode" by the green-conscious when referring to any other appliance.
as a recent immigrant, I notice many wall sockets here in the U.K. have a switch right on them, rather than needing to unplug a device to stop it from drawing power. I assume that most natives here do not own furniture, since otherwise these switches would be completely useless to everybody.
Everything that has a switch on the device, I really don't mind reaching over and flipping off. I haven't used my PS2 in months, so the red light on it stays off.