Fashion meets Ruby! Shop our fun Ruby-inspired apparel and accessories designed to celebrate the joy and diversity of the Ruby community. Learn more →
Scientist Alternatives
Similar projects and alternatives to Scientist
-
Rubocop
Discontinued A Ruby static code analyzer and formatter, based on the community Ruby style guide. [Moved to: https://github.com/rubocop/rubocop] (by rubocop-hq)
-
Coverband
Ruby production code coverage collection and reporting (line of code usage)
-
PopRuby
PopRuby: Clothing and Accessories for Ruby Developers. Fashion meets Ruby! Shop our fun Ruby-inspired apparel and accessories designed to celebrate the joy and diversity of the Ruby community.
-
SimpleCov
Code coverage for Ruby with a powerful configuration library and automatic merging of coverage across test suites
-
-
Traceroute
A Rake task gem that helps you find the unused routes and controller actions for your Rails 3+ app
-
Flog
Flog reports the most tortured code in an easy to read pain report. The higher the score, the more pain the code is in.
-
bundler-leak
Known-leaky gems verification for bundler: `bundle leak` to check your app and find leaky gems in your Gemfile :gem::droplet:
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Flay
Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored.
-
Laboratory
Achieving confident refactoring through experimentation with Python 2.7 & 3.3+
-
-
-
-
debezium
Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
-
-
Camunda BPM
Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.
-
opentelemetry-specification
Specifications for OpenTelemetry
-
opentelemetry-collector-contrib
Contrib repository for the OpenTelemetry Collector
-
zeebe
Discontinued Distributed Workflow Engine for Microservices Orchestration [Moved to: https://github.com/camunda/zeebe] (by camunda-cloud)
-
Scientist.net
A .NET library for carefully refactoring critical paths. It's a port of GitHub's Ruby Scientist library
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Scientist reviews and mentions
-
Crates that run multiple versions of a function and ensures the return value is the same?
For some google-fu, the ruby / .NET equivalent of this is https://github.com/github/scientist / https://github.com/scientistproject/Scientist.net
-
Scientist: A Ruby library for carefully refactoring critical paths
The readme (here https://github.com/github/scientist#alternatives) doesn't mention, but here is one for Rust: https://crates.io/crates/scientisto
-
Real-World Engineering Challenges: Migrations
Check out GitHub scientist if you are doing a migration with a ruby based system: https://github.com/github/scientist
Great support and functionality for testing differences between two systems of record.
-
Using Scientist to Refactor Critical Ruby on Rails Code
However, the good news is that it’s easy and safe to do so in Ruby and Rails using the Scientist gem. Scientist's name is based on the scientific method of conducting experiments to verify a given hypothesis. In this case, our hypothesis is that the new code does the job.
-
Book notes: Turn the Ship Around!
Github scientist.
-
How can I benchmark my application for Pagy vs Kaminari?
You could try using both gems and wrapping a few instances (or all) of your pagination logic in the scientist gem. I can't recall offhand if it has benchmarking built-in, but you could easily wrap your use and try blocks in benchmarking calls and compare that when you publish results.
-
A practical tracing journey with OpenTelemetry on Node.js
But there's an even better option: run both libraries in production for real-world requests, and see if there's a meaningful gain from undici. I learnt this approach from GitHub's Scientist. Sadly, this article is about tracing, not experimentation, so I won't continue down that path now, but I hope to write another article about it soon. My implementation would probably be to have a switch that randomly picks one of the two libraries for each request. Then I'll compare the metrics and see which performs better over time.
- Suture: A Ruby gem that helps you refactor your legacy code
-
A note from our sponsor - PopRuby
popruby.com | 28 Mar 2024
Stats
github/scientist is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of Scientist is Ruby.