I'm maintaining _why's Hackety Hack, which was built specifically for this purpose. It's still in "not quite 100% ready yet" mode, but you can at least keep your eyes peeled. I'm also quite open to thoughts and suggestions.
http://hackety-hack.heroku.com/http://github.com/steveklabnik/hacketyhack
It was. From Twitter:
RT @G20IMC Epic Police Fail: http://bit.ly/3lJ6Z2 Undercover officers attempt to infiltrate a March Against Police Brutality #G20 #reportg20
The protest started in Lawrenceville, as that's a neighborhood that's full of those sympathetic to the protesters, as well as having a great park for a gathering place. Then, when the police blocked off Penn Ave, the protest moved around them and into some other neighborhoods. The police regrouped, tear gas started to fly, the LRAD was activated, then the dumpster happened, the protest moved back up Liberty away from downtown, an ATM was vandalized, police started firing rubber bullets, the last gasps of that group bled through north oakland into oakland proper.
A group of students had gathered to see Obama's motorcade pull into Phipps, but the police heard that the protest was coming down Craig, so they started attacking students with tear gas. Some storefronts got broken.
Though I'm using Git for about year now, I'm pretty much n00b. Outside of the obvious - git init/add/commit/diff/pull/push/update + gitk - I know very little. That's why it is also very hard for me to understand the usual complain about Git that it is very arcane. Yes, documentation is very poor and still can't catch up with all the features, yet you rarely run into the need for some esoteric function or syntax. Basic commands are pretty much "intuitive".
I'm basically the same as you. I rarely use anything but those commands, and I'd agree that git is pretty easy to use, as long as you're sticking to the basics.
From what I understand, git used to be a huge patchwork of scripts that were much more difficult, and they spent some time a while ago making them a bit easier.
The release still has to come from somewhere. The idea is that you let GitHub become the repo where everyone starts from. Only the lead maintainer (or whoever) actually has access. He only merges that repo with his. He only merges his repo with the ones of the leads for each major section of the project. They only merge changes with people who are working on their section...etc. Think pyramid. This is how Linux is handled.
Other people have answered, but I feel that Linus can explain things for himself. Linus talks about Git. He discusses how it works with the kernel...even thought it's a bit long, it's pretty good as an intro to the git vs svn argument.
You, sir, are as broken-minded as he is. Forgetting about "fair" for a moment and considering this as a military simulation as it attempts to be, using your fellow soldiers as fodder is an offense that would lead one to the firing squad.
Halo 3 is nowhere near a 'military simulation.' But yes, I agree with you.
Using your team mates to further your own score is immoral.
In a video game? Hardly. Besides, in most games, when you're playing on a team, it's better for the team if everyone works together. If you were up against an actual challenge rather than your other kids, you probably would have lost the game due to your son's actions. The only reason he can kill steal at all is because your opposition is so easy that it doesn't even matter if he plays the game for real. Either that, or he's just stupid, but since you're calling into question the whole idea, I figure I'll give him the benefit of the doubt.
If you think "fair" is the same as "legal" then you show a trait that is also indicative of why our legal system is as abused as it has become. Morality plays a role in life even in game play.
While I agree that our legal system does get abused, it's set up that way. Those in charge want it to be able to be abused. And real life, with real consequences, is just a bit different than a game, so it's not even really relevant to this discussion. I disagree with the basic notion of kill stealing being immoral. Which is fine. I just felt that I'd try to explain another side of the story.
Sorry, I may not have explained myself fully. I (as a competitive type most of the time) prefer that a game is close. I wouldn't enjoy a game where there is no challenge at all. However, I will still try to win by as much as possible.
My son does not know the meaning of fair play. When we were playing Halo2 as team members, his favorite tactic was to hold back until he heard one of the others engaged in fire and then come in at an angle to clean up and get the kills.
Did your son mod the engine? Did he do something that you yourself could not do? Then it's fair.
Since when is taking advantage of others "fun" or part of a game?
The point of a game (to competitive types) is to win. Your son found a valid strategy that let him win. He didn't break any rules. He played within the game.
I like to describe this as competitive vs 'fluffy'. Fluff has no negative connotations, it comes from Warhammer, and it essentially means 'story.' Some WH players are interested in the game as a game, and tournaments. They'll sometimes build armies that don't really fit the fluff, but are much better than one that would. They're not breaking rules, they allow for armies like that. But people who are into fluff would rather play a non-competitive game where the story is just as sacred as the rulebook.
Now, I'm not saying you're interested in Halo's story. But what I am saying is that it seems like you want a game to be pretty much even, with one person barely pulling it out in the end. Everyone (almost) wins. That's great. It's also what the competitive people want. The difference is, the competitive people want to use every single last trick in the book to make it as hard for you to win as possible. In order to win games, your opponents have to lose. It's enjoyable for the competitive types to have the game still be close, even after that.
Anyway, I'm rambling. The point is, your son is just competitive. Or maybe not. But I hope you can at least see the viewpoint.
If you can't learn, then there is no point at all.
Incidentally, this is why when you play online it ranks you and only matches you up against people of your skill level. If you're a newbie, pretty soon you're also playing with only other newbies, and then you're free to learn in an environment where these kinds of conflicts don't happen. I agree that it sucks when everyone is destroying you and you can't do anything about it. Online play is nice in that regard.
And that's why your opinion is irrelevant. Please purchase a trade paperback version, support the creators of the original content, then try again.
You do know that Alan Moore never really felt that he was properly compensated for the book, and it was bad enough that it caused him to split from DC and never work for them again, right?
But don't let me spoil your good feelings for you. Don't get me wrong, your intentions are well placed. But don't forget that you're not always supporting the artist when you buy.
This coming from someone who just got their dead tree Watchmen today. I re-read it all in one sitting. So good...
Totally true. I'm on C's side (see my other comments in this thread). But I was pointing out that that there is at least one case where code without a semicolon will still compile.
I did learn C++, back in the day when it was a superset...but I stopped, because I didn't really like it.
I mean, how the hell can you write a program these days without OOP,
Honestly... I don't really like writing most things in OO style. I tend to find that most of the time, OOP is just done for OOP's sake, and it's much easier to just program in a procedural manner. A lot of "OO" code is just procedural code in OO clothing.
However, sometimes, it does make sense. Quite a bit of the coding I do is OO code. But that's usually because I'm working with other people who write in OOP style first.
exceptions
I don't like exceptions. It could be that I've been exposed to too much bad Java code, but again, I've found that most of the time, a try/catch block is wrapped around the smallest amount of code that it needs to be. Is
I mean hell, C can't even deal with strings in any reasonable way.
For your value of 'reasonable', anyway. I'll admit that it requires a tiny bit of extra knowledge compared to other languages, but it's certainly not difficult, and follows pretty logically from C's core ideas.
There is something to be said for pursuing the more modest rewards of a regular paycheck and the chance to gain some practical experience in your chosen profession.
Agreed.
Windows is a significant presence in almost every market segment. If you can find nothing of interest going on there, that says more about you than it does about the OS.
For me, it comes down to using the best tools. I only want to use what's best for the job, and I believe that only rarely is Windows the best tool.
I guess this backs up your point, it does say more about me than about the OS itself...
The problem with C++ is that it's a crazy, crazy language. At first, it was just a superset of C, but now there's all kinds of stuff...it's mutated into a totally different kind of thing. C has this elegant simplicity going for it. There's nothing the matter with C++...except that C is (pretty much) perfect.
Also your feel dirty comment, is that because of the ease in which a poor programmer can create unstructured code? If so would it not be the fault of the programmer and not the language specifically? (i.e. Assembly for the 8088,..286,..386 and IBM Mainframe made me feel dirty sometimes with they way you were forced to branch, but it was fast...and no I am far from an expert Assembly programmer.
The problem with PHP (and I code mostly in it for a living) is that it wasn't 'designed' at all. Originally it was just a pre-processor, and it's grown into a full blown language from there. This is all well and good, except that there's no sort of continuity to it at all. Naming conventions? (isset vs every other 'is' function starting with 'is_', etc) Who needs them? OO? Sure...ish.
PHP is great for getting things done, but I certainly feel dirty after coding in it.
FYI, personally I do not have a preference and simply choose what is convenient for me to use that will get the job done, period. I honestly do not know the nuances between them...and I am sure that there are some.
I won't pretend to remember Lisp inventor John McCarthy's exact words which is odd because there were only about ten but he simply asked if Python could gracefully manipulate Python code as data.
"No, John, it can't," said Peter and nothing more, graciously assenting to the professor's critique, and McCarthy said no more though Peter waited a moment to see if he would and in the silence a thousand words were said.
Slashdot Mirror
I'm maintaining _why's Hackety Hack, which was built specifically for this purpose. It's still in "not quite 100% ready yet" mode, but you can at least keep your eyes peeled. I'm also quite open to thoughts and suggestions. http://hackety-hack.heroku.com/ http://github.com/steveklabnik/hacketyhack
There were infiltrators: http://bit.ly/3lJ6Z2
It was. From Twitter: RT @G20IMC Epic Police Fail: http://bit.ly/3lJ6Z2 Undercover officers attempt to infiltrate a March Against Police Brutality #G20 #reportg20
The protest started in Lawrenceville, as that's a neighborhood that's full of those sympathetic to the protesters, as well as having a great park for a gathering place. Then, when the police blocked off Penn Ave, the protest moved around them and into some other neighborhoods. The police regrouped, tear gas started to fly, the LRAD was activated, then the dumpster happened, the protest moved back up Liberty away from downtown, an ATM was vandalized, police started firing rubber bullets, the last gasps of that group bled through north oakland into oakland proper. A group of students had gathered to see Obama's motorcade pull into Phipps, but the police heard that the protest was coming down Craig, so they started attacking students with tear gas. Some storefronts got broken.
4GB sticks are different than 2GB sticks. Yes, 2GB sticks cost $100, and 4GB sticks cost $500. It's harder to fit 4GB on one stick than 2GB.
It's not intuitive to people who've never used a Mac. It's worked that way in Mac-land for decades, we'd be confused if it worked a different way.
Check out GitForDarcsUsers. Also, you may be interested in why ghc switched to git.
Though I'm using Git for about year now, I'm pretty much n00b. Outside of the obvious - git init/add/commit/diff/pull/push/update + gitk - I know very little. That's why it is also very hard for me to understand the usual complain about Git that it is very arcane. Yes, documentation is very poor and still can't catch up with all the features, yet you rarely run into the need for some esoteric function or syntax. Basic commands are pretty much "intuitive".
I'm basically the same as you. I rarely use anything but those commands, and I'd agree that git is pretty easy to use, as long as you're sticking to the basics.
From what I understand, git used to be a huge patchwork of scripts that were much more difficult, and they spent some time a while ago making them a bit easier.
The release still has to come from somewhere. The idea is that you let GitHub become the repo where everyone starts from. Only the lead maintainer (or whoever) actually has access. He only merges that repo with his. He only merges his repo with the ones of the leads for each major section of the project. They only merge changes with people who are working on their section...etc. Think pyramid. This is how Linux is handled.
Other people have answered, but I feel that Linus can explain things for himself. Linus talks about Git. He discusses how it works with the kernel...even thought it's a bit long, it's pretty good as an intro to the git vs svn argument.
You, sir, are as broken-minded as he is. Forgetting about "fair" for a moment and considering this as a military simulation as it attempts to be, using your fellow soldiers as fodder is an offense that would lead one to the firing squad.
Halo 3 is nowhere near a 'military simulation.' But yes, I agree with you.
Using your team mates to further your own score is immoral.
In a video game? Hardly. Besides, in most games, when you're playing on a team, it's better for the team if everyone works together. If you were up against an actual challenge rather than your other kids, you probably would have lost the game due to your son's actions. The only reason he can kill steal at all is because your opposition is so easy that it doesn't even matter if he plays the game for real. Either that, or he's just stupid, but since you're calling into question the whole idea, I figure I'll give him the benefit of the doubt.
If you think "fair" is the same as "legal" then you show a trait that is also indicative of why our legal system is as abused as it has become. Morality plays a role in life even in game play.
While I agree that our legal system does get abused, it's set up that way. Those in charge want it to be able to be abused. And real life, with real consequences, is just a bit different than a game, so it's not even really relevant to this discussion. I disagree with the basic notion of kill stealing being immoral. Which is fine. I just felt that I'd try to explain another side of the story.
Sorry, I may not have explained myself fully. I (as a competitive type most of the time) prefer that a game is close. I wouldn't enjoy a game where there is no challenge at all. However, I will still try to win by as much as possible.
As for cheaters, though, no sympathy. They suck.
My son does not know the meaning of fair play. When we were playing Halo2 as team members, his favorite tactic was to hold back until he heard one of the others engaged in fire and then come in at an angle to clean up and get the kills.
Did your son mod the engine? Did he do something that you yourself could not do? Then it's fair.
Since when is taking advantage of others "fun" or part of a game?
The point of a game (to competitive types) is to win. Your son found a valid strategy that let him win. He didn't break any rules. He played within the game.
I like to describe this as competitive vs 'fluffy'. Fluff has no negative connotations, it comes from Warhammer, and it essentially means 'story.' Some WH players are interested in the game as a game, and tournaments. They'll sometimes build armies that don't really fit the fluff, but are much better than one that would. They're not breaking rules, they allow for armies like that. But people who are into fluff would rather play a non-competitive game where the story is just as sacred as the rulebook.
Now, I'm not saying you're interested in Halo's story. But what I am saying is that it seems like you want a game to be pretty much even, with one person barely pulling it out in the end. Everyone (almost) wins. That's great. It's also what the competitive people want. The difference is, the competitive people want to use every single last trick in the book to make it as hard for you to win as possible. In order to win games, your opponents have to lose. It's enjoyable for the competitive types to have the game still be close, even after that.
Anyway, I'm rambling. The point is, your son is just competitive. Or maybe not. But I hope you can at least see the viewpoint.
If you can't learn, then there is no point at all.
Incidentally, this is why when you play online it ranks you and only matches you up against people of your skill level. If you're a newbie, pretty soon you're also playing with only other newbies, and then you're free to learn in an environment where these kinds of conflicts don't happen. I agree that it sucks when everyone is destroying you and you can't do anything about it. Online play is nice in that regard.
Lots of companies incorporate in Delaware because their laws are sweet.
http://en.wikipedia.org/wiki/Delaware_corporation
http://corp.delaware.gov/faqs.shtml#numcorps
Also, see the question right below.
And that's why your opinion is irrelevant. Please purchase a trade paperback version, support the creators of the original content, then try again.
You do know that Alan Moore never really felt that he was properly compensated for the book, and it was bad enough that it caused him to split from DC and never work for them again, right?
But don't let me spoil your good feelings for you. Don't get me wrong, your intentions are well placed. But don't forget that you're not always supporting the artist when you buy.
This coming from someone who just got their dead tree Watchmen today. I re-read it all in one sitting. So good...
Only on the plain.
1337-ist?
I agree with your first sentence, but disagree with your second. I like wielding power tools.
Totally true. I'm on C's side (see my other comments in this thread). But I was pointing out that that there is at least one case where code without a semicolon will still compile.
I did learn C++, back in the day when it was a superset...but I stopped, because I didn't really like it.
I mean, how the hell can you write a program these days without OOP,
Honestly... I don't really like writing most things in OO style. I tend to find that most of the time, OOP is just done for OOP's sake, and it's much easier to just program in a procedural manner. A lot of "OO" code is just procedural code in OO clothing.
However, sometimes, it does make sense. Quite a bit of the coding I do is OO code. But that's usually because I'm working with other people who write in OOP style first.
exceptions
I don't like exceptions. It could be that I've been exposed to too much bad Java code, but again, I've found that most of the time, a try/catch block is wrapped around the smallest amount of code that it needs to be. Is
try { func(); } catch (Exception $e) { die("Died calling func: " . $e->getMessage(); }
really better than
#define TEST_ERROR(f, msg, ...) if(0 == f(__VA_ARGS__)) { fprintf(stderr, "Fatal error: %s", msg); }
TEST_ERROR(func, "Error calling func")?
generic containers/algorithms
Nice. But hardly neccesary.
user-defined data types
structs?
I mean hell, C can't even deal with strings in any reasonable way.
For your value of 'reasonable', anyway. I'll admit that it requires a tiny bit of extra knowledge compared to other languages, but it's certainly not difficult, and follows pretty logically from C's core ideas.
Can you think of even one situation where forgetting a semicolon would still result in code that compiles?
while(*p++ = *q++); anything_else();
I wouldn't be completely surprised if there is, but I can't think of one, and if it exists it's an edge thing.
Correct.
Why I don't use mono? I don't see the point in programming an app with a Microsoft framework on Linux.
There is something to be said for pursuing the more modest rewards of a regular paycheck and the chance to gain some practical experience in your chosen profession.
Agreed.
Windows is a significant presence in almost every market segment. If you can find nothing of interest going on there, that says more about you than it does about the OS.
For me, it comes down to using the best tools. I only want to use what's best for the job, and I believe that only rarely is Windows the best tool.
I guess this backs up your point, it does say more about me than about the OS itself...
...C++...
The problem with C++ is that it's a crazy, crazy language. At first, it was just a superset of C, but now there's all kinds of stuff...it's mutated into a totally different kind of thing. C has this elegant simplicity going for it. There's nothing the matter with C++...except that C is (pretty much) perfect.
Also your feel dirty comment, is that because of the ease in which a poor programmer can create unstructured code? If so would it not be the fault of the programmer and not the language specifically? (i.e. Assembly for the 8088, ..286, ..386 and IBM Mainframe made me feel dirty sometimes with they way you were forced to branch, but it was fast...and no I am far from an expert Assembly programmer.
The problem with PHP (and I code mostly in it for a living) is that it wasn't 'designed' at all. Originally it was just a pre-processor, and it's grown into a full blown language from there. This is all well and good, except that there's no sort of continuity to it at all. Naming conventions? (isset vs every other 'is' function starting with 'is_', etc) Who needs them? OO? Sure...ish. PHP is great for getting things done, but I certainly feel dirty after coding in it.
FYI, personally I do not have a preference and simply choose what is convenient for me to use that will get the job done, period. I honestly do not know the nuances between them...and I am sure that there are some.
Always a good way to be.
I won't pretend to remember Lisp inventor John McCarthy's exact words which is odd because there were only about ten but he simply asked if Python could gracefully manipulate Python code as data. "No, John, it can't," said Peter and nothing more, graciously assenting to the professor's critique, and McCarthy said no more though Peter waited a moment to see if he would and in the silence a thousand words were said.
http://smuglispweeny.blogspot.com/2008/02/ooh-ooh-my-turn-why-lisp.html