On Monday, October 19, 2015, Tamas Papp wrote:
>
> The "two language problem" is really about a discontinuity in the effort
> vs speed curve. You hit the limits of Language A, you have to go to
> Language B, which is significantly different. In Julia you can make a
> lot of incremental optimizatio
I agree with you in that most of the code I start out with usually
contains some dirty hacks that I later refactor. But that is just my
personal approach to programming -> get something running quickly and
iterate on it
That being said, based on my personal experience with Julia (which is
abo
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 writ
