There are different styles and levels of writing code in every language. There's highly abstract C++ and there's low-level pointer-chasing C++ that's basically C. Even in C there's the void*-style of programming which is effectively dynamically typed without the safety. Given this fact, I'm not sure what solving the two language problem would look like from the perspective this post is posing. Enforcing only one style of programming sounds like a problem to me, not a solution. On the contrary, I think one of Julia's greatest strengths is its ability to accommodate a very broad range of programming styles and levels.
On Sun, Oct 18, 2015 at 7:14 PM, Kristoffer Carlsson <[email protected]> wrote: > >> 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. >> >> > What is it with Julia that requires you to write in two completely > different styles? If what you are saying is that you can't just copy paste > code from Matlab and get 10x speed up then that is not really fair. > > For all the codes I am writing, sticking to good idiomatic julia code, it > is very rarely needed to rewrite large portions of the good for > performance. Tweaking some stuff in hot loops maybe but not starting from > scratch. >
