natalie VS Opal

Since I tried Sorbet, a Ruby type-checker, the idea of building an ahead-of-time compiler for Ruby is a cool side project that has been in my mind for some time now. To my surprise, during Hacktoberfest, I got to know Natalie, this AOT compiler written in C++ by Tim Morgan.

Unlike other languages, ruby is mainly driven by one application - Rails. As newer web FWs come, it's hard to see Rails keep up. The trends for Rails does not look good for the past 5 years [1]. I am hopeful that natalie [2] will work. If it does, it will remove the biggest downside to ruby.

[1] https://trends.google.com/trends/explore?date=today%205-y&q=...

[2] https://github.com/natalie-lang/natalie

Not the OP, but from what I remember they would seek out every possible opportunity in every single possible open source community they could find and propose the CoC that they wrote. 0 contributions to the projects, with the exception of demanding that people implement incredibly verbose CoC's in their projects under the guise of "protecting the minorities contributing to the projects".

Most infamous instance is probably this one, in the Opal repo: https://github.com/opal/opal/issues/941

As well as this thread in the Ruby issue tracker that devolves into pure chaos with Ada refusing to actually participate in any of the valid points others bring up: https://bugs.ruby-lang.org/issues/12004

And I'm sure there's many other instances if you look around a bit.

My experience with ruby for front end web dev is via https://opalrb.com/

Here's an example of the creator of the most adopted CoC (the Contributor Covenant) trying to get an open source contributor removed from a project due to his political opinions expressed on Twitter which she didn't like and found offensive.

So ruby has a JS transpiler - opal - https://opalrb.com/

I tried using it a little bit but the reality is if you need JS to make your app more interactable it's really worth it to just learn some JS. As soon as you need something complex the extra layer of abstraction just gets in the way and becomes more of a headache, and if you don't need anything complex then you don't need JS in the first place.

Advocating for removing a contributor for a statement on a different site, unrelated to the project, for example?

https://github.com/opal/opal/issues/941

Ruby can be transpiled to JavaScript :P Same as TypeScript is used a lot

There is already this project that I found which interprets ruby in JavaScript: https://github.com/opal/opal