Live data from Hacker News

Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

sinews.siam.org

201–210 of 249 posts

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#201
post #50

Julia is interesting, but the block syntax is a little off-putting. I'm not sure why someone would design a language that uses 'end' to delineate a block. Curly brackets make sense. Tabs make sense. But 'end'? All it does is make code harder to read and harder to write.

Because Pascal. And as Pascal was used as a teaching language, I don't think your 'make code harder to read and harder to write' argument holds. But certainly nowadays 'end's are not seen often; maybe this has an influence in your statement?

Why do you think that "end" is superior to more lightweight syntax? One might argue that using "end" doesn't really matter, but I am extremely skeptical one could argue it is superior to a curly bracket or a tab in any way at all.

PS: And in regards to your last statement, maybe "end"s aren't seen very much anymore is because language designers' agree with me, not that somehow my opinion is influenced by the syntax of modern languages.

If you just think about it, that is much more likely than what you are proposing.

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#202
post #57

The authors claim Julia is a general programming language, but after a few tries I am not totally sure about that. Yes, it's a nice programming language for scientific computing but I am afraid its usefulness stops there. Matlab is (was?) the default tool for computational science, and Julia borrows lots from it. I'd say it's safe to put Julia in the same category with Matlab and Mathematica

What about the Julia 1.0 language design do you find prevents general purpose programming?

I think he's just trolling...

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#203

The authors claim Julia is a general programming language, but after a few tries I am not totally sure about that. Yes, it's a nice programming language for scientific computing but I am afraid its usefulness stops there. Matlab is (was?) the default tool for computational science, and Julia borrows lots from it. I'd say it's safe to put Julia in the same category with Matlab and Mathematica

Conceivably you can see a backen server being built in Julia e.g. https://github.com/JuliaWeb/Mux.jl

But I can't imagine anyone would choose Matlab or Mathematica to build a backend...

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#204

I'll say only one thing: 1 based indexing. Jokes asides, congratulations to Jeff Bezanson, Stefan Karpinski, and Viral B. Shah, well deserved!

Oh well, can't let this pass...

Introducing TwoBasedIndexing.jl (https://github.com/simonster/TwoBasedIndexing.jl)

The point is, n-based indexing isn't really that big a deal.

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#205
post #200

Earlier quoted context omitted.

Ruby and Elixir both made the same decision, and I don't feel like it's had an actual negative impact, for me at least; I've found both languages to be delightfully readable. I haven't dabbled very much in Julia since the pre-1.0 days, but I don't recall it being any more or less jarring. I suppose it could indeed be jarring if you're not already used to languages which use 'end' to terminate blocks, but after awhile…

I mean, maybe it's not a big deal. But what value does it add? What if we had a 50 character string of random digits be the terminating identifier for a block? What about 100 characters? What about 200? Syntax shouldn't create visual noise, it should be as lightweight as possible. Maybe someone can justify why a 3 character word (end) doesn't really matter. But can someone give an argument on how it adds value versus…

it's easier to read.

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#206

Earlier quoted context omitted.

The target of julia is computional sciences. Sure for a web apps you don't care if your language is 30x slower, 1ms or 30us who cares, you can just rely on the raw speed of your overpowered computer and enjoy your favorite language. But when it's between waiting 1 day or 1 month for your results you start caring quite a lot

Sometimes the wait isn't the computational time wait, but the developer time wait, too.

Truth. See http://www.stochasticlifestyle.com/the-nonlinear-effect-of-c...

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#207
post #200

Earlier quoted context omitted.

I mean, maybe it's not a big deal. But what value does it add? What if we had a 50 character string of random digits be the terminating identifier for a block? What about 100 characters? What about 200? Syntax shouldn't create visual noise, it should be as lightweight as possible. Maybe someone can justify why a 3 character word (end) doesn't really matter. But can someone give an argument on how it adds value versus…

it's easier to read.

If every sentence ended in an "end" instead of a period, would you posit that that would be easier to read as well?

The crux of the issue is the signal to noise ratio. The more noise there is (syntax), the more difficult it is to pick up the signal (the semantics).

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#208
post #207

Earlier quoted context omitted.

it's easier to read.

If every sentence ended in an "end" instead of a period, would you posit that that would be easier to read as well? The crux of the issue is the signal to noise ratio. The more noise there is (syntax), the more difficult it is to pick up the signal (the semantics).

Sentence is not code! According to your logic, when do you see {} in prose?

begin some code some more code end

It's easier to read.

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#209
post #166

I'm ready to burn a part of my karma to say the following : - Naming a PL "Julia" is sexist and creepy - The language doesn't add any substantial value to PL theory or programming methodology compared to say, Python - The future of computer-human interaction is not in programming. Python will be good enough until we reach that point where we can use neural networks/AI to do most of the business tasks.

> Naming a PL "Julia" is sexist and creepy How? (I kind of assume that a big reason computer scientists would pull out that name without a specific referent in mind is the influence of the Julia set, named for Gaston Julia.) > The language doesn't add any substantial value to PL theory or programming methodology compared to say, Python Maybe; not all practical benefits in programming come from advances in methodology…

I also thought it was related to Gaston Julia or his sets, but apparently not: it was just chosen since it sounds nice (https://www.infoworld.com/article/2616709/application-develo...)

Re: Julia Language Co-Creators Win James H. Wilkinson Prize for Numerical Software

#210

Earlier quoted context omitted.

>> CPython is 100 to 1000 times slower than C > That's very context dependant. With annotations, typical calculations compile to C code roughly equivalent to native. The more of the actual runtime you use, the more you call into cpython which can't be sped up this way. Cython compiled code will be somewhere between C and cpython in terms of speed, but putting a single number to it will be always misleading. OP said "…

Oops, you're right. One day I'll learn to read :-)

No worries. I suspect many of your downvoters were confused as I was that you appeared to be arguing that CPython could compile your Python code to efficient C! Took me a few passes to spot the misunderstanding.
Post reply on HN