Future of Ruby standard libraries will focus on gemification. Standard libraries will be extracted out of the Ruby core repository and maintained as default gems or bundled gems in GitHub repositories. This allows libraries to be updated independently of Ruby releases and more easily accept contributions. While this approach has benefits, it also has challenges around maintaining compatibility and complex dependencies. The process of gemification will be gradual to reduce the size of changes.
How to develop the Standard Libraries of Ruby?Hiroshi SHIBATA
I maintain the RubyGems, Bundler and the standard libraries of the Ruby language. So, I've been extract many of the standard libraries to default gems and GitHub at Ruby 3.0. But the some of libraries still remains in only Ruby repository. I will describe these situation.
How to develop the Standard Libraries of Ruby?Hiroshi SHIBATA
I maintain the RubyGems, Bundler and the standard libraries of the Ruby language. So, I've been extract many of the standard libraries to default gems and GitHub at Ruby 3.0. But the some of libraries still remains in only Ruby repository. I will describe these situation.
An overview of Ruby, jRuby, Rails, Torquebox, and PostgreSQL that was presented as a 3 hour class to other programmers at The Ironyard (http://theironyard.com) in Greenville, SC in July of 2013. The Rails specific sections are mostly code samples that were explained during the session so the real focus of the slides is Ruby, "the rails way" / workflow / differentiators and PostgreSQL.
This is the version of my Crate talk that was given at Scotland on Rails 2009.
This talk will cover the Crate project and how it may be used to package your web application. The end result is a statically built executable of the ruby interpreter and all dependent binary extensions. The application code, ruby stdlib the web framework itself, and all assets are packed into one or more SQLite databases.
Rspec and Capybara Intro Tutorial at RailsConf 2013Brian Sam-Bodden
Behavior-Driven Development and Acceptance Testing are heavily intertwined and in many aspects are one and the same. Both focus on starting at the outer layers of your application by concentrating on what matter to users; behavior. In this session/workshop we'll talk about how testing can be used both for specifying your application yet to be develop expected behavior and as accurate, running documentation that can be used to validate your stakeholder's acceptance criteria. We'll talk about the different types of testing and do a few hands-on exercises to flesh out a Rails application with RSpec and Capybara.
There are 900 Tickets currently in the Rails Lighthouse, some big, many small, and some relevant for Rails 3. Many of those issues could be fixed by people like us without too much effort.
Using online resources and a short demo we want do find out how to use the Rails Lighthouse, how to clone edge rails and how to run the test suites, and how one can create patches out of the fixes to make them available to the developers.
Cette conférence a pour but de vous faire (re)découvrir le framework web Ruby on Rails. En une heure, nous vous montrerons comment développer une application simple et la déployer sur Microsoft Azure. Nous nous ferons découvrir le dynamisme de la communauté Ruby.
Long journey of Ruby Standard library at RubyKaigi 2024Hiroshi SHIBATA
Ruby has a lot of standard libraries from Ruby 1.8. I promote them democratically with GitHub today via default and bundled gems. So, I'm working to extract them for Ruby 3.4 continuously and future versions. It's long journey for me.
After that, some versions may suddenly happen LoadError at require when running bundle exec or bin/rails, for example matrix or net-smtp. We need to learn what's difference default/bundled gems with standard libraries.
In this presentation, I will introduce what's the difficult to extract bundled gems from default gems and the details of the functionality that Ruby's require and bundle exec with default/bundled gems. You can learn how handle your issue about standard libraries.
Long journey of Ruby standard library at RubyConf AU 2024Hiroshi SHIBATA
I will introduce what's the difficult to extract bundled gems from default gems and the details of the functionality that Ruby's require and bundle exec with default/bundled gems. You can learn how handle your issue about standard libraries.
Deep dive into Ruby's require - RubyConf Taiwan 2023Hiroshi SHIBATA
Since Ruby's bundled and default gems change every year with each release, some versions may suddenly happen LoadError at require when running bundle exec or bin/rails, for example matrix or net-smtp.
In this presentation, I will introduce the details of the functionality that extends Ruby's require to provide guidance to users on what they can do to load them. And I will also show how $LOAD_PATH is build behind Ruby and Rails by Bundler.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
8. Packaging and Disribution(1)
• RAA(Ruby Application Archive)
• 2013/08: raa.ruby-lang.org 終了のご報告 https://www.ruby-lang.org/ja/news/
2013/08/08/rip-raa/
• RubyForge
• 2009/10: RubyForge To Be Phased Out, RubyGems.org Takes Over Gem Hosting
https://www.infoq.com/news/2009/10/rubyforge-phased-out-rubygemsorg
• gems.github.com
• 2009/10: Gem Building is Defunct https://www.infoq.com/news/2009/10/
github-stops-gem-building
9. Packaging and Disribution(2)
• gemcutter.org:
• https://github.com/rubygems/gemcutter
• You can use `gem yank` command after you did invoke `gem i gemcutter`.
• rubygems.org:
• gemcutter.org was renamed to rubygems.org.
• bundler:
• 2010: Released to 1.0.0 version.
10. A History of Ruby(Short Ver.)
• Ruby 1.8.7 bundled a lot of library named standard library a.k.a stdlib.
• Ruby 1.9.x bundled rubygems that is ruby library packaging and distributing.
• Many of libraries was born after that. Example for rspec, nokogiri, rake and thor. It’s
start time for Ruby language and library ecosystems.
• First Authors of famous library is burnout.
• Some of useful gems are changed maintainers of second generation.
• Ruby 2.4, 2.5
2013
2017
2009
2008
12. What’s Standard library?
• We called its “標準添付ライブラリ” in Japanese.
• It needs to `require` difference from embedded libraries like
String, Thread, etc.
• https://tech.pepabo.com/2017/09/11/rubykaigi-2017/
• It can be used without Bundler or RubyGems
13. Classification of standard libraries
Standard
Libraries
Default
Gems
Bundled
Gems
Pure Ruby 69 1 7
C extensions 23 5 0
This matrix shows number of standard libraries and their
classifications in Ruby 2.4.
14. What differences these libraries?
• Standard Libraries
• Upstream: Only Ruby core repository(svn.ruby-lang.org)
• Release cycle: 1 year
• Default Gems
• Upstream: Ruby core repository and GitHub
• Release cycle: 1year or maintainers matter
• Bundled Gems
• Upstream: Only GitHub
• Release cycle: Maintainers matter
15. What number of these libraries - 2.4.0 to 2.5.0
In Ruby 2.4
Standard Libraries
• Pure ruby: 69
• Extensions: 23
Default gems
• Pure ruby: 1
• Extensions: 5
Bundled Gems
• Pure ruby: 7
• Extensions: 0
In Ruby 2.5
Standard Libraries
• Pure ruby: 64 (-5)
• Extensions: 14 (-9)
Default gems
• Pure ruby: 6 (+5)
• Extensions: 14 (+9)
Bundled Gems
• Pure ruby: 7
• Extensions: 0
17. Inside default gems
• `tool/rbinstall.rb` put gemspec files for default gems on Ruby
core repository.
• We can release default gems to the rubygems.org. It’s a
Standard library that seems to be installed as a gem.
• Rubygems have a detection method for default gems.
>> Gem.loaded_specs["did_you_mean"].default_gem?
=> false
>> require 'openssl'
=> true
>> Gem.loaded_specs["openssl"].default_gem?
=> true
19. Status of OpenSSL binding
• OpenSSL is already extracted default gems. You can update it
separated ruby core releases same as rubygems, rdoc,
bigdecimal.
• https://github.com/ruby/openssl
• It’s maintained by @rhenium
• Upstream was changed github repository from svn.ruby-lang.org
• He aggressively maintains new feature of openssl
20. Security release
We hard to fix and release these security issue. so all of release
maintainer are volunteer work.
But If your Ruby supports Default gems/Bundled gems, You can
upgrade these gems without upgrading ruby interpreter.
22. Whats psych?
A libyaml wrapper for Ruby
It supports bundled libyaml-* sources. You can build psych
without libyaml-devel(dev) packages.
# Load YAML in to a Ruby object
Psych.load('--- foo') # => 'foo'
# Emit YAML from a Ruby object
Psych.dump("foo") # => "--- foon...n"
23. JRuby integration
• We need to support Java
implementation now.
• I guarantee compatibility for
other implementation used
by Travis.
In current status, It
compatibility was breaking.
Because It’s beta status.
25. Whats rdoc?
RDoc produces HTML and online documentation for Ruby
projects.
# puts listings.product + "n" + listings.price
#
# _Generates_
#
# Chicken Fried Steak
# A well messages pattie, breaded and fried.
#
# Chicken Fried Steak -- 9.95
# A well messages pattie, breaded and fried.
#
def initialize(str, safe_level=nil, trim_mode=nil, eoutvar='_erbout')
@safe_level = safe_level
compiler = make_compiler(trim_mode)
set_eoutvar(compiler, eoutvar)
@src, @encoding, @frozen_string = *compiler.compile(str)
@filename = nil
@lineno = 0
end
26. Current status of rdoc
• I moved canonical repository to ruby/rdoc.
• I handle a project of rdoc and management releases(not
product management)
• Our official tracker named “bugs.ruby-lang.org” is high
threshold. But GitHub resolve this by pull requests.
VS
28. Inside Bundled gems
• It was installed by `tool/rbinstall.rb` on Ruby core repository.
• You can see list of Bundled gems via `gems/bundled_gems`
• We bundled *.gem and unpacked files to tarball package for
Bundled gems.
• `make install` installed Bundled gem your box.
30. Why separated the test framework?
The following libraries uses minitest directly in Ruby 2.3:
• rubygems
• rdoc
Other libraries uses test-unit. rubygems and rdoc are developed
at github.com/rubygems/rubygems and github.com/ruby/rdoc.
We need to support these libraries and their tests.
31. A problem of test-unit/minitest
• It has difference behaviors and namespace from released
gems that are test-unit and minitest.
• [Bug #9660] test/unit, minitest & bundler
• We gave up to maintain compatibility with released gems.
• But @zenspider said “I AM against shipping ruby without a
testing library.”
33. Make in Ruby
Rake is a Make-like program implemented in Ruby. Tasks and
dependencies are specified in standard Ruby syntax.
task :awesome do
puts :bar
end
task beat: [:awesome] do
puts :buzz
end
task default: :beat
34. ruby/rake
•Rake was originally created by Jim Weirich, who unfortunately
passed away in February 2014.
•This repository was originally hosted at github.com/
jimweirich/rake, It has been moved to github.com/ruby/rake by
@drbrain
•Rake adopted SemVer policy. (v0.9.x to v10.x.y)
•@drbrain and @hsbt maintain ruby/rake now.
35. Concerns of bundled gems
• We couldn’t support to compile C extension on Bundled gems.
• Bundled gems couldn’t support cross compilation.
Ex. We need to make Date gem to bundled gem before extracted
from ruby core.
36. Concerns of bundled gems(2)
We need test suite for bundled gem with ruby trunk.
• https://gist.github.com/unak/a80b03d9a33de59bedb52e2711410e0d
• https://github.com/ko1/rubyhackchallenge/issues/25
No one guarantee work bundled gems and develop version of
ruby.
38. Gemification for standard library
https://bugs.ruby-lang.org/issues/5481
• We extracted stdlibs like net-telnet, xmlrpc, rake to bundled
gems.
• These are extracted under the https://github.com/ruby/ . And
shipped on rubygems.org
• Other gems are also extracted at the future.
39. What’s problem of Gamification?
• It issue size is too big for human.
• I resolved it used default gems and bundled gems.
• We can promote standard libraries to default gems, after that
we promote it to bundled gems.
• I am moving toward the final goal for Gemification.
40. Pros of Gemification
• Maintainers can release gem for bugfix, new feature
independent with Ruby core.
• Easily backport stable version from develop version. Ruby
users can use new feature on stable version.
• If upstream is available on GitHub, Ruby users easily send
patch via Pull request.
• Ruby interpreter developper can concentrate development
Ruby internal.
41. Cons of Gemification
• Abandoned and complex dependency on rubygems and
bundler.
• Maintainers need to maintain ruby core and GitHub
repositories both.
• It’s hard to maintain compatibility.
42. How to merge upstream from others
I merged upstream into ruby/ruby periodically using following
instructions.
ruby and rubygems guarantee to work to test and code each
other. it’s the same situation for ruby and rdoc
$ git clone https://github.com/ruby/ruby
$ git clone https://github.com/rubygems/rubygems
$ cd ruby
$ rm -rf lib/rubygems test/rubygtems lib/rubygems.rb
$ cp -rf ../../rubygems/rubygems/lib/rubygems ./lib
$ cp -rf ../../rubygems/rubygems/lib/rubygems.rb ./lib
$ cp -rf ../../rubygems/rubygems/test/rubygems ./test
$ git checkout lib/rubygems/LICENSE.txt
43. backport is hard
rubygems still supports Ruby 1.8.
% g show a34fb569e41cd87866e644d92a9df4be89b3cad2 test/rubygems/test_gem_package.rb
commit a34fb569e41cd87866e644d92a9df4be89b3cad2
Author: Eric Hodel <drbrain@segment7.net>
(snip)
--- test/rubygems/test_gem_package.rb
+++ test/rubygems/test_gem_package.rb
@@ -638,7 +638,7 @@ class TestGemPackage < Gem::Package::TarTestCase
e.message
io
end
- tf.close!
+ tf.close! if tf.respond_to? :close!
end
def test_verify_empty
45. What’s rubygems
RubyGems is a package management framework for Ruby.
• rubygems/rubygems.org:
• The Ruby community's gem host.
• rubygems.org is maintain by infrastructure team of rubygems. It is different
team from rubygems cli team.
• rubygems/rubygems:
• Command line tool of rubygems
• Rubygems are created by Seattle.rb
46. Current problem of rubygems
Bundler team funded RubyTogether take over rubygems/
rubygems
In the past, We easily discuss maintenance plan and policy
about ruby and rubygems to @tenderlove and @drbrain.
I hard to backport a patch to rubygems from ruby core. Because
these patch only need ruby trunk. It is needless stable versions.
47. Reserved words on rubygems.org
Rubygems block reserved name same as standard libraries.
• But you can see: https://rubygems.org/gems/fileutils/versions/
0.7
• If you install fileutils-0.7, fileutils-0.7 break your ruby
environment.
Why???
48. fiddle
fiddle is standard library for wrapper of libffi. But fiddle
was already reserved another implementation(https://
github.com/bsm/fiddle) on rubygems.org
I did coordinate to transfer above namespace and
override CRuby implementation(https://github.com/ruby/
fiddle) now.
49.
50. What we will do?
I must offer to transfer ownership of these gems to
rubygems.org and overwrite it used by ruby stdlib.
My plan for reserved gems:
・Transfer request to owners of reserved gems.
・Removed gemification gems from blacklist on rubygems.org.
・Override reserved gems by standard libraries.
53. Reducing Ruby package size
•In Ruby 2.5, We added “bundler” to default gems.
•Bundler will be integrated RubyGems until Ruby 3.0 releasing.
•I will promote all of standard libraries to default gems.
•I will promote all of default gems without Rubygems
dependencies to bundled gems.
54. Bundle Bundler to Ruby core
• Bundler uses rspec.
• I made `test-bundler` task that is invoking rspec examples of
Bundler.
~/D/r/trunk > mk test-bundler
./miniruby -I../../github.com/ruby/ruby/lib -I. -I.ext/common ../../github.com/ruby/ruby/tool/runruby.rb
--extout=.ext -- --disable-gems -C "../../github.com/ruby/ruby" bin/gem install --no-ri --no-rdoc
--install-dir spec/rspec --conservative 'rspec:~> 3.5'
Run options: exclude {:ruby_repo=>true, :rubygems_master=>true, :git=>"=< 2.14.1", :rubygems=>"=< 2.6.13",
:ruby=>"=< 2.5.0", :realworld=>true, :sudo=>true}
..........................................................................................................
..........................................................................................................
....................
55. Migration status of Rubygems and Bundler
• rubygems-2.7.0 uses bundler on only test code.
• After bundler-2.0 released, We will target rubygems-3.0
• Ruby 2.5.0 have rubygems(-2.6.13) and bundler(-1.15.4), It
helps migration plan of rubygems/bundler.
56. Activated problem for Rubygems
• Rubygems have a activated problem with default gems.
• https://bugs.ruby-lang.org/issues/13847
$ ruby -ropenssl -e 'p OpenSSL::VERSION'
"2.0.5"
$ cat Gemfile
# frozen_string_literal: true
source "https://rubygems.org"
gem 'openssl', '2.0.4'
$ bundle exec ruby -ropenssl -e 'p OpenSSL::VERSION'
/path/to/2.4.1/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/runtime.rb:317:in
`check_for_activated_spec!': You have already activated openssl 2.0.5, but your Gemfile
requires openssl 2.0.4. Prepending `bundle exec` to your command may solve this.
(Gem::LoadError)
57. require :into
https://bugs.ruby-lang.org/issues/10320
Matz has some concerns about ruby internal.
• Conflicts versions of a shared library like libyaml-., libssl-,
libffi, etc...
• Order of LOADED_FEATURE
So, This feature is difficult to implement on current ruby
specification now.
require 'libfile', into: :Lib
58. What are requirements of Rubygems?
base64
benchmark
cgi
digest
English
erb
fileutils
find
io/console
monitor
net/http
net/https
openssl
optparse
pathname
pp
rbconfig
resolv
set
shellwords
socket
stringio
strscan
tempfile
thread
time
timeout
tmpdir
tsort
uri
webrick
Win32API
zlib
59. Does Gemification make happy Rubyists?
• It’s heavy to maintain like github triage, gem release, resolve
dependency.
• I should provide a benefit of gemification for Ruby core team.
61. Summary of Today’s talk
• I described about a standard libraries of the Ruby language.
• I introduced specification of default gems/bundled gems of
Ruby.
• I shared current status of Rubygems and Gemification
projects.
• I shared my plan towards Ruby 3.0.