Ruby 3.3.0-preview3 Released

We are pleased to announce the release of Ruby 3.3.0-preview3. Ruby 3.3 adds a new parser named Prism, uses Lrama as a parser generator, adds a new pure-Ruby JIT compiler named RJIT, and many performance improvements especially YJIT.

Prism

  • Introduced the Prism parser as a default gem
    • Prism is a portable, error tolerant, and maintainable recursive descent parser for the Ruby language
  • Prism is production ready and actively maintained, you can use it in place of Ripper
    • There is extensive documentation on how to use Prism
    • Prism is both a C library that will be used internally by CRuby and a Ruby gem that can be used by any tooling which needs to parse Ruby code
    • Notable methods in the Prism API are:
      • Prism.parse(source) which returns the AST as part of a ParseResult
      • Prism.dump(source, filepath) which returns the serialized AST as a String
      • Prism.parse_comments(source) which returns the comments
  • You can make pull requests or issues directly on the Prism repository if you are interested in contributing

Use Lrama instead of Bison

RJIT

  • Introduced a pure-Ruby JIT compiler RJIT and replaced MJIT.
    • RJIT supports only x86-64 architecture on Unix platforms.
    • Unlike MJIT, it doesn’t require a C compiler at runtime.
  • RJIT exists only for experimental purposes.
    • You should keep using YJIT in production.
  • If you are interested in developing JIT for Ruby, please check out k0kubun’s presentation on Day 3 of RubyKaigi.

YJIT

  • Major performance improvements over 3.2
    • Support for splat and rest arguments has been improved.
    • Registers are allocated for stack operations of the virtual machine.
    • More calls with optional arguments are compiled.
    • Exception handlers are also compiled.
    • Instance variables no longer exit to the interpreter
      with megamorphic object shapes.
    • Unsupported call types no longer exit to the interpreter.
    • Integer#!=, String#!=, Kernel#block_given?, Kernel#is_a?,
      Kernel#instance_of?, Module#=== are specially optimized.
    • Now more than 3x faster than the interpreter on optcarrot!
  • Significantly improved memory usage over 3.2
    • Metadata for compiled code uses a lot less memory.
    • Generate more compact code on ARM64
  • Compilation speed is now slightly faster than 3.2.
  • Add RubyVM::YJIT.enable that can enable YJIT at run-time
    • You can start YJIT without modifying command-line arguments or environment variables.
    • This can also be used to enable YJIT only once your application is
      done booting. --yjit-disable can be used if you want to use other
      YJIT options while disabling YJIT at boot.
  • Option to disable code GC and treat --yjit-exec-mem-size as a hard limit
    • Can produce better copy-on-write behavior on servers using unicorn and forking
  • ratio_in_yjit stat produced by --yjit-stats is now avaiable in release builds,
    a special stats or dev build is no longer required to access most stats.
  • Exit tracing option now supports sampling
    • --trace-exits-sample-rate=N
  • --yjit-perf is added to facilitate profiling with Linux perf.
  • More thorough testing and multiple bug fixes

M:N thread scheduler

  • M:N thread scheduler was introduced. [Feature #19842]
    • M Ruby threads are managed by N native threads (OS threads) so the thread creation and management cost are reduced.
    • It can break C-extension compatibility so that M:N thread scheduler is disabled on the main Ractor by default.
      • RUBY_MN_THREADS=1 environment variable enables M:N threads on the main Ractor.
      • M:N threads are enabled on non-main Ractors.
    • RUBY_MAX_CPU=n environment variable sets maximum number of N (maximum number of native threads). The default value is 8.
      • Since only one Ruby thread per Ractor can run at the same time, the number of native threads will be used, which is the smaller of the number specified in RUBY_MAX_CPU and the number of running Ractors. So that single Ractor applications (most of applications) will use 1 native thread.
      • To support blocking operations, more than N native threads can be used.

Other Notable New Features

Language

Performance improvements

  • defined?(@ivar) is optimized with Object Shapes.
  • Name resolution such as Socket.getaddrinfo can now be interrupted (in environments where pthreads are available). Feature #19965
    • For this purpose, a pthread is now created whenever calling getaddrinfo or getnameinfo. This incurs some overhead in name resolution (about 2.5x in our experiments). We do not expect the name resolution overhead to be a problem for most applications, but if you observe such, or if you see unexpected affects that you believe are due to this change, please report them.
  • Environment variable RUBY_GC_HEAP_REMEMBERED_WB_UNPROTECTED_OBJECTS_LIMIT_RATIO has been added. Feature #19571
  • Children of old objects are no longer immedately promoted to the old generation in the garbage collector. Feature #19678
  • Support for weak references has been added to the garbage collector. Feature #19783

Other notable changes since 3.2

IRB

IRB has received several enhancements, including but not limited to:

  • Advanced irb:rdbg integration that provides an equivalent debugging experience to pry-byebug (doc).
  • Pager support for ls, show_source and show_cmds commands.
  • More accurate and helpful information provided by the ls and show_source commands.
  • Experimental autocompletion using type analysis (doc).
  • It is now possible to change the font color and font style in the completion dialog by a newly introduced class Reline::Face (doc)

In addition, IRB has also undergone extensive refactoring and received dozens of bug fixes to facilitate easier future enhancements.

Compatibility issues

Note: Excluding feature bug fixes.

Removed constants

The following deprecated constants are removed.

Removed methods

The following deprecated methods are removed.

Removed environment variables

The following deprecated methods are removed.

  • Environment variable RUBY_GC_HEAP_INIT_SLOTS has been deprecated and is a no-op. Please use environment variables RUBY_GC_HEAP_{0,1,2,3,4}_INIT_SLOTS instead. Feature #19785

Stdlib compatibility issues

ext/readline is retired

  • We have reline that is pure Ruby implementation compatible with ext/readline API. We rely on reline in the future. If you need to use ext/readline, you can install ext/readline via rubygems.org with gem install readline-ext.
  • We no longer need to install libraries like libreadline or libedit.

C API updates

Updated C APIs

The following APIs are updated.

Removed C APIs

The following deprecated APIs are removed.

Standard library updates

RubyGems and Bundler warn if users require gem that is scheduled to become the bundled gems in the future version of Ruby.

Targeted libraries are:

  • abbrev
  • base64
  • bigdecimal
  • csv
  • drb
  • getoptlong
  • mutex_m
  • nkf
  • observer
  • racc
  • resolv-replace
  • rinda
  • syslog

The following default gem is added.

  • prism 0.15.1

The following default gems are updated.

  • RubyGems 3.5.0.dev
  • base64 0.2.0
  • benchmark 0.3.0
  • bigdecimal 3.1.5
  • bundler 2.5.0.dev
  • cgi 0.4.0
  • csv 3.2.8
  • date 3.3.4
  • delegate 0.3.1
  • drb 2.2.0
  • english 0.8.0
  • erb 4.0.3
  • etc 1.4.3.dev.1
  • fcntl 1.1.0
  • fiddle 1.1.2
  • fileutils 1.7.2
  • find 0.2.0
  • getoptlong 0.2.1
  • io-console 0.6.1.dev
  • irb 1.8.3
  • logger 1.6.0
  • mutex_m 0.2.0
  • net-http 0.4.0
  • net-protocol 0.2.2
  • nkf 0.1.3
  • observer 0.1.2
  • open-uri 0.4.0
  • open3 0.2.0
  • openssl 3.2.0
  • optparse 0.4.0
  • ostruct 0.6.0
  • pathname 0.3.0
  • pp 0.5.0
  • prettyprint 0.2.0
  • pstore 0.1.3
  • psych 5.1.1.1
  • rdoc 6.6.0
  • reline 0.3.9
  • rinda 0.2.0
  • securerandom 0.3.0
  • shellwords 0.2.0
  • singleton 0.2.0
  • stringio 3.0.9
  • strscan 3.0.7
  • syntax_suggest 1.1.0
  • tempfile 0.2.0
  • time 0.3.0
  • timeout 0.4.1
  • tmpdir 0.2.0
  • tsort 0.2.0
  • un 0.3.0
  • uri 0.13.0
  • weakref 0.1.3
  • win32ole 1.8.10
  • yaml 0.3.0
  • zlib 3.1.0

The following bundled gem is promoted from default gems.

  • racc 1.7.3

The following bundled gems are updated.

  • minitest 5.20.0
  • rake 13.1.0
  • test-unit 3.6.1
  • rexml 3.2.6
  • rss 0.3.0
  • net-imap 0.4.4
  • net-smtp 0.4.0
  • rbs 3.2.2
  • typeprof 0.21.8
  • debug 1.8.0

See GitHub releases like Logger or
changelog for details of the default gems or bundled gems.

See NEWS
or commit logs
for more details.

With those changes, 5207 files changed, 284820 insertions(+), 174773 deletions(-)
since Ruby 3.2.0!

Download

  • https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.0-preview3.tar.gz

    SIZE: 21550473
    SHA1: 2811f191d66dffee0206771873bd990857ae4ed6
    SHA256: 0969141be92e67e0edb84a8fb354acc98f01bd78e602a23a0f136045c82f4809
    SHA512: 94db07a6958c09809b2e5b597fa55a121074e8bacb3bf588c83cf0d35b07a8b070172035a49d1abf0d8ee364a9ace824f34e677f7327ffe1acdbab0938ac49c4
    
  • https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.0-preview3.tar.xz

    SIZE: 15970144
    SHA1: 496600612605f8ebeb955255e98bac73a4cbc045
    SHA256: f79afcf122dc7d04fe26cfa4436b9c488b21766fc54b0d2dfb2ba41cd0cdd355
    SHA512: d7ab0d703e7884efd31045933409cd68fac1d9941963537ccc8e309ca7c8bee8500a68182135acba22cbdbf4a8ae99f39bf7f0925273eb4fbc3728c0c1ba0c19
    
  • https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.0-preview3.zip

    SIZE: 26618303
    SHA1: 6a13e08c7e484d42037c1e2c87c5d0e220f893a0
    SHA256: c35bf637a647c2f60148368ffb374db5c258570911794f46b6dfdb98ebfe95d9
    SHA512: c4ef2cdcdadeb85ad1d42aedc97f9f3d609b3b01eea2319451cf92c81bd31ae8129b7c91fc68571469dd888c01ea0f48f73234b965db17f6a87404ca382f7794
    

What is Ruby

Ruby was first developed by Matz (Yukihiro Matsumoto) in 1993,
and is now developed as Open Source. It runs on multiple platforms
and is used all over the world especially for web development.

Posted by naruse on 12 Nov 2023

Who’s Your Daddy – Saçmalamasyon Ailesi

Gitaristv: https://www.youtube.com/channel/UCWIhR0c9M6i5bT7v_1UMh7Q
Minecraft Diğer Harika Modları İçin Tıkla
— Handaşlar Desteklerinizden Dolayı Çok Teşekkür Ederim Hepinizi Çok Seviyorum İyi Seyirler ¦
— Daha Fazla Oyun Videosu İstiyorsanız Handaşlar Like Atmayı Unutmayın ¦
— Değerli Yorumlarınızı Bekliyorum Handaşlar ¦
Ayrıcalıklardan yararlanmak için bu kanala katılın:
https://www.youtube.com/channel/UCpcHFJwDFlrnbCw3yD-4Wzg/join

CANIM HANDAŞ AİLEM BİZLERİ DESTEKLEDİĞİNİZ HER GÜN GELEN VİDEOLARIMIZI İZLEYİP LİKE ve YORUM ATTIĞINI İÇİN HEPİNİZE SONSUZ TEŞEKKÜR EDİYORUM.
SİZLER SAYESİNDE BURADAYIZ VE SİZLER SAYESİNDE HEDEFİMİZE ULAŞACAĞIZ 10 MİLYON HANDAŞ AİLESİNE ULAŞMAK İÇİN ELİMİZDEN GELENİ YAPACAĞIZ.
SİZLERDE HANDAŞ AİLEMİZE KATILMAYI VE BİZLERE DESTEK VERMEYİ LÜTFEN UNUTMAYIN
—————————————————————————————————————————————-
– SOSYAL MEDYA HESAPLARIM –
-Discord : https://discord.gg/sttQ7WUJ
– Katılmak için: https://bit.ly/3w2a5TV
-İnstagram : https://bit.ly/37ftx50
-Tiktok : https://bit.ly/3CEky95
-2.Kanal : https://bit.ly/3hZrggC
– HAN KANAL DİĞER VİDEO SERİLERİM –
– PoppyPlayTime: https://bit.ly/3JdC9r1
– Roblox: https://bit.ly/3KC7kfZ
—————————————————————————————————————————————-

[OPEN 인터뷰]기타로 세계 1등 조대연…손톱에 탁구공 붙이고 우승?

Q. 가수들은 대회를 앞두고 있으면 목이 제일 중요하겠죠? 목 컨디션이 기타리스트는 뭐가 제일 중요합니까?

Q. 손톱 관리하는 모습을 볼 수 있을까요?

Q. 이번 대회 준비하면서 큰일 날 뻔했다면서요?

Q. 허벅지 부상 이런 게 생기는 거군요?

Q. 피크랑은 비교가 안 되는 거죠?

Q. 옆에서 볼 때 “너무 연습 많이 하는 거 아니야?“ 할 정도로 연습해 본 적 있나요?

Q. 주변에서 뭐라고 안 해요? 피를 튀기면서 하면요?

Q. 기타리스트인데 왜 기타가 없었어요?

poke @ Savannah: Debuggers and Analysis Tools CfP @ FOSDEM 2024

Guinevere Piazera Larsen sent us the CfP for the upcoming Debuggers and Analysis Tools at FOSDEM 2024!:

We are excited to announce that the call for proposals is now open for the Debuggers and Analysis Tools developer room at the upcoming FOSDEM 2024, to be hosted on Saturday, February 3rd 2024 in Brussels, Belgium.

This devroom is a collaborative effort and is organized by dedicated people from projects such as GDB, SystemTap, Valgrind, GNU poke, Elfutils, binutils, Libabigail, and the like.

Important Dates:

   1st December 2023    Submission deadline

   8th December 2023    Acceptance notifications

   15th December 2023   Final Schedule announcement

   3rd February 2024    Conference dates

## CFP Introduction

This devroom is geared towards authors, users and enthusiasts of Free Software programs involved with debugging and analyzing ELF programs using all the binary information available (including DWARF data).

The goal of the devroom is for developers to get in touch with each other and with users of their tools, have interesting and hopefully productive discussions, and finally what is most important: to have fun.

The format of the expected presentations will cover a range that

includes:

    * Talks oriented towards developers of these projects

    * Presentation / Introductory Workshops for users of these programs

    * Activities oriented towards collaboration & standardization between these programs

All presentation slots are 25 minutes, with 15 minutes recommended for presentations, and 10 minutes for Q&A. This way we can have 8 slots and bio breaks, covering many topics!

### What is FOSDEM?

*FOSDEM is a free event for software developers to meet, share ideas and collaborate.*

Every year, thousands of developers of free and open source software from all over the world gather at the event in Brussels.

FOSDEM 2024 will take place on Saturday 3 and Sunday 4 February 2024.

It will be an in-person event at the *ULB Solbosch Campus, Brussels, Belgium, Europe.* If you aren’t there, you can watch the live streams from the main tracks and developer rooms.

### Important stuff:

– FOSDEM is free to attend. There is no registration.

– [FOSDEM website](https://fosdem.org/)

– [FOSDEM code of conduct](https://fosdem.org/2024/practical/conduct/)

– [FOSDEM Schedule](https://fosdem.org/2024/schedule/)

### Desirable topics:

In this devroom, we’re interested in any projects that directly reads binary files and analyses or manipulates them directly. Some projects and tools that fit the devroom are:

– GDB

– LLDB

– Ghidra

– Valgrind

– Dyninst

– GNU poke

– Binutils

– SystemTap

– Elfutils

– Libabigail

– Radare2

And any other debugging or binary analysis tool or framework

projects that might be of interest to Free Software enthusiasts.

### Topic overlap

There are over 50 developer rooms this year, and multiple main tracks, so there may be overlap with some other events.

If the topic would fit more than one devroom, you are free to choose which to submit to, but we encourage you to consider the focus of the talk, and see which devroom is best matched.

Full list of devrooms

[here](https://fosdem.org/2024/news/2023-11-08-devrooms-announced/).

### How to submit your proposal

To submit a talk, please visit the [FOSDEM 2024 Pretalx

website](https://pretalx.fosdem.org/fosdem-2024/cfp).

Click *Submit a proposal*. Make sure you choose the “Debuggers and analysis tools” devroom in the track drop-down menu (so that we see it rather than another devroom’s organisers)

### What should be in your submission

– name

– short bio

– contact info

– title

– abstract (what you’re going talk about, supports markdown)

Optional:

– description (more detail description, supports markdown)

– submission notes (for the organiser only, not made public)

– session image (if you have an illustration to go with the talk)

– additional speaker/s (if more than one person presenting)

Afterwards, click “Continue”.

The second page will include fields for:

– Extra materials for reviewers (optional, for organisers only)

– Additional information about the speaker (optional).

– Resources to be used during the talk

All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded.

For example:

    “If my presentation is accepted for FOSDEM, I hereby agree to

license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License.

    Sincerely,

    <NAME>.”

Once you’ve completed the required sections, submit and we’ll get

back to you soon!

### Things to be aware of

  • The reference time will be Brussels local lime (CET)

<https://www.timeanddate.com/worldclock/belgium/brussels>

  • There will be a Q/A session after the talk is over.

  Please make sure that you will be available on the

  day of the event.

  • If you’re not able to attend the talk in-person, live stream links

  will be available on the FOSDEM schedule page:

<https://fosdem.org/2024/schedule/>.

  • FOSDEM Matrix channels are specific to each devroom,

  the general link is: </#/#fosdem:fosdem.org>

  • *Matrix bridge to the LibreSOC IRC channel*:

<https://matrix.to/#/#_oftc_#libre-soc:matrix.org>


### Contact

If you have any question about this devroom, please send a message to debuggers-and-analysis-devroom-manager at fosdem dot org.

Organizers of the devroom can also be reached on IRC at #dadevroom@irc.libera.chat

A quick look back at the official announcement of Microsoft Windows 1.0 40 years ago today

The year was 1983. Microsoft was slowly becoming a well-known tech company in the PC space. Two years before, in 1981, Its MS-DOS operating system would be installed in the first IBM PC. It launched its first-word processing program, Word, earlier in 1983, along with its first Microsoft Mouse product. It even made Mac and PC hardware expansion cards. However, 40 years ago today, on November 10, 1983 at a press event in New York City, Microsoft first revealed its plans to launch an all-new graphical user interface-based PC operating system. The company called the OS Windows. If you’ve ever used Windows 1.0 – either because you’re old and remember it as new, or in a VM – you’ll know just how limited and useless Windows 1.0 really was. Still, it set the stage for one of the most successful tech products of all time, and few products in tech can boast about being on the market for four decades. That being said, I’m not exactly sad Windows seems to be in its twilight years.