Fortran is an awesome language, but clearly there's demand for something easier. Keep in mind that every single popular technical computing environment is dynamically typed.
On Sun, Oct 18, 2015 at 7:32 PM, LarryD <[email protected]> wrote: > How does this compare to the "old standard?" > > 1. Fortran requires every variable to have a defined type, but > automatically defaults to floating or integer type based on the first > letter of the variable name. Or, you can pre-define your own sets of > first-letter defaults with the Implicit command. Once you get used to this, > writing new code goes just as fast as if you didn't need to define types. > > 2. Optimizing compilers take care of most of the clean-up phase. No work > required. > > Larry > > > On Sunday, October 18, 2015 at 7:51:21 AM UTC-5, Sisyphuss wrote: >> >> The two-language problem refers to prototyping with one slow dynamic >> language and rewrite it with a fast static language for the final product. >> >> If Julia really solves the two-language problem, it should meet the >> following criteria: >> Let A be the code written during prototyping, B be the code written for >> the final product, with a small net increment $\Delta$, A+\Delta=B. >> >> If Julia uses one code style to do prototyping, and then uses a >> completely different style to write final product, then it can't be called >> the same language. At best, Julia turns the 2-language problem to a >> 1.5-language problem. >> >> >>
