What a weird and pointless comparison, imo (I mean the inclusion of Python, seems so random to me).
133 karma · joined April 27, 2014
What a weird and pointless comparison, imo (I mean the inclusion of Python, seems so random to me).
Any evidence? If it's personal experience, then mine is exactly the opposite.
I don't know if such a thing exists, but maybe a big list of the main changes would help convince people more (type annotations, yield from, the forthcoming @ operator). From what I've seen and read, of course all this is somewhere in the docs and release notes, but I've never seen a clean concise list of the main new features, fixes and reasons why these features are cool.
And in the Twitter, they have this thing that from the timeline you can swipe to "Discover", and it's only shown by a small set of "pagination" circles on top – there's no explicit mention of this, and the circles are kind of easy to miss.
I'm still considering Rackspace as an alternative.
For personal and test projects, I use DigitalOcean – the lower price being the main reason.
Linode resizing seems a bit better, too – so for a big project which (hopefully) will need scaling, that's a plus. But I ran a Linode for two months before switching to DO, and tried to resize the disk image, and the whole thing went unresponsive, had to start from scratch (thankfully, no data was lost, I was just playing at that moment).
The worst part (not taking into account the coding style per se) for me was the (sometimes) inability to reuse the code I've encountered or adapt it to other cases.
I think scientific advisors should make a point which goes something like "If you're serious about your work, you might find one day that someone else wants to use parts of your code, so take that into account when planning your program". In my experience, a lot of programs are written as quick-hack solutions, and then there is no time to rewrite them, they grow bigger and it just snowballs from there.
The way CS was taught to us (and we're a big university) was pretty bad. No coding style, no experience with CVS, nothing concerning planning before writing new code. In the end, a lot of people got the bare minimum amount of knowledge needed to code, and started doing research using that knowledge.
And this looks a tad easier to find and understand than the standard docstring variable types description.
And this, imo, has more to do with the way CS is taught to scientists - I had a two-year course in C/C++, and we spent those two years writing all kinds of trees, lists and stuff like that. Needless to say, that is good and all, but that didn't exactly help us with writing scientific code later on - a lot of people wrote terrible code to get their AVL trees working, for example, just to get a passing grade. No one taught coding style, working with CVS, computer arithmetics and such. The same goes for the MATLAB course I took.
In my opinion, it would've been a lot wiser to teach people scientific computing using Python. It has tons of scientific libraries (a lot of people that I know who are involved in scientific computations often neglect to re-use code, use publicly available libraries; teaching people how to use third-party packages/libraries is important), forces programmers to indent (the amount of unindented C code I've dealth with makes me shudder), and makes them realize what makes a program fast or slow. Besides, using Numba/Cython/Theano/multiprocessing), it is possible to give a more or less painless introduction to the world of parallel/optimized computing. And only then start teaching C/C++/OpenMP/MPI/Fortran.
Now, I'm judging from my personal experience and from what I've seen at my university (which is the second-biggest research university in the country), there's a huge difference between how CS is taught to CS students and science students (physics, mechanics). The knowledge that science students receive is subpar, and, unfortunately, enough to start writing computational code.