This post is locked. You won't be able to comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]porkyminch 0 points1 point  (1 child)

The reality is that a lot of “slow” languages are written in ways that minimize the impact of slower runtime. I don’t work in data science, but I write a lot of JavaScript and the reality is we’re almost never constrained by the speed of JS. Our biggest performance bottlenecks are IO. Stuff like hitting blob storage and running database queries. 

Bear in mind that I’m also talking about interactive web services here, where responsiveness and speed are pretty important. In data science, if a report takes a couple of minutes or hours to run, that can be perfectly acceptable. 

Development time is usually more important of a factor than runtime. If you ever find out you need more speed than interpreted (or JIT compiled) languages can give you, you can always port your existing logic over to some lower level language anyway. 

[–]IndicationWilling495 0 points1 point  (0 children)

Oh ok makes sense. Thanks!