Is there a language more perfect than Python for Veeky Forums coding?

...

>t. neet
Computer time is cheap, programmer time is expensive.

Are you already a competent programmer? If so, learn the basics of Python data types and syntax, then choose some smallish projects to implement. When things don't work or you don't know what to do, look it up.

Can someone honestly disprove 's point? I really don't know why people consider Python as 'slow' when it saves so much development time? Sure, it's slow if you want to crunch numbers but for 80% of use cases I just don't understand why would you label it as 'slow'.

It's like saying that a car is slow in traversing 2000km and a plane is faster; sure, the car is slow but you can use it everyday whereas you barely use a plane unless you're traveling really long distances. Different tools for different jobs as they say, I believe.

Where does one find small projects?

I've literally gone to youtubes watched some lectures on python and did the exercise (converting DNA sequences and stuff to RNA) and other things like that. I didn't learn anything.

>Can someone honestly disprove 's point?
Literally no body can. You have to remember Veeky Forums is 99% filthy undergrad plebeians, they have no idea what the real world is like.

>Sure, it's slow if you want to crunch numbers
It's not though. Crappy Python is slow, but the solution to that is to not write crappy Python.
If you're doing large amounts of number crunching there's libraries designed for it rather than handling each element individually.

Depends on the "scientist". For my work I coded a solver in python that's 9x faster than it was in MATLAB that's already 10x faster than comparable finite element codes. I don't need to manipulate and analyze it til after I solve it. Since I'm already in python I do that in python too, not about to switch to R.

>Can someone honestly disprove 's point?
Computer time isn't "cheaper" than development time because you only develop your application once (in a loose sense, please don't start a nitpick semantics argument about versioning), whereas it will probably run a lot more than once when your consumers actually make use of it. That's kind of the whole point of programming and automation, you put in some work up front and get a reusable tool out of it afterwards instead of not putting in some work up front but having to do tasks manually over and over again.
i.e. It's an investment. Investments aren't immediately profitable, you give up something valuable up front with the expectation you'll reap a greater amount in benefits later.

I don't think most people on Veeky Forums are developing for consumers though. Most people here are probably just analyzing their own data.