If you are eager to be involved in some friendly FOSS community and would like to share some of your experience in a particular field where you see reproducibility and bootstrapability would improve the state of the art - don't be afraid and submit a request to be included in the one of many teams in Guix project!
Teams which will love to see for more participants #Java, #Go, #Perl, #Ruby, #Julia
https://guix.gnu.org/manual/devel/en/html_node/Teams.html
No commit access is required
If you are eager to be involved in some friendly FOSS community and would like to share some of your experience in a particular field where you see reproducibility and bootstrapability would improve the state of the art - don't be afraid and submit a request to be included in the one of many teams in Guix project!
Teams which will love to see for more participants #Java, #Go, #Perl, #Ruby, #Julia
https://guix.gnu.org/manual/devel/en/html_node/Teams.html
No commit access is required
The first data science book that has a chapter on monads https://reproducible-data-science.dev/
Learn how to build robust #DataScience pipelines with #RStats, #Python , #Julia and #Nix !
The first data science book that has a chapter on monads https://reproducible-data-science.dev/
Learn how to build robust #DataScience pipelines with #RStats, #Python , #Julia and #Nix !
@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.
I have been looking for a programming language for simple (cross platform) CLI tools for a long time. Professionally I use #Java, which I accept now as the safest choice for serious enterprise stuff. I have tried #Typescript but after a long stint I have decided to say goodbye to the Javacript ecosystem for anything but Frontend. Now on #Go and #Rust, leaning towards the latter. I won’t consider #Python (sorry). I could just use Java for everything. Anyone want to weigh in?
@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.
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.
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?
Looking for #Nix X #Julia enjoyers to review this PR
https://github.com/NixOS/nixpkgs/pull/433332
(posted already on discourse)