burrito
crates.io
Our great sponsors
burrito | crates.io | |
---|---|---|
11 | 661 | |
816 | 2,796 | |
3.4% | 2.1% | |
8.1 | 10.0 | |
13 days ago | 5 days ago | |
C | Rust | |
MIT License | Apache License 2.0 |
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.
burrito
- Why are Apple Silicon VMs so different?
- Show HN: Burrito v1.0.0 β Wrap Elixir Apps into Standalone Binaries
-
Elixir at Ramp
Most of the BEAM isn't well-suited for trends in today's immutable architecture world (Docker deploys on something like Kubernetes or ECS). Bootup time on the VM can be long compared to running a Go or OCaml binary, or some Python applications (I find larger Python apps tend to spend a ton of time loading modules). Compile times aren't as fast as Go, so if a fresh deploy requires downloading modules and compile-from-scratch, that'll be longer than other stacks. Now, if you use stateful deploys and hot-code reloading, it's not so bad, but incorporating that involves a bit more risk and specific expertise that most companies don't want to roll into. Basically, the opposite of this article https://ferd.ca/a-pipeline-made-of-airbags.html
Macros are neat but they can really mess up your compile times, and they don't compose well (e.g. ExConstructor and typed_struct and Ecto Schemas all operate on Elixir Structs, but you can't use all three)
If your problem is CPU-bound, there are much better choices: C++, Rust, C. Python has a million libraries that use great FFI so you'll be fine using that too. Ditto memory-bound: there are better languages for this.
This is also not borne from direct experience, but: my understanding is the JVM has a lot more knobs to tune GC. The BEAM GC is IMO amazing, and did the right thing from the beginning to prevent stop-the-world pauses, but if you care about other metrics (good list in this article https://blog.plan99.net/modern-garbage-collection-911ef4f8bd...) you're probably better off with a JVM language.
While the BEAM is great at distribution, "distributed Erlang" (using the VM's features instead of what most companies do, and ad-hoc it with containers and infra) makes assumptions that you can't break, like default k-clustering (one node must be connected to all other nodes). This means you can distribute to some number of nodes, but it's hard to use Distributed Erlang for hundreds or thousands of nodes.
Deployment can be mixed, depending on what you want. BEAM Releases are nice but the lack some of the niceness of direct binaries. Libraries can work around this (like Burrito https://github.com/burrito-elixir/burrito).
If you like static types, Dialyzer is the worst of the "bolted-on" type checkers. mypy/pyright/pyre, Sorbet, Typescript are all way better, since Dialyzer only does "success typing," and gives way worse messages.
[1]: https://morepablo.com/2023/05/where-have-all-the-hackers-gone.html
-
Building Apps with Tauri and Elixir
The answer was given by the Elixir community with burrito which enables users to pack up everything an Elixir application needs within a binary namely Zig Archiver to package the binary and Zig Wrapper that wraps the Erlang Virtual Machine to be used in multiple platforms (Zig + Rust in the same project π€―).
- Burrito: Cross-Platform Elixir Deployments
-
Is Elixir a good fit for a hobbyist? (Homelab automation/Content Backlog Management)
Might be worth looking into burrito for that use case?
-
Which language to choose ?
Elixir is extremely practical for building systems, I know some sysadmin/devops that write their tools in it - which is maybe a bit of a leap for most. It has better support for cli stuff these days but it's not it's strong suit - you can create single-bin packages with stuff like https://github.com/burrito-elixir/burrito or regular "mix releases". (LiveView is very sexy.) It's not statically typed. There is some experimental skunkworks project to add typing to it but probably wont see any public preview until mid/late next year as I understand it.
-
Sell me on Elixir
I would consider 1 to be the major blocker but Burrito has addressed many of the concerns here, including cross-compilation. The only downside of Burrito is that the first boot has to unpack the runtime (which is sub-second in my experience).
-
FireZone β Tailscale Alternative β The Open Source VPN Server and Firewall
Sure! Elixir's been great. Phoenix is a joy to work with, and many of the concurrency primitives built into OTP make it the perfect foundation for a product like this. And rustler makes it super easy to add low-level / native code.
I will say the big downside to using Elixir is that distributing releases is a bit cumbersome. `mix release` expects that you're building on the same OS / version as you'll be running on, though we're looking into using something like burrito [1] aim to alleviate this.
[1] https://github.com/burrito-elixir/burrito
-
Zig monthly, October 2021: Games, gamedev, Elixir, tools and more
I was intrigued so I went to hunt for the Burrito repo [1].
I thought it was some sort of Erlang native compiler written in Zig (which sounds like an incredible pain in the ass), but it's really "just" a cross-platform installer. Still useful !
[1]: https://github.com/burrito-elixir/burrito/issues?q=is%3Aissu...
crates.io
-
Rust Keyword Extraction: Creating the YAKE! algorithm from scratch
All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.
-
Migrating a JavaScript frontend to Leptos, a Rust framework
So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. Thereβs a good chance the crates you need are available in Rust's crates.io repository.
-
Learning Rust: A clean start
The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.
-
#2 Rust - Cargo Package Manager
Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.
-
Rust π¦ Installation + Hello World
Before proceeding, let's check https://crates.io/, the official Rust package registry.
-
Underestimating rust for my Project.
The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.
-
Top 10 Rusty Repositories for you to start your Open Source Journey
5. Crates.io
-
Project Structure Clarification Coming From Python - With Example
When using crates from eg. crates.io, and also things like std and core
-
Cargo has never frustrated me like npm or pip has. Does Cargo ever get frustrating? Does anyone ever find themselves in dependency hell?
Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.
-
How did I need to know about feature rwh_05 for winit?
So this is my question: Which way was the right to find it out? There is no info about this feature on crates.io. I also have no clue what exactly it does and why it is named rwh_05.
What are some alternatives?
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
docs.rs - crates.io documentation generator
ex_tauri - Utility to build Phoenix Desktop applications using web views from Tauri
plotters - A rust drawing library for high quality data plotting for both WASM and native, statically and realtimely π¦ ππ
sendgrid-v3 - Haskell Sendgrid v3 API Library
Cargo - The Rust package manager
Rustler - Safe Rust bridge for creating Erlang NIF functions
trunk - Build, bundle & ship your Rust WASM application to the web.
babashka - Native, fast starting Clojure interpreter for scripting
gtk4-rs - Rust bindings of GTK 4
capacitor - Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web β‘οΈ
Rocket - A web framework for Rust.