It would've sucked in Warsow imo.

That's not a Warsow map.

They are quite organized, it's pretty hard to be disorganized, when you only have 2 main developers, and 2-3 occasional helpers.

I think the biggest hurdle in developing this version was actually the choice of using libRocket to script the UI with. Turns out the lib is very slow, and it needed lots of work to get working properly.

Yeah that is correct.

There's vic, me and toukka doing any coding and kimza mapping some, jihnsius doing the music, and have pretty good agreement over everything we do, so I wouldn't call us disorganized :)

When this game was founded, about 7 years ago, Quake 3 was at a pretty big peak. The original goal was to make the next big competitive FPS. Though that didn't last too long, even though the scene is still largely very competitive players, there's no big tournaments for the game. Another thing to note, is that Warsow's engine is actually based on idtech 2.

Yeah, the game right now I don't think is that good. I was talking with the developer and he's planing on doing some big gameplay changes. I really hope it turns out good, that game has a lot of potential.

I personally think it's better to break backwards compatibility if you're removing or changing something that was bad in the first place. Otherwise, there is no need, and thus it never breaks. Much like in the case of your list of non breaking programs.

> I personally think it's better to break backwards compatibility if you're removing or changing something that was bad in the first place.

This is the false dichotomy that I want to dispel. You can remove/change bad things while maintaining backwards compatibility in most cases! It just takes a little bit of extra glue code!

Considering the post is titled "How I lost access to my Google account today," there is a lack of how.

It's well known that your data should be redundant, this is one of those 'I didn't make a backup' posts.

But then there's python.

The reason people don't complain about Python is because if you don't like the language, there is no reason to use it, so they don't. When people are forced to use it, they do complain--stupid scoping, horrible lambdas, no pattern-matching, weird desugaring, idiotic default argument semantics and so on. (These are all the things I've heard about it from other students in my compilers course.)

People use C and C++ when they need fast code close to the machine. People use Java when they need more portability but can't sacrifice performance completely. People only use Python because they like it.

I have always felt Python is the new Java. Same qualities of verbosity, low barrier to entries.

And weird level of verbosity for a scripting language.

I do not know why someone has downvoted zxy. He/she has the point: python is used by many but few dislike it. Python is a third kind: the ones people like. Bjarne was looking for excuses for his bad C++.

I don't know, I know a ton of people who don't like Python. The difference is that unlike C or C++ or even Java, if you don't like the language itself there is no compelling reason to use Python, and so those people don't.

That said, when people do have to use Python, like in my compilers class right now, quite a lot are not happy with it. (Even the professor gets annoyed with it; I really don't know why we're using it.) So I think there is just much more selection bias in the land of Python than in C++ or Java.

Yes, that could explain off some differences between python and C++ in these two polls, but right now, over 95% python voters favor it as opposed to about 50% for C++. I can hardly believe your argument alone can explain off this huge difference. Also, look at C and C#. A lot of programmers are forced to use them, too, but they seem to like them better than C++ at least in the HN community. On the other hand, I agree that Python may not be the best choice for a course on the compiler theory. I am sure more would hate python if they were asked to develop a linux kernel with python.

I complain about python all the time, but I'm in the minority.

Is that the language with `pass`?

Are you complaining about the backticks or the pass keyword, or both?

Strike!

I remember Linus saying they only keep the last 5 years of commits, because more isn't really necessary.

I think it's very dependent on the project. There really are times in php-src when you want to be able to go back a fair way, since the last significant change to function's implementation may well have been 10 years ago in the early 4.x days (and Git is going to be a huge win for us there over Subversion).

I wouldn't be surprised if it makes much less sense for the kernel, though.

The cool thing :target allowed was those css3 only lightboxs (http://tympanus.net/Tutorials/CSS3Lightbox/). I might play around with this method and see if it works as well.