Explore >> Select a destination
|
You are here 
|
blog.presidentbeef.com | ||
| | | | |
andre.arko.net
|
|
| | | | | For the last ten years or so of working on Bundler, I've had a wish rattling around: I want a better dependency manager. It doesn't just manage your gems, it manages your ruby versions, too. It doesn't just manage your ruby versions, it installs pre-compiled rubies so you don't have to wait for ruby to compile from source every time. And more than all of that, it makes it completely trivial to run any script or tool written in ruby, even if that script or tool needs a different ruby than your application does. | |
| | | | |
yehudakatz.com
|
|
| | | | | TL;DR Although apps and gems look like they share the concept of "dependency", there are some important differences between them. Gems depend on a name and version range, and intentionally don't care about where exactly the dependencies come from. Apps have more controlled deployments, and need a guarantee that | |
| | | | |
ankane.org
|
|
| | | | | I've created a few Ruby gems over the years, and there are a number of patterns I've found myself repeating that I wanted to share. I didn't invent... | |
| | | | |
github.com
|
|
| | | A terminal-based text editor written in Rust. Contribute to gchp/iota development by creating an account on GitHub. | ||
