Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news-out.readnews.com!transit4.readnews.com!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: Error Testing Date: Fri, 1 Nov 2013 08:32:24 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 15 Message-ID: References: <33549834-2f27-47f3-abea-eb3486909dec@googlegroups.com> <9e734f2b-9bcd-47d8-adb9-de6501fa6e7d@googlegroups.com> <52717d82$0$1677$e4fe514c@dreader35.news.xs4all.nl> <586c9c5d-d0d4-44c7-8454-94dcfc128318@googlegroups.com> NNTP-Posting-Host: c-24-118-110-103.hsd1.mn.comcast.net X-Trace: reader1.panix.com 1383294744 29604 24.118.110.103 (1 Nov 2013 08:32:24 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Fri, 1 Nov 2013 08:32:24 +0000 (UTC) User-Agent: slrn/1.0.1 (Linux) Xref: csiph.com comp.lang.python:58246 On 2013-11-01, William Ray Wing wrote: > Actually, FORTRAN is probably responsible for more CPU cycles being > executed even today than most other languages. If you think about > the fact that most large scientific simulation codes (weather > forecasting, combustion modeling, finite-element modeling and so on), > are still FORTRAN based, and that those are the codes that occupy > multi-hundred-thousand-core petaflop class supper computers for weeks > on end, you have to respect its longevity. IIRC, some of the scientific computing libraries I used to use daily in Python data-crunching programs are still written in FORTRAN. -- Grant