236 karma · joined January 4, 2010
My C++ and Java are very rusty, and I don't think I could do it on the spot if I tried; let alone go into languages like python and ruby that are new to me. But if you gave me a week or two, I know I could get up to speed.
Yes, this.
At the Museum of communism in Prague, there is an exhibit that talks of how the people in the eastern bloc were kept in a state of terror of the imminent threat of the American Weapons of Mass Destruction. Which was quite plausible, since the Americans had already nuked one country. Of course, this threat served political ends of damping down domestic dissent and disloyalty. Draw your own parallels.
we had a determined adversity who was dedicated to destroying us by any means possible in every realm
-sigh- Someone hasn't learned yet.
It has to be sold to me (or your typical departmental svn user). I do spend time learning new tools, but that time is limited, so I'm less likely to spend it on something that has the potential drawbacks that I raised.
FWIW, yes, I am trying out git on the side. That use of time looks worthwhile.
For most of us, no. For the SVN team, other forces are at work - I'd say familiarity of the code and desire for their baby to stay relevant are big ones.
Kinda not. Computers, IT, internet and mobile phones were just starting to change the way that everyday people did things in the 1980s. They really got going in the 1990s. The cold war and the USSR ended about then. The thing is, change is coming faster now than it did in 1990. And it's not slowing down.
using a new version with a few new features of an existing tool (svn) is always an easier sell than using two new tools (git, git-svn) as well, especially when one (git) has a reputation as being very complex, and the other (git-svn) looks like a hack to glue two different systems together.
Backup is not the point. The point is that you should be able to get onto a new machine, and execute your build process, and it should work. If some of the application files are missing, it wont.
I have a favicon.ico in some of my repositories.
It seems that all you're really saying is that your applications aren't media-intensive (binary files limited to an icon), and you don't want to think about ones that are.
That sounds just like the IQueryable<T> interface used in .Net's LINQ.
Did you read the article? The author says (and I totally agree) that refraining from tasteless jokes while at the airport is a small price that we we pay without concern, but the freedom to make bad jokes on the internet in your spare time is something else entirely. It's the thin end of the "censorship of all speech" wedge, really.
I personally used "oriented" - why use a longer word when a shorter one is precisely equivalent? Also, I'm used to it.
I was trying to forget about MySQL and it's plethora of engines.
- You have to choose engines
- Some features (e.g. ACID Transactions) don't work in some engines.
I'm not sure exactly why this is a feature. In PostgreSQL (and in most sane DB software)
- You don't have to choose engines
- All features work all the time. There's no posiblity of foolery like, say, beginning a transaction and then updating two tables, then finding that one of the tables will ignore the transaction but the other won't.
Jobs, on the other hand, probably cares more about his own business than about confusing Microsoft PR.
BTW, is Project Natal shipping?
I don't know, but they are hiring.
I'm not sure that follows. Last September isn't that long ago.