dd-trace-rb
package-ruby
| dd-trace-rb | package-ruby | |
|---|---|---|
| 4 | 1 | |
| 290 | 2 | |
| 0.3% | - | |
| 10.0 | 10.0 | |
| 1 day ago | over 8 years ago | |
| Ruby | Ruby | |
| 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.
dd-trace-rb
-
The end of "Useless Ruby sugar": On intuitions and evolutions
Thing is, once you have 1) and 2), the added complexity of bringing in, integrating, and writing for a different tool to achieve 3) begins to make little sense, when you can just go along and do it just as well in rspec anyway... It's a matter of balance and heavily depends on the project.
> if you're still at Datadog
As a matter of fact I am. Feel free to shoot me an email.
curl -s https://github.com/DataDog/dd-trace-rb/commit/176c642ca73679cabc5fa1a113bc9b600aa04dcd.patch | grep '^From:' -
A few words on Ruby's type annotations state
> For myself, I'm fine with the typing being in a separate .rbs file
We type[0] by having one separate .rbs file per .rb file. Works really well with an editor's vertical splits: type outline on one side, code on the other. That, or use something like vim-projectionist[1].
[0]: (WIP: there's a huge codebase to type, but we're progressively getting there) https://github.com/DataDog/dd-trace-rb/tree/master/sig
[1]: https://github.com/tpope/vim-projectionist
-
Why Authorization Is Hard
Thanks! I'll pass it on to the team :D
I've got to say, the folks at Intercom made it particularly fun. They were sending us traces and graphs from their internal systems when we trying to figure out some issues with them (e.g. we ran into this datadog context problem: https://github.com/DataDog/dd-trace-rb/issues/1389)
package-ruby
-
The end of "Useless Ruby sugar": On intuitions and evolutions
It mostly comes from the intentional design of open classes, thus the namespace organisation is fundamentally decoupled from the filesystem: any Ruby file has to be able to contain any class/module, otherwise one can't add to an open class/module†!
There are a bunch of issues about this upstream about this, e.g: https://bugs.ruby-lang.org/issues/14982
My take on it: https://github.com/lloeki/package-ruby
† ... via `class` and `module` keywords, as one could always include/extend/prepend or use `module_eval`/`class_eval`/`instance_eval`.
What are some alternatives?
cerbos - Cerbos is the open core, language-agnostic, scalable authorization solution that makes user permissions and authorization simple to implement and manage by writing context-aware access control policies for your application resources.
ffi - Ruby FFI
Ory Keto - Open Source (Go) implementation of "Zanzibar: Google's Consistent, Global Authorization System". Ships gRPC, REST APIs, newSQL, and an easy and granular permission language. Supports ACL, RBAC, and other access models.
casbin-server - Casbin as a Service (CaaS)
Rails Performance - Monitor performance of you Rails applications (self-hosted and free)
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
sorbet - A fast, powerful type checker designed for Ruby
contracts.ruby - Contracts for Ruby.
vim-projectionist - projectionist.vim: Granular project configuration
oso - Oso is a batteries-included framework for building authorization in your application.