4 ms·
Same, and they're not. If anything, programming for academia is more of a mess than web development. Case in point - I spent the better part of a day rewriting
by zhdc1 6y ago
Same, and they're not.
If anything, programming for academia is more of a mess than web development. Case in point - I spent the better part of a day rewriting what's essentially a parallelized for loop because the library I'm using in Julia to open HDF5 files has a well known memory leak. I have the impression that something similar in any popular web dev framework or library would have been ruthlessly purged a long time ago.
- mattkrause 6y agoBugs in libraries and code that overpromises are maddening (and too common), but I think it's different. You can get the data out of an HDF5 file with using HDF5 c = h5open(filename, "r") do file read(file, "data") end And you're done. You're not somehow locked into plotting data with the Plotly backend, but not GR. You know exactly where the data came and can trivially point it somewhere else with some 'magic' breaking.
- zhdc1 6y agoHDF5.jl suffers from a memory leak when HDF5 files are opened in succession. Bug report: https://github.com/JuliaIO/HDF5.jl/issues/349 https://github.com/JuliaIO/HDF5.jl/issues/349
- mattkrause 6y agoRight, but that's a bug. It's annoying it isn't fixed and working around it is undoubtedly annoying. This seems different from a system where there's lots of complexity in just choosing what frameworks to start with and if/how they play well together, and all of that rapidly changing over time. (I'd bet, for example, that many of those examples used to work).