@yth I've used #Java to create CLI "tools" for genetics research. Though we think of them more often as methods. Java fit the time and space complexities I was dealing with, and I really enjoyed writing multi-threaded code with its mature API (on this front I'd love to try out the more modern structured concurrency and virtual threads provided in Project Loom). I used the picocli library for command-line stuff. All this said, I could see myself writing CLI methods using #Julia as well.

@yth I've used #Java to create CLI "tools" for genetics research. Though we think of them more often as methods. Java fit the time and space complexities I was dealing with, and I really enjoyed writing multi-threaded code with its mature API (on this front I'd love to try out the more modern structured concurrency and virtual threads provided in Project Loom). I used the picocli library for command-line stuff. All this said, I could see myself writing CLI methods using #Julia as well.

The #ocaml debacle with the ginormous slop #AI / #LLM "contributions" continues! It's round two, already! Oh no. With the same outcome, predictably. This time in the #julia community.

https://discourse.julialang.org/t/ai-generated-enhancements-and-examples-for-staticcompiler-jl/134054/18

The patience of the Julia people is absolutely immense here! I've huge respect for them after reading this (and the Ocaml people, only days ago).

The fundamental issue seems to be that the guy attempting this novel approach to software development thinks the AI "understands" what it's doing. So even if showstopping nonsense in the AI-produced code is pointed out to him, he comes back with - oh well, yeah, the AI gets "lazy", or some other sort of narrative that rationalises the slop, and presumes the "AI" is, by definition, really understanding what's going on, and smart, and capable, and all that.

Will there be no end to this nonsense? Each week the patience of a new set of #FOSS maintainers will be tested? It's Groundhog Day, but with all the quirkiness and charm removed?

The #ocaml debacle with the ginormous slop #AI / #LLM "contributions" continues! It's round two, already! Oh no. With the same outcome, predictably. This time in the #julia community.

https://discourse.julialang.org/t/ai-generated-enhancements-and-examples-for-staticcompiler-jl/134054/18

The patience of the Julia people is absolutely immense here! I've huge respect for them after reading this (and the Ocaml people, only days ago).

The fundamental issue seems to be that the guy attempting this novel approach to software development thinks the AI "understands" what it's doing. So even if showstopping nonsense in the AI-produced code is pointed out to him, he comes back with - oh well, yeah, the AI gets "lazy", or some other sort of narrative that rationalises the slop, and presumes the "AI" is, by definition, really understanding what's going on, and smart, and capable, and all that.

Will there be no end to this nonsense? Each week the patience of a new set of #FOSS maintainers will be tested? It's Groundhog Day, but with all the quirkiness and charm removed?

Lenses in Julia

https://juliaobjects.github.io/Accessors.jl/stable/lenses/

#HackerNews #Lenses #Julia #Accessors #FunctionalProgramming #DataStructures

Looking for #Nix X #Julia enjoyers to review this PR

https://github.com/NixOS/nixpkgs/pull/433332

(posted already on discourse)