I was one of the 16000 protesters in Munich. The message came to me via the evening TV news about germany delayed signing ACTA.
It was impressive to see how many people care about that topic. 200 attendants in London sounds like no protest at all.
If you leave aside C-extensions and libraries, CPython is a pretty bad language for number crunching. This is just not the use-case it tries to solve. I am glad they favor simplicity over execution speed.
Removing the GIL might be useful for a faster implementation with JIT compiler though.
This is not exactly true. We can alleviate the GIL issue by releasing it inside C extensions, true, but it is still there nonetheless. Incidentally, one of the big advantage of the GIL is to make C extensions easier to write.
As long as you are not creating or destroying the Python objects you expect to give back to the Python side of your program, you don't have to care much about it.
CPython is a pretty bad language for number crunching
Perhaps, but thanks to numpy, scipy and a host of other amazing libraries it still ties with matlab as the go to language for number crunching among everyone I know who crunches numbers for a living.
When you are used to the SVN/CVS workflow, it takes a long time to get over it. It took me a long time to understand why the distributed approach is better, despite having read a lot about them.
In my company we are using git as well, but most developers refuse to work anywhere else than on master. They probably had their share of trouble with branching in other systems.
I found the thing that tipped the scales for people who were set in their ways was walking them through a merge and showing that tree conflicts don't exist. And that merging doesn't need to take more than 5 minutes.
I work on a codebase that changes pretty fast, and git has hugely reduced time wasted screwing around with tree conflicts and SVN losing its lunch.
Two weeks are quite some time for an automation. But depending on how much time you spend every day, you might want to go for it. It's not only about saving time daily, it's even more about scaling things up.
If the process is automated, it should be quite easy to use modified versions for similar problems. And you can quickly run it again and again without having to worry about making mistakes.
This is a very biased view and it might become invalid in different market conditions. Just think of a great inflation or any market collapse. If you own a house, you can still live in there. But you can only burn your cash for heating.
As long as our financial system works, cash is of course the best form of an asset.
I was thinking about this a lot of times. Having some person to handle the kind of work I dislike.
But in the end, I guess it's too hard to realize. Headhunters are supposed to help you with it, but they never do. There had to be a different, employee-friendly incentive for them. However, I'd love to be proved wrong.
Yeah, absolutely. Lots of talk about talent wars but salaries have been going down according to some surveys. Also where is the actual recruitment? People call and want you to interview and they are not willing to state the range or agree to pay for travel expenses. Whatever. Not a real serious talent war.
Gingerbread has a concurrent GC, so animation should not stop completely. However, on a single core system I wouldn't expect this to have a huge impact. But this is just my personal guess.
