BinaryBuilder.jl
WSL
BinaryBuilder.jl | WSL | |
---|---|---|
5 | 406 | |
379 | 16,676 | |
1.1% | 0.7% | |
6.5 | 8.6 | |
9 days ago | 4 days ago | |
Julia | PowerShell | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
BinaryBuilder.jl
-
Is Julia suitable today as a scripting language?
There are some efforts and the startup times are getting better with every release and there's BinaryBuilder.jl.
-
Because cross-compiling binaries for Windows is easier than building natively
There is the Julia package https://github.com/JuliaPackaging/BinaryBuilder.jl which creates an environment that fakes being another, but with the correct compilers and SDKs . It's used to build all the binary dependencies
-
Discussion Thread
https://binarybuilder.org/. You can do it manually obviously, but this is easier.
-
PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)
> The main pain point is probably the lack of standard, multi-environment packaging solutions for natively compiled code.
Are you talking about something like BinaryBuilder.jl[1], which provides native binaries as julia-callable wrappers?
--
[1] https://binarybuilder.org
-
What to do about GPU packages on PyPI?
Julia did that for binary dependencies for a few years, with adapters for several linux platforms, homebrew, and for cross-compiled RPMs for Windows. It worked, to a degree -- less well on Windows -- but the combinatorial complexity led to many hiccups and significant maintenance effort. Each Julia package had to account for the peculiarities of each dependency across a range of dependency versions and packaging practices (linkage policies, bundling policies, naming variations, distro versions) -- and this is easier in Julia than in (C)Python because shared libraries are accessed via locally-JIT'd FFI, so there is no need to eg compile extensions for 4 different CPython ABIs (Julia also has syntactic macros which can be helpful here).
To provide a better experience for both package authors and users, as well as reducing the maintenance burden, the community has developed and migrated to a unified system called BinaryBuilder (https://binarybuilder.org) over the past 2-3 years. BinaryBuilder allows targeting all supported platforms with a single build script and also "audits" build products for common compatibility and linkage snafus (similar to some of the conda-build tooling and auditwheel). There was a nice talk at AlpineConf recently (https://alpinelinux.org/conf/) covering some of this history and detailing BinaryBuilder, although I'm not sure how to link into the video.
All that to say: it can work to an extent, but it has been tried various times before. The fact that conda and manylinux don't use system packages was not borne out of inexperience, either. The idea of "make binaries a distro packager's problem" sounds like a simplifying step, but that doesn't necessarily work out.
WSL
-
GoboLinux
It absolutely 100% can be true.
As an example: Windows Services for Linux 2 used a special init daemon to interact with the host OS.
That meant no systemd. That meant that the `systemctl` program wasn't there.
This baffled legions, armies, of wannabe sysadmins.
https://stackoverflow.com/questions/55579342/why-systemd-is-...
https://superuser.com/questions/1785697/systemd-in-wsl-on-wi...
https://github.com/microsoft/WSL/issues/9477
https://askubuntu.com/questions/1132230/unable-to-run-any-sy...
People on the whole have no idea how this stuff works, and they just copy magic incantations from StackOverflow to get stuff to happen. If that doesn't work, then this OS is broken. The end.
For these guys, WSL was broken.
Result:
MS hired Lennart Poettering.
https://www.theregister.com/2022/07/07/lennart_poettering_re...
He "fixed" it. Systemd now works in WSL2. All those guides for noobs now work. Everyone is happy.
In a world where tools like Flatpak and Snap are proliferating and it's driving deep divisions between Linux distros, if you think the average person struggling with Linux is going to use `ldd` to work out where the dependencies for something live, I'm afraid you are a deep guru who lives on a different plane of existence.
We now have widely-used packaging systems which simply embed an apps entire dependency tree into a package to avoid people having to work out the difference between `apt` and `rpm`. Thousands of terabytes of disk are being burned to make this stuff go away.
Yes, this is too hard. Way too hard.
-
Why Linux utilities tend to run poorly on Windows
Better source: https://github.com/Microsoft/WSL/issues/873#issuecomment-425...
- Weird graphical glitch/problem in Ubuntu WSLg (OpenGL)
-
RamRamRamEveryoneSleepingOnDocker
One of the bugs where on the Docker side. As I have said, there have been several since release with a lot of impact period overlap. The latest and greatest is not resolved.
-
Laravel dev in Windows - Laragon vs Docker?
It's the issue of abysmal I/O performance in communication between the mounted WSL2 virtual hard disk and Windows mounts inside the WSL2 distro.
- WSL freeze seems fixed in 2.0.12
-
What's the right way to open files in the system's default program from Ubuntu 22.04 in WSL 2 please?
I found this github page and I was able to reproduce this from the answer
-
Ask HN: Best Docker open source alternative?
* Docker engine and not Docker Desktop in a VM. WSL2 works well after some configuration: https://github.com/microsoft/WSL/issues/6655#issuecomment-11...
-
Broadcom to Cut Almost 1,300 VMware Jobs in California After Takeover
Seems to more of a Defender issue than a WSL one, see https://github.com/microsoft/WSL/issues/8995
After adding exclusions for the fsnotifier-wsl process and and both variants of the WSL distro path my disk performance was improved.
Adding the idea64.exe process also helped since I was trying to run IntelliJ against projects inside WSL.
- Bricked WSL 2 after 2.0.9 / Windows 10
What are some alternatives?
functorch - functorch is JAX-like composable function transforms for PyTorch.
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
Yggdrasil - Collection of builder repositories for BinaryBuilder.jl
genie - A quick way into a systemd "bottle" for WSL
HTTP.jl - HTTP for Julia
Scoop - A command-line installer for Windows.
dh-virtualenv - Python virtualenvs in Debian packages
Single-GPU-Passthrough
RDKit - The official sources for the RDKit library
setup-msys2 - GitHub Action to setup MSYS2
StarWarsArrays.jl - Arrays indexed as the order of Star Wars movies
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.