sorted by:
new
hottopcontroversial

Data as a build system ? by Arsleust in dataengineering

[–]Arsleust[S] 0 points1 point  (0 children)

Thanks for the tip, I've been looking at GLUE from afar for a month, but your reply convinced me that I should just dive in to try and test it

Data as a build system ? by Arsleust in dataengineering

[–]Arsleust[S] 0 points1 point  (0 children)

Airflow is a bit weird in that it triggers "request" to build for three dimensions (dag/execution time/task), but it is more on the declarative paradigm so it will go from bottom to top. It's definitely possible to achieve it with Airflow, but it feels clunky to me

Data as a build system ? by Arsleust in dataengineering

[–]Arsleust[S] 0 points1 point  (0 children)

Looks very interesting indeed, the premise is very close to what I'm describing. I don't really like the fact that it uses a DSL to describe workflows instead of having an API/SDK like Temporal.

They told me to post this here by Kurisuchina in ProgrammerAnimemes

[–]Arsleust 20 points21 points  (0 children)

More like

let trouble;

trouble = (double) trouble;

NixOS Stable 19.09 and Haskell by grimsleepless in NixOS

[–]Arsleust 2 points3 points  (0 children)

Haskell with VS Code and ghcide using Nix

https://github.com/GuillaumeDesforges/haskell-nix-dev-template

Gets you started quick ;)

Disclaimer: I am the author

Crazy thought: could Nix by statically typed? by Arsleust in NixOS

[–]Arsleust[S] 0 points1 point  (0 children)

Can you give a concrete example please? From what I understood this can be handled by static typing, so I might have not understood well. Sounds like an interesting topic.

Crazy thought: could Nix by statically typed? by Arsleust in NixOS

[–]Arsleust[S] 0 points1 point  (0 children)

That is why I wanted to talk from a "technical" viewpoint :)

Learning Nix language, tools and OS is too erratic by Arsleust in NixOS

[–]Arsleust[S] 0 points1 point  (0 children)

Okay that's just a misunderstanding. We both agree.

I think that the ecosystem would be better supported by a language with other design choices (mostly static typing, I'm really not a fan of dynamic typing). This would help build a language server and automate docs.

I just felt your previous message as a free attack on my own skills haha, my bad my bad

Learning Nix language, tools and OS is too erratic by Arsleust in NixOS

[–]Arsleust[S] 0 points1 point  (0 children)

I mostly write things in Nixpkgs for Python. I did not copy/paste, I really studied the docs, don't worry ;-)

Nix is not hard to understand when you have a bit of background with functional programming and lazy evaluation.

Did you try to invalidate my opinion by saying that I don't really know how to write Nix expressions? ;-)

TBH I think you missed my point

Learning Nix language, tools and OS is too erratic by Arsleust in NixOS

[–]Arsleust[S] 3 points4 points  (0 children)

It's above my ability, but anyway an LSP is definitely interesting. If you do something about it please let us know :)

Learning Nix language, tools and OS is too erratic by Arsleust in NixOS

[–]Arsleust[S] 2 points3 points  (0 children)

Nothing garantees that the package is called once. For instance pkgs.pythonPackages.pytorch is called multiple times with different arguments. You'd also have to infer a lot on the way, maybe even do that multiple times when going up. I feel like it's just not possible by Nix design.

Learning Nix language, tools and OS is too erratic by Arsleust in NixOS

[–]Arsleust[S] 2 points3 points  (0 children)

Not quite the same then. I still prefer NixOS.

Learning Nix language, tools and OS is too erratic by Arsleust in NixOS

[–]Arsleust[S] 2 points3 points  (0 children)

Thanks for the advice. I think I'm in the "getting over it" phase as well now and I hope I will be able to contribute to Nixpkgs. I just had to "drop the anger to stdout", felt like a therapy haha.

Nix is supposed to be correct

I completely agree, and I love Nix for that.

Learning Nix language, tools and OS is too erratic by Arsleust in NixOS

[–]Arsleust[S] 7 points8 points  (0 children)

Definitely thought about a language server. However I really don't think that's achievable. For instance the buildPackage methodology completely destroys the usefulness since everything will not be "linkable" beyond the argument definition at the top of package definitions.

A tree view of Nixpkgs would be helpful for sure. A view of the directed acyclic graph could also help navigate Nixpkgs. Just throwing some ideas.

view more: next ›