when I was CTO of a company and someone joined, the first thing they had to do was to spend two weeks reading AWDwR from cover to cover. Once you know the framework, there is no magic, only defaults that act as a catalizer and let you fly.

string ones are those most of the Rubyists remember.

From day one, your team will love the familiarity of a spreadsheet, and the power of a database.

Familiarity: Volumes function as generic block devices, so you can treat attached volumes like locally connected storage drives. This lets you partition, format, and manage volumes with familiar tools and techniques.

The controllers feel very familiar to using ActiveRecord models

You stick with what you know. It's trouble free because you know how to use it. That's achievable on any of the main OSs, even (gasp!) Windows.

big companies feel more confident if the Linux distribution is being backed/supported by a known commercial entity.

Slots can already be pretty confusing to comprehend, I think it is better to stick to what people (may) already know.

Familiar npm inspired dependency management.

I have a few colleagues that converted to hyperscript, and while they were adverse at first, they were satisfied with having switched once they had become comfortable with the way it looks/reads.

The only "issue" it has is that its unfamiliar. People have been working with HTML for years and are comfortable with it. That's basically the only reason that people find it more readable. If you make an effort to spend sometime with hyperscript, it becomes as familiar and readable as jsx.

Make sure students can reach out to you privately to let you know if anything about the experience was uncomfortable for them.