Re:Giving up on Julia (2016)
by StefanKarpinski on Sunday August 18, 2019 @04:48PM
(#20732724)
That’s totally unrelated to startup or compilation time. It’s due to a bug in the crufty old Windows CMD.exe terminal—if you use a real terminal it doesn’t happen.
[ Parent
| on HN ]
I’m now actually curious - what’s the bug in cmd.exe and why doesn’t that happen with other REPLs? I’m well aware that cmd.exe has its fair share of weird bugs, but on Windows it’s sometimes the only thing available. Plus, every third party terminal basically has to interface with the Windows GUI command-line program via screen-scraping, and so they inherit many of the same bugs. (The Windows Console architecture is fascinating - see https://devblogs.microsoft.com/commandline/windows-command-l... for a rundown!)
Re:Giving up on Julia (2016)
by StefanKarpinski on Tuesday August 20, 2019 @10:01AM
(#20747120)
If we knew that it would be fixed by now. Julia's REPL only supports VT100 terminals and its descendants. My guess is that CMD.exe on older Windowses fails to emulate VT100 correctly somehow.
that doesnt explain why every other interpreted language ive ever used doesnt have this problem.
its a julia issue that the devs refuse to acknowledge or even test
Re:Giving up on Julia (2016)
by ChrisRackauckas on Wednesday August 21, 2019 @07:10PM
(#20762909)
Julia isn't interpreted. There is a package that implements an interpreter though and it doesn't have these issues.