News for hackers. Stuff that matters.
Re:Rubysyn: Clarifying Ruby's Syntax and Semantics by amomchilov on Sunday April 05, 2026 @08:31AM (#47648704)
I never understood the appeal of this talking point. It’s just an accounting trick that moves the complexity to the standard library.

For example, SmallTalk is a class based OO system, yet this postcard doesn’t slow you how to create a class.

Re:Rubysyn: Clarifying Ruby's Syntax and Semantics by petalmind on Sunday April 05, 2026 @08:39AM (#47648781)
Yeah, I was also going to say that conflating trivial syntax and "supremely easy to learn" is a very weak flex.

The first Smalltalk-80 book you randomly find is 560 pages.

Also, there is a weird bargaining with "but not block temporaries" and "not an instance variable". Why not? Half of the postcard is basically empty. Also, "except primitives" — how many primitives are there?

Re:Rubysyn: Clarifying Ruby's Syntax and Semantics by Smalltalker-80 on Sunday April 05, 2026 @09:09AM (#47649047)
The appeal of having a very simple, base syntax and almost everything in the library / primitives, would be that code is always easy to read and write, also on the 'reflection' level, where most languages have specific keywords that cannot be used 'first class' with the rest of the language. E.g: Types next to class objects or operator overloading, look at Swift.. (Of course the complexity of a full working system (library) does not disappear in Smalltalk, it's just easier to read and modify. :)
Re:Rubysyn: Clarifying Ruby's Syntax and Semantics by petalmind on Sunday April 05, 2026 @09:18AM (#47649154)
> on the 'reflection' level, where most languages have specific keywords that cannot be used 'first class' with the rest of the language.

In Ruby this is also the other way around, and it's one of my pet peeves.

`Kernel#callcc` looks like a method (arguably, of a special class), yet it's impossible to re-implement directly in the language, as far as I can tell.

Same with `raise`, I keep forgetting that it's not a keyword even.

Re:Rubysyn: Clarifying Ruby's Syntax and Semantics by decasia on Sunday April 05, 2026 @09:38AM (#47649331)
Yeah, I just discovered this and was also amazed.

https://decasia.org/tech/2026/02/raise-not-a-reserved-word.h...

This being said, I don't think there is any requirement technically that every core method can also be re-implemented in Ruby... There are so many methods that are just thin interfaces to something written in C, whether because they are touching VM internals, or for perf reasons, or because they make system calls or call external libraries.

Re:Rubysyn: Clarifying Ruby's Syntax and Semantics by petalmind on Sunday April 05, 2026 @10:00AM (#47649552)
You reimplement `while` in terms of `loop`, but do you know that `loop` is also a method :)
Re:Rubysyn: Clarifying Ruby's Syntax and Semantics by amomchilov on Sunday April 05, 2026 @08:55AM (#47648927)
Next up: “all the characters you need fit on a single keyboard!”
Re:Rubysyn: Clarifying Ruby's Syntax and Semantics by chihuahua on Sunday April 05, 2026 @01:12PM (#47651530)