What they need is nice JIT engines like PyPy and not to switch languages.
If no one invested in improving implementations for modern languages and switched to something lower level all the time, we would still be using Fortran for business applications.
Personally I LOVE Python but I always feel it is the 2nd best choice. I do use Python but it rarely is the best tool to use for the problem you are solving. Maybe Pypy will turn this around, and I hope so.
Actually, the time-critical loops are usually implemented in C or Fortran. Much of SciPy is a thin layer of code on top of the scientific routines that are freely available at http://www.netlib.org/. Netlib is a huge repository of incredibly valuable and robust scientific algorithms written in C and Fortran. It would be silly to rewrite these algorithms and would take years to debug them. SciPy uses a variety of methods to generate “wrappers” around these algorithms so that they can be used in Python. Some wrappers were generated by hand coding them in C. The rest were generated using either SWIG or f2py. Some of the newer contributions to SciPy are either written entirely or wrapped with Cython.
A second answer is that for difficult problems, a better algorithm can make a tremendous difference in the time it takes to solve a problem. So using scipy’s built-in algorithms may be much faster than a simple algorithm coded in C.
http://www.scipy.org/scipylib/faq.html#how-can-scipy-be-fast...
Too many people just have the wrong impression, thinking that PyPy plans on re-implementing all the libraries that Numpy and scipy use but that's just completely false.
They have re-implemented the Numpy array so that it can take advantage of the JIT and so that parts of an algorithm implemented In Python that uses Numpy can also be optimized. Unlike what occurs when using Numpy under CPython where the Python code does not get optimized unless it is converted to Cython, C Code, or some alternative to Python to have it be optimized.
For me business applications are what you would use Cobol, Clipper, Java, Delphi, C#, Eifel, ....
Of course Fortran makes sense for number crushing, but that is the language domain, not doing CRUD, ETL or distributed computing stuff (not counting MPI here).
Do you intend to refer to a product done in those areas Fortran in modern days, maybe with Fortran 2008?
Outside scientific computing and heavy number crushing algorithms and libraries, I don't see a use for it.
I'm not saying anyone should use it today lol. Julia and R are the best for that sort of stuff. Way the hell ahead of Fortran. Although I thought about making a nice web application in Fortran just to screw with people who eventually try to extend it and gasp in horror. ;)
PyPy also has a slower startup time/overhead so very small amounts of work may end up slower than CPython but in general larger chunks of work will be faster if not its a bug and should be reported.
There is currently some work going on to improve the C extension issue. It's currently in its beginning stages and its goals are to provide both a significant amount of compatibility with existing extensions and a significant reduction in the overhead to call out to C extensions over what is currently implemented in PyPy. On the performance side the new approach was said to remove about 40% of the existing overhead. There are tons of corner cases that still need to be worked on for the new approach to become production worthy and there is no guarantee that there will be no show stoppers that come up or that the tail of corner cases that need to be dealt with becomes a nightmare and the approach is abandoned. If this works succeeds, it will be a game changer as suddenly the majority of libraries would then become compatible with PyPy.
In terms of performance naysayers only get convinced when someone proves them wrong, not because of what we think might be possible.
So it is important that we have research in GC systems, JIT compilers for dynamic languages, optimizers for FP and LP languages and so on.
Otherwise we might as well keep on using just Assembly.
The thing is I've never found another developer that new about it, something is very wrong...
>>> π = 3.14
In Python 2: >>> π = 3.14
File "<stdin>", line 1
π = 3.14
^
SyntaxError: invalid syntax Python 2.7.10 (850edf14b2c7, Oct 29 2015, 17:32:05)
[PyPy 4.0.0 with GCC 5.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>> π = 3.14
File "<stdin>", line 1
π = 3.14
^
SyntaxError: Unknown character
Are you sure you weren't trying it in Python 3 (or PyPy3) rather than PyPy? Python 2.7.8 (default, Sep 30 2014, 15:34:38) [GCC] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> π = 3.14
File "<stdin>", line 1
π = 3.14
^
SyntaxError: invalid syntax
>>>
also: Python 3.4.1 (default, May 23 2014, 17:48:28) [GCC] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> π = 3.14
>>> print(π)
3.14
The most popular package(s) that don't work with it have been numpy, scipy, etc. When I first encountered pypy, there was a numpypy and I wouldn't be surprised if that's different now. But bottom line, tons of python code out there needs more performance and has no dependency on numpy or any C extensions.