4 ms·

The scientific community is not going to adopt any new language until most used idioms can be easily found in a quick search and copy-pasted. It is extremely di

by yiyus 11y ago

The scientific community is not going to adopt any new language until most used idioms can be easily found in a quick search and copy-pasted. It is extremely difficult to arrive there. I totally agree that having dynamic dispatch in the first position of the features list, for example, does not help. But, in my opinion, it is ok for a pre-1.0 language. That is what makes exciting seeing some external help to release a stable version.

CyberDildonics 11y ago
What's wrong with dynamic dispatch?
- yiyus 11y ago
  Nothing at all. But, if Julia takes off, I would not expect it to be the main selling point. It can be a very interesting feature for somebody into language design, but the average Joe working in a lab is not going to learn a completely new language and rewrite all his Matlab code because of it. Most probably, he has not idea what it is or why he would want it. It was an example of how, at this point, it seems like the web site is more directed towards language developers than potential users.
  - elcritch 11y ago
    Actually, I think the main page is directed toward those scientific users who create their own custom projects and/or libraries. This also goes back to your earlier point in that early in a language evolution you need more library and package creators so you can have a broad ecosystem for the more day to day programmers. One example of this need, is the creator of the fftw library (a cornerstone fft implementation in C) wrote several popular packages for Julia. I think there's a talk he gave at the 2014 JuliaCon. In this regard, multiple dispatch is actually a huge selling point! I've written in Fortran 90 code, C, Python, and enjoyed most of those languages. There is something unique about being able to pull up the source code for almost every operator/function in the language, implemented in that language. Fortran has this, but is much more statically oriented and difficult for quick scripting. Python, well I'm hopeful pypy keeps building momentum. Or perhaps Pyrhon ported to web assembly, in more pure Python.

by yiyus 11y ago

CyberDildonics 11y ago

What's wrong with dynamic dispatch?

yiyus 11y ago
Nothing at all. But, if Julia takes off, I would not expect it to be the main selling point. It can be a very interesting feature for somebody into language design, but the average Joe working in a lab is not going to learn a completely new language and rewrite all his Matlab code because of it. Most probably, he has not idea what it is or why he would want it. It was an example of how, at this point, it seems like the web site is more directed towards language developers than potential users.
- elcritch 11y ago
  Actually, I think the main page is directed toward those scientific users who create their own custom projects and/or libraries. This also goes back to your earlier point in that early in a language evolution you need more library and package creators so you can have a broad ecosystem for the more day to day programmers. One example of this need, is the creator of the fftw library (a cornerstone fft implementation in C) wrote several popular packages for Julia. I think there's a talk he gave at the 2014 JuliaCon. In this regard, multiple dispatch is actually a huge selling point! I've written in Fortran 90 code, C, Python, and enjoyed most of those languages. There is something unique about being able to pull up the source code for almost every operator/function in the language, implemented in that language. Fortran has this, but is much more statically oriented and difficult for quick scripting. Python, well I'm hopeful pypy keeps building momentum. Or perhaps Pyrhon ported to web assembly, in more pure Python.