20140626 red dotrubyconf2014

Oct 12, 20140 likes710 views

1) The Ruby programming language is now primarily developed and maintained by the open source community rather than just Matz, its original creator. 2) To contribute to Ruby, developers should submit bug reports with a minimum reproducible case and logs from different Ruby versions, or submit feature requests with use cases and naming conventions. 3) While GitHub is commonly used, some core developers prefer Redmine, which is where Matz primarily focuses and requires tickets to be submitted.

How to improve
experiences of Ruby
Hiroshi SHIBATA
@hsbt
RedDotRubyConf 2014

class Bar
def bar(foo = foo())
foo
end
def buzz(foo = foo)
foo
end
def foo
:buzz
end
end
p Bar.new.bar
p Bar.new.buzz

% ruby -v r45272.rb
ruby 2.2.0dev (2014-04-13 trunk 45580) [x86_64-darwin13]
:buzz
nil
% ruby -v r45272.rb
ruby 2.1.2p80 (2014-03-01 revision 45231) [x86_64-darwin13.0]
:buzz
:buzz

The document discusses the strategy for building and testing the programming language Hiroshi. It covers: 1. The Ruby Core team which maintains the language and includes over 80 volunteers. 2. The testing strategy for Ruby which involves testing at different levels from the interpreter to libraries. Extensive tests are run on Linux, Windows and macOS. 3. The CI environments used for Ruby development including GitHub Actions, Travis CI and AppVeyor, as well as internal VM clusters. Test results are collected on Ruby CI and discussed on Slack.

20140925 rails pacificHiroshi SHIBATA

This document discusses how to craft a Rails culture within a company by enforcing modern architectures, open source practices, and integrating administrative functions. It provides examples of migrating from older Ruby and Rails versions, replacing legacy middleware, and designing internal or separate apps for administrative tasks. The document advocates an evolutionary approach of learning Rails step-by-step and establishing practices like GitHub workflow and ChatOps to support DevOps.

tDiary annual report 2009 - Sapporo Ruby Kaigi02Hiroshi SHIBATA

This document is the annual report for 2009 of tDiary, an open-source web diary application built using Ruby. It discusses updates made to tDiary in 2009, including releasing version 2.3.2 which added compatibility with Ruby 1.9, as well as plans for future versions including adopting testing frameworks like RSpec and Cucumber, migrating to use the Rack middleware interface, and adding support for XML-RPC and Atom/PubSubHubbub. It also promotes involvement with the tDiary project on GitHub and in the Japanese Ruby community.

Gate of Agile Web DevelopmentKoichi ITO

From 'Legacy' to 'Edge'Hiroshi SHIBATA

This document summarizes a presentation given at RedDotRubyConf 2013 about continuously upgrading a legacy Rails application to newer versions of Ruby and Rails. It discusses the challenges faced such as compatibility issues, testing to prevent regressions, and deploying updates without downtime. Continuous integration, staging environments, monitoring and alerts were used to safely upgrade the application from Ruby 1.8.6 and Rails 2.0.2 to Ruby 2.0 and Rails 3.2 over time.

Leave end-to-end testing to CapybaraHiroshi SHIBATA

Leave end-to-end testing to Capybara. Capybara is a web testing tool that simulates user interactions with a website. It allows automating browser interactions for scenarios and features using domain-specific languages like Cucumber. Capybara supports using different drivers like Selenium for JavaScript interactions and HtmlUnit for non-JavaScript sites. Specifying the driver and JavaScript support in tests allows running tests across different environments.

20140918 ruby kaigi2014Hiroshi SHIBATA

How to develop Jenkins plugin using to ruby and Jenkins.rbHiroshi SHIBATA

- The document discusses developing Jenkins plugins using Ruby and the jpi tool. It covers generating a sample wrapper plugin, configuring the plugin, and building and releasing the plugin through jpi commands. - The speaker demonstrates creating a sample "rbenv" plugin with jpi to configure Ruby versions and gems for builds. - Commands like jpi new, generate, build, server and release are used to generate the plugin scaffolding, configure the wrapper, build the plugin file, host it locally for testing, and prepare it for release.

20140425 ruby conftaiwan2014Hiroshi SHIBATA

Gems on RubyHiroshi SHIBATA

1. The document discusses RubyGems, Bundler, and rbenv/ruby-build. It provides an overview of each tool's purpose and history. 2. RubyGems is the package manager for Ruby libraries. Bundler is a tool for managing dependencies of Ruby applications. Rbenv/ruby-build allow managing multiple Ruby versions and building Ruby. 3. The document outlines plans to further integrate RubyGems and Bundler, but notes Bundler 2 has not yet been released, which is needed for full integration. Security improvements have also been made to RubyGems.

20140419 oedo rubykaigi04Hiroshi SHIBATA

This document summarizes the key points in migrating a legacy Rails 2.0 application to a newer version of Rails. It discusses upgrading to Rails 2.3 first to address compatibility issues. Then it recommends upgrading to Ruby 2.1 and Rails 4.1 to get performance improvements from the language and framework updates. Various techniques are presented for the migration process such as running the newer versions in production gradually.

How DSL works on RubyHiroshi SHIBATA

This document summarizes a presentation about the future of the Rake gem and domain-specific languages (DSLs) in Ruby. The presentation discusses: 1. How Rake works as a Make-like program implemented in Ruby syntax with tasks and dependencies. Rake files use standard Ruby syntax. 2. Examples of common patterns for building internal DSLs in Ruby using class/module methods, method definition, implicit/explicit code blocks, and instance evaluation. 3. How popular Ruby gems like Rake, Bundler, and Thor use DSL techniques and inherit from each other to provide domain-specific interfaces.

How to Begin to Develop Ruby CoreHiroshi SHIBATA

How to distribute Ruby to the worldHiroshi SHIBATA

The document discusses how the Ruby programming language is developed and released. It describes the Ruby core team and committers, release cycles, backporting fixes, testing on various platforms via Ruby CI, packaging and distributing releases, handling security issues, and the *.ruby-lang.org domains. It also discusses moving the source code repository from Subversion to Git and migrating development tools and processes.

20141210 rakuten techtalkHiroshi SHIBATA

This document discusses how to change an organization and provides examples of how the author's company changed their technical organization and processes. Some of the key points discussed include adopting agile methodologies like Scrum, emphasizing testing and use of open source tools, upgrading technologies and adopting newer versions of Ruby and Rails, and optimizing teams and processes to better support the business.

How to develop the Standard Libraries of Ruby?Hiroshi SHIBATA

RubyGems 3 & 4Hiroshi SHIBATA

The document discusses changes and new features in RubyGems 3 and 4, the package manager for the Ruby programming language. Some key points: - RubyGems 3 removes deprecated methods and support for older Ruby versions. It adds warnings for deprecated methods and allows direct use of the release toolchain. - RubyGems 4 will have incompatible changes like upgrading the dependency resolver, making conservative installation the default, changing the behavior of default installation, and making user installation the default. - Other topics discussed include deprecation handling, code search tools for RubyGems code, testing changes on all Ruby versions, removing deprecated code, and pre-releasing RubyGems updates.

Gemification for Ruby 2.5/3.0Hiroshi SHIBATA

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.

Middleware as Code with mrubyHiroshi SHIBATA

This document discusses using the mruby programming language as middleware code. Some key points: - mruby allows embedding Ruby code into middleware applications like web servers. This provides a powerful programming environment for Rubyists to write middleware code. - ngx_mruby is an example of using mruby with the nginx web server. It allows placing Ruby code handlers and variables in the nginx configuration file. - Advantages of mruby include producing a single binary without separate Ruby files, and ability to embed Ruby runtime and code directly into middleware applications like web servers. - The document demonstrates sample ngx_mruby code for content handlers, variables, and initialization/worker scripts. It

The Future of Dependency Management for RubyHiroshi SHIBATA

The document discusses integrating the Bundler dependency manager into the Ruby programming language core. It covers the benefits of integrating Bundler, such as allowing developers to manage library dependencies directly within Ruby projects. It also discusses challenges faced in integrating Bundler, like ensuring Bundler test suites work properly within the Ruby core codebase. The author details steps taken to start merging Bundler code into Ruby, including adding a "make test-bundler" command to run Bundler tests during development.

Gemification plan of Standard Library on RubyHiroshi SHIBATA

The document discusses plans to extract standard Ruby libraries into gems to improve maintenance. It notes libraries have been extracted as default or bundled gems, with different maintenance policies. Benefits include easier bugfixes and new features, but concerns include complex dependencies, need for cross-platform support, and ensuring gems do not conflict with standard libraries. It provides statistics on libraries extracted in Ruby 2.4 and 2.5 and discusses ongoing work like OpenSSL extraction and addressing naming conflicts.

The Future of Bundled BundlerHiroshi SHIBATA

1. The first step of package management integration discusses integrating Bundler into RubyGems to provide bundled gems as the default package management solution. 2. What's happened in Ruby 2.6 discusses updates to RubyGems 3 and Bundler 2 that dropped support for older Ruby versions and integrated Bundler fully into Ruby 2.6 as the default package manager. 3. BugMash after releasing Ruby 2.6 summarizes issues that came up after Ruby 2.6's release regarding path injection problems with LOAD_PATH, invalid gemspec generation by the installer, and Bundler version switching on Heroku.

Large-scaled Deploy Over 100 Servers in 3 MinutesHiroshi SHIBATA

Large-scaled Deploy Over 100 Servers in 3 Minutes Deployment strategy for next generation involves creating OS images using Packer and cloud-init that allow deploying over 100 servers within 3 minutes through automation. The strategy uses Puppet for configuration management and builds minimal and application-specific images to reduce bootstrap time. All deployment operations are implemented through a CLI tool for rapid and automated scaling.

Dependency Resolution with Standard LibrariesHiroshi SHIBATA

The document discusses the roadmap for RubyGems and Bundler integration with Ruby 3.0. Key points include: 1) RubyGems 3.1 and Bundler 2.1 were recently released with improvements like lazily loading default gems. 2) Future versions will continue merging the projects, with RubyGems 3.2/Bundler 2.2 integrating into Ruby 2.8. 3) Ruby 3.0 will focus on "gemifying" standard libraries by extracting them to default gems, though some may be excluded. 4) This will require addressing issues around dependency and version resolution for the new default gems.

RubyGems 3 & 4Hiroshi SHIBATA

How to Begin Developing Ruby CoreHiroshi SHIBATA

This document provides an introduction to testing the Ruby programming language. It discusses how to set up a development environment to run Ruby's core tests, describes the various test suites and tasks, and provides examples of test files. The document encourages contributors to test Ruby by cloning its repository, running the test suites locally, focusing tests in specific areas, and submitting patches for new or updated tests.

How to test code with mrubyHiroshi SHIBATA

This document discusses testing code written for mruby, a lightweight Ruby implementation. It proposes using the mruby runtime itself to test code, rather than Ruby, by using the mruby-mtest library. This allows testing mruby code directly using the same binaries and libraries as production. Sample code shows how to structure tests and set up a test runner to execute tests against the mruby binary. Testing code with mruby provides faster, more direct testing compared to using Ruby.

OSS Security the hard wayHiroshi SHIBATA

Hiroshi SHIBATA presented on OSS security at the builderscon 2019 conference. The presentation covered: 1. How Ruby handles releases on a regular schedule and processes for stable and development versions. 2. Policies for triaging vulnerabilities based on impact and developing workflow for coordinated security releases. 3. Recent attacks targeting RubyGems where malicious gems were uploaded by hijacking developer accounts or registering typosquatted gems. 4. Steps users can take to improve security like using strong unique passwords, enabling two-factor authentication, and being wary of code injections in gem installations or native extensions.

20131109 ruby conf2013Hiroshi SHIBATA

RailsGirls JapanHiroshi SHIBATA

More Related Content

What's hot (20)

20140425 ruby conftaiwan2014Hiroshi SHIBATA

Gems on RubyHiroshi SHIBATA

20140419 oedo rubykaigi04Hiroshi SHIBATA

How DSL works on RubyHiroshi SHIBATA

How to Begin to Develop Ruby CoreHiroshi SHIBATA

How to distribute Ruby to the worldHiroshi SHIBATA

20141210 rakuten techtalkHiroshi SHIBATA

How to develop the Standard Libraries of Ruby?Hiroshi SHIBATA

RubyGems 3 & 4Hiroshi SHIBATA

Gemification for Ruby 2.5/3.0Hiroshi SHIBATA

Middleware as Code with mrubyHiroshi SHIBATA

The Future of Dependency Management for RubyHiroshi SHIBATA

Gemification plan of Standard Library on RubyHiroshi SHIBATA

The Future of Bundled BundlerHiroshi SHIBATA

Large-scaled Deploy Over 100 Servers in 3 MinutesHiroshi SHIBATA

Dependency Resolution with Standard LibrariesHiroshi SHIBATA

RubyGems 3 & 4Hiroshi SHIBATA

How to Begin Developing Ruby CoreHiroshi SHIBATA

How to test code with mrubyHiroshi SHIBATA

OSS Security the hard wayHiroshi SHIBATA

20140425 ruby conftaiwan2014Hiroshi SHIBATA

Gems on RubyHiroshi SHIBATA

20140419 oedo rubykaigi04Hiroshi SHIBATA

How DSL works on RubyHiroshi SHIBATA

How to Begin to Develop Ruby CoreHiroshi SHIBATA

How to distribute Ruby to the worldHiroshi SHIBATA

20141210 rakuten techtalkHiroshi SHIBATA

How to develop the Standard Libraries of Ruby?Hiroshi SHIBATA

RubyGems 3 & 4Hiroshi SHIBATA

Gemification for Ruby 2.5/3.0Hiroshi SHIBATA

Middleware as Code with mrubyHiroshi SHIBATA

The Future of Dependency Management for RubyHiroshi SHIBATA

Gemification plan of Standard Library on RubyHiroshi SHIBATA

The Future of Bundled BundlerHiroshi SHIBATA

Large-scaled Deploy Over 100 Servers in 3 MinutesHiroshi SHIBATA

Dependency Resolution with Standard LibrariesHiroshi SHIBATA

RubyGems 3 & 4Hiroshi SHIBATA

How to Begin Developing Ruby CoreHiroshi SHIBATA

How to test code with mrubyHiroshi SHIBATA

OSS Security the hard wayHiroshi SHIBATA

Viewers also liked (20)

20131109 ruby conf2013Hiroshi SHIBATA

RailsGirls JapanHiroshi SHIBATA

20131019 rails girlstokyo3rdHiroshi SHIBATA

技術的負債との付き合い方Hiroshi SHIBATA

GitHub Enterprise with GMO PepaboHiroshi SHIBATA

Practical Testing of Ruby CoreHiroshi SHIBATA

The document discusses testing practices for the Ruby programming language. It provides details on how to run various test suites that are part of the Ruby source code repository, including: 1. Running the "make test" command which runs sample tests, known bug tests, and tests defined in the test/ directory. 2. Running "make test-all" which runs core library and standard library tests under the test/ directory. 3. Running "make check" which builds encodings and extensions, runs all test tasks including test frameworks like Test::Unit and Minitest. 4. It also discusses strategies for merging test changes from external repositories like RubyGems and RDoc back into the Ruby source code

mruby で mackerel のプラグインを作るはなしHiroshi SHIBATA

This document discusses how to create Mackerel plugins using mruby. It explains what Mackerel plugins are, the required format, and how to write command line tools and classes in mruby. It then provides an example of implementing Redis commands like SCARD and SMEMBERS in mruby-redis by reading the C source and making additions. This allows monitoring Redis set data with Mackerel. Finally, it shows a sample Mackerel plugin for monitoring Sidekiq job counts.

Advanced technic for OS upgrading in 3 minutesHiroshi SHIBATA

This document discusses strategies for rapidly automating operating system upgrades and application deployments at scale. It proposes a two-phase image creation strategy using official OS images and Packer to build minimal and role-specific images. Automated tools like Puppet, Capistrano, Consul and Fluentd are configured to allow deployments to complete within 30 minutes through infrastructure-as-code practices. Continuous integration testing with Drone and Serverspec is used to refactor configuration files and validate server configurations.

成長を加速する minne の技術基盤戦略Hiroshi SHIBATA

Ruby 'root'Hiroshi SHIBATA

The advanced usage of heroku clientHiroshi SHIBATA

Create Responsive Learning, Engage Mobile UsersXyleme

The document discusses responsive design for learning content and how the Xyleme LCMS allows for its implementation. It covers: 1) What responsive design is and why it is effective for creating learning content accessible on any device 2) How the Xyleme LCMS can achieve responsive design without technical expertise through its publishing engine 3) Customizing Xyleme's responsive learning templates using its intuitive DIY interface

The Princeton Review: A Case Study in Scalable Learning Content DeliveryXyleme

Designing solutions for large scale content development and online delivery can be daunting. Michael Bleyhl, VP, Product Technology of The Princeton Review, is not only responsible for setting learning technology strategy, but also for setting the standards around Adaptive, Predictive and Personal Learning. He will discuss their unique business challenges, solution design, key integration strategies as well as his vision for the future of personalized online learning. He is joined by Mark Hellinger, CEO of Xyleme. The Xyleme Learning Platform has played a critical role in The Princeton Review’s success, incorporating single-source content development along with secure, scalable delivery from the cloud.

Paychex Single Source AuthoringXyleme

This document summarizes the implementation of a single source authoring system at Paychex, Inc. It discusses how the company had over 12,000 employees supporting 560,000 clients across nearly 100 products and services. Their training and development center utilized a centralized approach to author content once and distribute it across multiple channels. They implemented a new single source authoring system to improve content reuse, media management, and engagement metrics. The system allowed content to be authored once and then distributed to various business units and employee audiences, addressing the need for more efficient content creation and delivery.

20131208 agile samuraibasecampHiroshi SHIBATA

Learning Delivery: Meeting the Learner Where They Are - Part 1Xyleme

In this 27 minute webinar, part 1 of a 2 part series, Xyleme will have a conversation with Cristine Lipscomb (Duckworth), partner in the Chapman Alliance, about how and where learners learn. Like she does with her many clients from a variety of industries, she will address the big picture questions like ‘how do we adapt our content strategy to address the needs of the modern learner’, and ‘where do we put our technology investments to ensure delivery anytime, anywhere?’

Using personalization to create next generation performance supportXyleme

When training content moves from large courses to semantically rich nuggets of information, you can create a whole host of specialized, next-generation performance support apps that deliver personalized, bite-sized learning to employees at the moment-of-need on the device of their choice. But getting there is not easy. In the "how-to" part of this session, you will learn how to think about learning as an app-driven experience rather than a course-driven one, how to develop content that drives relevance and flows seamlessly across devices, and how to match user profiles and behavior to content to drive personalized recommendations. In the "here it is" part of this session, you will see how Dunkin' Brands supports more than 7,000 US restaurants through contextual performance support web portals and mobile apps that deliver relevant moment-of-need procedural information as well as enabling real-time operational audits. This is not your grandfather's performance support!

Caterpillar Single SourceXyleme

This document discusses Caterpillar's single source approach to learning and development. It outlines their Digital Product Catalog (DPC) which houses online courses organized by campus (subject area) for management, sales, service, and product support. In 2014, over 667,000 course sessions were completed through the DPC, including 27,001 instructor-led sessions and 537,982 web-based trainings. The DPC aims to provide a centralized, engaging learning environment for Caterpillar employees through tools like interactive slides, mobile access to training plans and goals, and a new simplified campus navigation launching in 2015.

Middleware as Code with mrubyHiroshi SHIBATA

The document discusses testing Ruby code used in ngx_mruby, an open source project that embeds the mruby scripting language into the nginx web server. It proposes a testing approach using a dummy implementation of the ngx_mruby API to test the Ruby code in isolation without needing nginx. Sample code shows how to set up dummy request and connection classes to mimic the ngx_mruby environment, as well as a memcached class to test code that interacts with memcached. A skeleton test case demonstrates how to write tests using this approach with the Test::Unit framework to test specific behaviors like restricting requests based on cookie sessions.

The Google Analytics Approach to Measuring Learning: Allowing HR to move at t...Xyleme

A strategic partner to the business is able to prove the effectiveness and efficiency of their organization. Today, we measure time-in-training, completion rates and test scores. Unfortunately, these don’t tell you if the training you are providing is actually working. The business wants more. They want low-level, actionable metrics. This can be accomplished when we take a Google analytics approach to measuring learning. What if we had a set of learning analytics that could be plugged into the corporate scorecard? And, what if we could take immediate action on these analytics to make course corrections at the speed of business? In her session at the ASTD 2014 Conference, Xyleme VP of Marketing Dawn Poulos, addressed these questions through a series of real-world use cases that showed learning data aligned to functional performance indicators. Attendees left the session with the analytical tools they need to prove the ROI of their training initiatives.

20131109 ruby conf2013Hiroshi SHIBATA

RailsGirls JapanHiroshi SHIBATA

20131019 rails girlstokyo3rdHiroshi SHIBATA

技術的負債との付き合い方Hiroshi SHIBATA

GitHub Enterprise with GMO PepaboHiroshi SHIBATA

Practical Testing of Ruby CoreHiroshi SHIBATA

mruby で mackerel のプラグインを作るはなしHiroshi SHIBATA

Advanced technic for OS upgrading in 3 minutesHiroshi SHIBATA

成長を加速する minne の技術基盤戦略Hiroshi SHIBATA

Ruby 'root'Hiroshi SHIBATA

The advanced usage of heroku clientHiroshi SHIBATA

Create Responsive Learning, Engage Mobile UsersXyleme

The Princeton Review: A Case Study in Scalable Learning Content DeliveryXyleme

Paychex Single Source AuthoringXyleme

20131208 agile samuraibasecampHiroshi SHIBATA

Learning Delivery: Meeting the Learner Where They Are - Part 1Xyleme

Using personalization to create next generation performance supportXyleme

Caterpillar Single SourceXyleme

Middleware as Code with mrubyHiroshi SHIBATA

The Google Analytics Approach to Measuring Learning: Allowing HR to move at t...Xyleme

Similar to 20140626 red dotrubyconf2014 (20)

How to debug mruby (rubyconftw2014)yamanekko

This document discusses debugging mruby code. It describes how mruby compiles Ruby code to bytecode without debugging information. The authors developed a hybrid debugger that uses GDB at the C level along with a Ruby extension to allow setting breakpoints and stepping through both Ruby and C code. They demonstrate their debugger using Eclipse and show that more features need to be added like stepping, backtraces and viewing variables. The goal is to make debugging mruby easier.

TypeProf for IDE: Enrich Development Experience without Annotationsmametter

The document discusses TypeProf for IDE, a VSCode extension powered by TypeProf, a static type analyzer for Ruby. It allows achieving aspects of modern development experience like on-the-fly error reporting and type inference without type annotations. The demo shows features like method signature hints, error reporting, and completion working through the language server protocol. Future work includes improving parser robustness and optimizing analysis performance.

The story of language developmentHiroshi SHIBATA

The document summarizes aspects of developing and maintaining the Ruby programming language, including its core team members, development resources, issue tracking process, testing procedures, release management, and security practices. The Ruby core team consists of around 90 committers and branch maintainers who work on various parts of the codebase. Development resources include build servers, documentation hosting, package distribution, and funding from various sponsors. Feature requests require use cases, attached patches, and approval from the project leader Matz. Releases aim to occur yearly on Christmas and follow a branch model with backported fixes. Security issues present ongoing challenges.

P4 P Update January 2009vsainteluce

This document is the slides from a presentation introducing Ruby. It discusses what the presentation will cover which is an overview of Ruby including its history, features, syntax, and comparisons to Perl and Python. It provides a quick tour through Ruby syntax and basics like variables, data types, operators, and control structures. It also covers classes, inheritance and modules. Finally, it lists resources for learning more about Ruby.

Ebay News 2001 4 19 EarningsQuarterlyEarningsReports

Ebay News 2000 10 19 EarningsQuarterlyEarningsReports

Ruby 4.0 To Infinity and Beyond at Ruby Conference Kenya 2017 by Bozhidar BatsovMichael Kimathi

The document discusses plans and ideas for Ruby 4.0. Some key points include: - Ruby 4.0, codenamed "Buzz", aims to be 4 times faster than Ruby 3.0 through optimizations and removing legacy features. - New features may include immutable data structures like vectors, hashes and sets, as well as static typing and runtime contracts inspired by RDL. - Improved concurrency through CSP-style APIs inspired by concurrent-ruby for better parallel programming. - Simplicity is a core design principle - reducing redundancies and dropping unused or obscure features like BEGIN/END blocks, flip-flops, character literals and more. - The standard library could be

Lightweight APIs in mRuby (Михаил Бортник)Fwdays

CRuby_Committers_Whos_Who_in_2014nagachika t

Week1reneedv

This document provides an overview of an introductory course on the Ruby programming language. It outlines the course structure, which includes lectures, demos, exercises and homework. It also details the requirements for installation of Ruby and related tools like Git and RSpec. The document demonstrates how to check that these tools are properly installed and introduces concepts like version control with Git and test-driven development with RSpec.

Pré Descobrimento Do Brasilecsette

Rib Console and plugins to make you happierM C

The secret of programming language development and futureHiroshi SHIBATA

Developing cross platform desktop application with RubyAnis Ahmad

A bridge between php and ruby do_aki

Truby Daisuke Watanabe

Here are the key steps in the compiler implementation: 1. The compiler takes Tiby code as input and converts it to an abstract syntax tree (AST) representation. 2. It traverses the AST and generates corresponding Jasmin bytecode instructions. 3. For example, an integer assignment in Tiby like "a:Int = 10" would be represented as a node in the AST. 4. The compiler generates Jasmin instructions to create an integer object, load the value 10, call the integer constructor, and store the object in a variable. 5. Method calls in Tiby are also represented as nodes in the AST. 6. The compiler generates Jasmin instructions to load

Foreman - Process manager for applications with multiple componentsStoyan Zhekov

Upgrading to Ruby 2.1, Rails 4.0, Bootstrap 3.0bryanbibat

Functional MCU programmingKiwamu Okabe

This document discusses functional programming on microcontroller units (MCUs) and summarizes the speaker's workshop on this topic. It explores reasons for using functional languages on MCUs and Internet of Things devices due to benefits like strong typing and runtime error avoidance. Several cross-compilers from functional languages to C suitable for MCUs are presented, like Ajhc for Haskell and Rust, along with experiences running them on boards like the mbed LPC1768 and Seeeduino Arch Pro. Debugging options using pyOCD and OpenOCD are also covered.

The new Odoo community organization and platformOdoo

Odoo is transitioning its community tools to GitHub from Launchpad. This includes moving the source code repository from Bazaar to Git, integrating Runbot for continuous integration, and using GitHub for pull requests and bug reports. Translations will continue on Launchpad initially with future integration of tools like Transifex planned. The documentation is also migrating to be more wiki-based on GitHub.

How to debug mruby (rubyconftw2014)yamanekko

TypeProf for IDE: Enrich Development Experience without Annotationsmametter

The story of language developmentHiroshi SHIBATA

P4 P Update January 2009vsainteluce

Ebay News 2001 4 19 EarningsQuarterlyEarningsReports

Ebay News 2000 10 19 EarningsQuarterlyEarningsReports

Ruby 4.0 To Infinity and Beyond at Ruby Conference Kenya 2017 by Bozhidar BatsovMichael Kimathi

Lightweight APIs in mRuby (Михаил Бортник)Fwdays

CRuby_Committers_Whos_Who_in_2014nagachika t

Week1reneedv

Pré Descobrimento Do Brasilecsette

Rib Console and plugins to make you happierM C

The secret of programming language development and futureHiroshi SHIBATA

Developing cross platform desktop application with RubyAnis Ahmad

A bridge between php and ruby do_aki

Truby Daisuke Watanabe

Foreman - Process manager for applications with multiple componentsStoyan Zhekov

Upgrading to Ruby 2.1, Rails 4.0, Bootstrap 3.0bryanbibat

Functional MCU programmingKiwamu Okabe

The new Odoo community organization and platformOdoo

More from Hiroshi SHIBATA (19)

Introduction of Cybersecurity with Ruby at RedDotRubyConf 2024Hiroshi SHIBATA

I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems. The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS. Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application. I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.

Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA

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

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.

How resolve Gem dependencies in your code?Hiroshi SHIBATA

This document contains the slides for a presentation on resolving gem dependencies in Ruby code. It discusses RubyGems and Bundler, which are package managers for Ruby that handle dependency resolution. Key terms are defined, like gem, gemspec, Gemfile, and various components involved in dependency resolution like the resolver, resolver engine, and different engines used by RubyGems and Bundler. Performance issues with RubyGems are also addressed, and how Bundler helps address them.

How resolve Gem dependencies in your code?Hiroshi SHIBATA

The document discusses resolving gem dependencies in Ruby code. It begins with an introduction to ANDPAD and then defines key terms related to package managers and gem dependency resolution. It describes the architecture of RubyGems and Bundler and some current issues, such as performance problems and cases where `bundle update` or `gem install` do not work as expected. Deep dives are provided into specific cases to explain underlying causes.

Ruby コミッターと歩む Ruby を用いたプロダクト開発Hiroshi SHIBATA

Why ANDPAD commit Ruby and RubyKaigi?Hiroshi SHIBATA

RailsGirls から始めるエンジニアリングはじめの一歩Hiroshi SHIBATA

Roadmap for RubyGems 4 and Bundler 3Hiroshi SHIBATA

The document discusses the roadmap for integrating RubyGems and Bundler, including gemifying standard Ruby libraries for Ruby 3. Key points include: 1) RubyGems and Bundler repositories and teams have been merged into a monorepo to more closely integrate the projects. 2) The roadmap includes releasing RubyGems and Bundler versions simultaneously and potentially bumping to RubyGems 4.0 synchronized with Ruby 3. 3) Standard libraries will be extracted to default gems for Ruby 3, aiming to publish all to default gems except those using internal APIs. 4) Issues around dependency resolution and versioning of default gems need to be addressed in the integration.

The Future of library dependency management of RubyHiroshi SHIBATA

The document discusses the integration of package management in Ruby. It provides an overview of RubyGems and Bundler, the two main tools for managing library dependencies in Ruby. It also outlines the roadmap for further integrating RubyGems and Bundler, including merging RubyGems 3.2 into Ruby 2.8 and moving Bundler's canonical repository to RubyGems.org. Additionally, it discusses challenges around dependency resolution compatibility and activation of default gems between different versions of RubyGems and Bundler.

Ruby Security the Hard WayHiroshi SHIBATA

1. The document discusses security topics related to Ruby including defining vulnerabilities, triage policies, and the RubyGems.org workflow. 2. It describes how vulnerabilities are reported and coordinated between developers, and outlines the process of code fixes, releases, and disclosure. 3. Recent attacks on RubyGems.org are reviewed, highlighting account hijacking and typo squatting issues. Solutions discussed include not reusing passwords, using strong unique passwords, and enabling two-factor authentication.

The Future of library dependency manageement of RubyHiroshi SHIBATA

What's new in RubyGems3Hiroshi SHIBATA

RubyGems is the package manager for Ruby libraries. Hiroshi Shibata discussed recent changes to RubyGems 3 and 4, as well as integration efforts between RubyGems and Bundler. Key points included making the conservative option default in RubyGems 4, installing gems to the user directory by default, and resolving incompatibilities between dependency resolvers in RubyGems and Bundler. The team is working to merge code bases and integrate command line interfaces.

Productive Organization with RubyHiroshi SHIBATA

Gems on RubyHiroshi SHIBATA

How to distribute Ruby to the worldHiroshi SHIBATA

The secret of Release story discusses how Ruby is released and distributed to the world. It covers: 1. The Ruby core team which maintains and releases Ruby. 2. The release cycle and process which aims to release every Christmas with preview releases and backporting of fixes. 3. The *.ruby-lang.org domains which are controlled by Matz and host official Ruby resources like documentation, packages, and repositories. 4. Tools for installing Ruby from source like rbenv and ruby-build. 5. Experimental Ruby snap packages which package Ruby as self-contained binaries. 6. Plans to migrate the source code repository from Subversion to Git hosted on git.ruby-lang.org.

Gemification for Ruby 2.5/3.0Hiroshi SHIBATA

This document discusses plans for standard Ruby libraries and gemification. It introduces the classifications of standard, default, and bundled libraries. It outlines pros and cons of extracting libraries to gems. The author details their work transferring reserved gems on Rubygems and overriding standard libraries. They propose promoting all standard libraries to default gems and removing Rubygems dependencies from default gems for Ruby 3.0 to reduce package size. Integrating Bundler into the Ruby core by Ruby 3.0 is also discussed.

Introduction of Cybersecurity with Ruby at RedDotRubyConf 2024Hiroshi SHIBATA

Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA

Long journey of Ruby Standard library at RubyKaigi 2024Hiroshi SHIBATA

Long journey of Ruby standard library at RubyConf AU 2024Hiroshi SHIBATA

Deep dive into Ruby's require - RubyConf Taiwan 2023Hiroshi SHIBATA

How resolve Gem dependencies in your code?Hiroshi SHIBATA

Ruby コミッターと歩む Ruby を用いたプロダクト開発Hiroshi SHIBATA

Why ANDPAD commit Ruby and RubyKaigi?Hiroshi SHIBATA

RailsGirls から始めるエンジニアリングはじめの一歩Hiroshi SHIBATA

Roadmap for RubyGems 4 and Bundler 3Hiroshi SHIBATA

The Future of library dependency management of RubyHiroshi SHIBATA

Ruby Security the Hard WayHiroshi SHIBATA

The Future of library dependency manageement of RubyHiroshi SHIBATA

What's new in RubyGems3Hiroshi SHIBATA

Productive Organization with RubyHiroshi SHIBATA

Gems on RubyHiroshi SHIBATA

How to distribute Ruby to the worldHiroshi SHIBATA

Gemification for Ruby 2.5/3.0Hiroshi SHIBATA

20140626 red dotrubyconf2014

1. How to improve experiences of Ruby Hiroshi SHIBATA @hsbt RedDotRubyConf 2014

2. Thank you!

3. SHIBATA Hiroshi(@hsbt)

4. Ruby Committer

6. Who are making Ruby now?

7. Matz?

8. No

9. Matz’s work

10. mruby

11. bump version

12. Who are making Ruby now?

13. Community

14. Example with me

15. Use trunk everyday

16. class Bar def bar(foo = foo()) foo end def buzz(foo = foo) foo end def foo :buzz end end p Bar.new.bar p Bar.new.buzz

17. % ruby -v r45272.rb ruby 2.2.0dev (2014-04-13 trunk 45580) [x86_64-darwin13] :buzz nil % ruby -v r45272.rb ruby 2.1.2p80 (2014-03-01 revision 45231) [x86_64-darwin13.0] :buzz :buzz

19. How to contribute Ruby?

20. bugreport

21. Good bug report

22. minimum case

23. Try different version of ruby

24. clash log attached

25. feature request

26. Good feature request

27. usecase

28. naming

29. code

30. github is ok