Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
droelf
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
droelf
2y ago
We're working on rattler-build ( https://github.com/prefix-dev/rattler-build/ ) - which is a build system inspired by Apko / conda-build and uses YAML files to statically define dependencies. It works real
32.
▲
by
droelf
2y ago
There is also Dora-RS which looks quite interesting - but I agree, improving ROS would be even better! https://dora-rs.ai/
33.
▲
WASM and Conda: Revolutionizing Scientific Computing in the Browser
(prefix.dev)
5 points
by
droelf
2y ago
|
0 comments
34.
▲
by
droelf
2y ago
There are definitely some similarities, but pixi is explicitly not "Python-only". We support many more package ecosystems (thanks to Conda being language agnostic). This includes, for example, R, C/C++ compilers, Rust, Go ...
35.
▲
by
droelf
2y ago
That is a valid criticism. Although I personally have seen Spack come up mostly in HPC workloads which is a bit more specialized. There are many disciplines that might not need the "full power" of something like Spack (e.g. source
36.
▲
Pixi – rust-based package manager for reproducible scientific workflows
(prefix.dev)
24 points
by
droelf
2y ago
|
5 comments
37.
▲
Pixi-pdf – make research PDFs reproducible and "executable"
(twitter.com)
5 points
by
droelf
2y ago
|
0 comments
38.
▲
by
droelf
2y ago
Hi everyone, author here. If someone has questions, do let me know! We really care about open science and reproducibilty.
39.
▲
by
droelf
2y ago
Resolvo (the SAT solver here) has been really good for us. It helped make some conda-forge bots up to 10x faster than the previous C-based solver (libsolv) while being memory safe. The specific bot tests went from taking 60 minutes to ~6 mi
40.
▲
50x faster conda environment solving with "sharded" repodata
(prefix.dev)
5 points
by
droelf
2y ago
|
0 comments
41.
▲
by
droelf
3y ago
Weird that it doesn't go into LFortran more, they even have an excellent online and mindblowing WASM example. https://dev.lfortran.org/
42.
▲
Reasons to Switch from Conda to Pixi
(prefix.dev)
4 points
by
droelf
3y ago
|
0 comments
43.
▲
Adopting `uv` into `pixi` for a fast conda and pip experience
(prefix.dev)
11 points
by
droelf
3y ago
|
2 comments
44.
▲
Py-rattler, Rust based Python library to create conda environments fast
(prefix.dev)
7 points
by
droelf
3y ago
|
0 comments
45.
▲
by
droelf
3y ago
rip isn't really planned as a tool that you would install on your computer. It's a low-level library.
46.
▲
by
droelf
3y ago
No plans but we would be happy to explore this further if the poetry-devs want to. Maybe they'll join us at PackagingCon next week: https://packaging-con.org/
47.
▲
by
droelf
3y ago
We'll build some features sooner or later on the repository side that are going to be interesting for enterprise customers. But we have a strong and true commitment to open source. A non-open-source package manager would definitely not
48.
▲
by
droelf
3y ago
Yeah, rye uses a Python build from indiegreg while we use the Python builds from conda-forge (which is a community project with many maintainers). Conda-forge also produces packages for much more (nodejs, Qt, HDF5, C/C++ compilers, LLV
49.
▲
by
droelf
3y ago
Yeah, we're working on that and use a similar model like pnpm in pixi / rattler already. In fact, for a long time conda & mamba have created "hard-links" to a central package cache for the mentioned space savings.
50.
▲
by
droelf
3y ago
Yeah, I think it would be awesome to work on top of the same foundations (rip & resolvo being two of those, and konstin's, who works with Charlie at astral, pep440_rs and pep508_rs being two others). We'll have some more conve
51.
▲
by
droelf
3y ago
Our solver implements "state-of-the-art" CDCL (conflict driven clause learning). So there is a chance that the performance is improved over "resolvelib" which is used by pip. Once we are feature complete enough we will w
52.
▲
by
droelf
3y ago
It doesn't work well for those yet. rip only deals with wheel files for now. The way (afaik) pip works for source dist packages is that it locally builds the wheel, and then extracts the metadata from that locally built wheel. This is
53.
▲
by
droelf
3y ago
yep, that's it!
54.
▲
by
droelf
3y ago
Yeah, rattler are our low-level crates to handle conda packages (similar to how rip is a low-level crate to handle PyPI packages). Both build on top of resolvo (our SAT solver, based on MiniSAT and libsolv) and both are used (or going to be
55.
▲
by
droelf
3y ago
Blog post author here – happy to take any questions. We're looking to unify the conda + PyPI ecosystems and build a really nice cross-platform, language independent package manager (which is called pixi).
56.
▲
Rip – Rust crate to resolve and install Python packages
(prefix.dev)
135 points
by
droelf
3y ago
|
36 comments
57.
▲
The PackagingCon schedule is published
(cfp.packaging-con.org)
2 points
by
droelf
3y ago
|
0 comments
58.
▲
Pixi – solving dependency hell with Rust
(prefix.dev)
13 points
by
droelf
3y ago
|
0 comments
59.
▲
A new memory-safe SAT solver for package management in Rust (port of libsolv)
(prefix.dev)
9 points
by
droelf
3y ago
|
0 comments
60.
▲
PackagingCon – A conference only for software package management
(packaging-con.org)
189 points
by
droelf
3y ago
|
155 comments
More ›