Announcement

Collapse
No announcement yet.

Ruby 3.3 Released With New "Prism" Parser & Pure-Ruby JIT Compiler

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Ruby 3.3 Released With New "Prism" Parser & Pure-Ruby JIT Compiler

    Phoronix: Ruby 3.3 Released With New "Prism" Parser & Pure-Ruby JIT Compiler

    Out for Christmas is Ruby 3.3 as a big update to this dynamic open-source programming language. With Ruby 3.3 the Prism parser is added as well as a new pure-Ruby just-in-time (JIT) compiler...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Worst. Language. Ever.

    Comment


    • #3
      Originally posted by uid313 View Post
      Worst. Language. Ever.
      you are so eloquent and detailed

      Comment


      • #4
        Originally posted by szymon_g View Post

        you are so eloquent and detailed
        Well it looks like Perl and Python mixed with acid into some unholy mess.

        All double colon things, lots of weird syntax, and where all other languages call things null, Ruby calls it nil because hey its cool to be different, right?

        I am not sure Ruby sit above or below Perl and Tcl on the tier list of languages, but it definitely is low down on the list.

        Comment


        • #5
          Ruby would be ok as a cleaned up and slightly modernized Perl. If it weren't for the monumentally bad design decision that strings and their symbolized forms do not match as hash keys. This alone must have cost millions and millions due to stupid bugs when you got a hash key as a string, try to access the value and get nil because the value was stored under a symbolized keys. What were they thinking?

          Comment


          • #6
            Originally posted by uid313 View Post

            [...] and where all other languages call things null, Ruby calls it nil because hey its cool to be different, right?
            Tbf so does Lua

            Comment


            • #7
              I can see how Ruby could have a place in a world where there was only C, C++, Perl, Tcl, PHP 4, and JavaScript at the state it was during the Netscape era.
              Ruby is just arguably better than Perl which is awful.

              Originally posted by niner View Post
              Ruby would be ok as a cleaned up and slightly modernized Perl. If it weren't for the monumentally bad design decision that strings and their symbolized forms do not match as hash keys. This alone must have cost millions and millions due to stupid bugs when you got a hash key as a string, try to access the value and get nil because the value was stored under a symbolized keys. What were they thinking?
              Crazy!

              Originally posted by fong38 View Post

              Tbf so does Lua
              But at least Lua has some redeeming qualities. It has great interoperability with C and it is very fast. It has a common, established open source license, the MIT License, not a vanity license, the Ruby License.

              Comment


              • #8
                Originally posted by fong38 View Post

                Tbf so does Lua
                Plenty of other languages do too including Lisp, Objective-C, Swift, Pascal and Erlang. Whining about superficial things like this is the worst form of language criticism.

                Comment


                • #9
                  Ruby is so nice to actually work in, at least for the small-to-medium scripts and custom DSLs I use it for. I find it chock-full of pragmatic choices and assists that make development faster and simpler. I don’t use Rails so don’t know anything about that world.

                  Comment


                  • #10
                    Everyone who code in Ruby professionally or long enough knows the bad parts:
                    • Excessive usage of meta-programming turns code into undebugable magic
                    • Performance issues in edge cases or when you do stupid things like n+1
                    • Memory issues when you really don't understand how much objects you produce
                    That's all, nothing in syntax or language itself is bad to the level of language design flaw.

                    Comment

                    Working...
                    X