From: zverok.offline@... Date: 2021-05-13T07:44:33+00:00 Subject: [ruby-core:103825] [Ruby master Feature#17859] Start IRB when running just `ruby` Issue #17859 has been updated by zverok (Victor Shepelev). Two observations from my experience with Python: 1. Python (in the modern default installation, I believe) has _two_ consoles: `python` which loads instantaneously, has no syntax highlight, and very simplistic autocomplete; and `ipython` with rich autocomplete, cool syntax highlighting and whatnot, but takes some time to load. (See also @xtkoba's comment above about loading time) 2. When starting to work with Python after Ruby, I was constantly bugged with _undesired_ interpreter start, most notably when running `python -v` (trying to ask "what version of Python do I have?", with `-v` being almost universal shortcut for it, but instead having a full screen of gibberish, because it runs interpreter in verbose mode). It should be avoided. ---------------------------------------- Feature #17859: Start IRB when running just `ruby` https://bugs.ruby-lang.org/issues/17859#change-91943 * Author: deivid (David Rodr�guez) * Status: Open * Priority: Normal ---------------------------------------- Compare python: ``` $ python Python 3.8.3 (default, Jul 8 2020, 16:49:12) [GCC 7.5.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> ``` To ruby: ``` $ ruby # just hangs ``` I think firing up a console it's a good default behaviour for beginners. -- https://bugs.ruby-lang.org/ Unsubscribe: