Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
The W3C is starting to recommend to use WebAssembly, and we can compile mruby to WebAssembly very easy in now day. But we have Opal and it works well, we really need to use WebAssembly? Let me share my experience about trying to add mruby to HTML5 game, and discuss the pros and cons when we use Ruby in WebAssembly way in Web.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the talk titled "Is it time to run Ruby on Web via WebAssembly?" by elct9620 at RubyKaigi Takeout 2020, the speaker shares insights on using WebAssembly to run Ruby applications in web environments. The session highlights the ease of compiling mruby to WebAssembly, especially as the W3C starts recommending its use. The discussion draws on elct9620's experiences with integrating Ruby into an HTML5 game, focusing on the advantages and challenges of employing Ruby in a WebAssembly context. **Key Points Discussed:** - **Background and Motivation:** The speaker's journey began with a search for a solution to an open-source game that had ceased functioning due to the end of Flash support. This led to an exploration of rewriting the client-side in Ruby using WebAssembly. - **Bootstrapping WebAssembly Projects:** Elct9620 explains how to start a WebAssembly project using Ruby, emphasizing the use of Emscripten as the chosen compiler, despite initial attempts with LLVM. - **Compilation Process:** The process involves defining configuration, linking Ruby binaries with C code, and compiling them into WebAssembly format. - **Demo and Practical Application:** A demo on GitHub was presented, showcasing how to run the compiled project. The speaker highlighted the necessity for JavaScript to manage standard output from Ruby. - **Challenges Faced:** Key challenges discussed included the complexity of memory management in WebAssembly, the inefficiencies of interchanging data types between Ruby and JavaScript, and the issues surrounding debugging Ruby in a WebAssembly environment. - **Performance Concerns:** The speaker cautioned about the performance overhead when handling large datasets and suggested that Ruby’s integration with WebAssembly is more suited for smaller applications rather than resource-intensive games. **Conclusions and Takeaways:** - Utilizing Ruby in a WebAssembly context is feasible but comes with practical limitations that require consideration, particularly regarding memory constraints and the complexity of configuration. - The approach can be beneficial for lightweight applications but is not yet fully developed for larger-scale projects. Future development in tools and methodologies is necessary to address these limitations effectively. - The speaker encourages consideration of the benefits and challenges before implementing Ruby in WebAssembly for web applications.
Suggest modifications
Cancel
