4 ms·

Being complicated and needing to care about the complications are different. For example, I use Julia as a fast, pseudo-Matlab desk calculator and haven't bothe

Being complicated and needing to care about the complications are different. For example, I use Julia as a fast, pseudo-Matlab desk calculator and haven't bothered to read about the type system [1] (I think I read a "so you're coming from Matlab" style cheat sheet). Maybe someday, but until then it sorta just works as you would expect. [1]: The other day I did spend some time figuring out how to do Pkg.add("SQLite").

rdtsc 9y ago
> Being complicated and needing to care about the complications are different. I used to think that but changed my mind when it comes to programming languages. Mainly because once complexity is there, unless it's just a single developer or very tightly controlled / peer reviewed development practice, different contributors will use various subsets of features of the language and so you still have to know all the complex edge cases because you might have to read code. And arguably code is read more than written.
- oconnore 9y ago
  Maybe I'll run into that, but like I just went digging into some packages to see if I could get myself lost, and instead I learned that Julia can work on raw pointers, and found a cool raytracer that seems pretty readable in the CSG package: https://github.com/JuliaDB/PostgreSQL.jl/blob/master/src/dbi_impl.jl#L160 https://github.com/JuliaDB/PostgreSQL.jl/blob/master/src/dbi... https://github.com/jtramm/ConstructiveSolidGeometry.jl/blob/master/src/ConstructiveSolidGeometry.jl#L317 https://github.com/jtramm/ConstructiveSolidGeometry.jl/blob/...