amber VS sorbet

Technologically robust, making use of open source frameworks that ensure scalability of usage and auditability of the codebase. So, no PHP-based rickety structures or the secret devising of some lone wolf developer. This can't be trusted by anyone: its development must be done in the public repositories. Consider using a Crystal framework such as Amber, which is a compiled-to-binary Ruby clone, lightning-fast (it can handle over 1 million+ requests per second) and compatible with the expansive Rails ecosystem. Or any other solid language base, such as Go or Java.

I'm in a similar situation with the Amber Framework. I'm not one of the original creators of Amber, I just took it over last year (2022). So I have a decent size code base to maintain with potential for breaking changes.

I'd love to see two docs there:

- What's different from Lucky https://luckyframework.org/

- What's different from Amber https://amberframework.org/

Amber : https://amberframework.org/

hey r/webdev, i have a side project i want to make, where users with different logins can upload music files onto a server via ftp, and listen to it back via mpd. I've decided for the meantime, on using the [amber framework](https://amberframework.org/). Each user will have a basic username/password login with *optional* OTP sent via email, a specific limit on the amount of storage they get (say, 5-10Gb), and a user-specific mpd connection\*

https://luckyframework.org/ one of the web frameworks available in Crystal. There's also Amber, Grip, and SpiderGazel (the most Rails-like).

Amber

Well, I guess have something to share with you! https://github.com/amberframework/amber

https://amberframework.org/

There are two pretty big web frameworks in the Crystal world right now, one is Kemal which strives to be the Sinatra or Flask of the Crystal world (lightweight, supporting plugins), and the other is Crystal which is trying to be the Ruby on Rails or Django of the Crystal world (full-featured, opinionated).

Not part of the official language spec, but Ruby has Sorbet, from a company who employs Ruby core contributors and helped with the recently released JIT additions to the language, amount countless other contributions over the last couple decades.

https://sorbet.org/

First let's introduce the tool: Sorbet is a gem developed by Stripe that aims to bring type notation syntax and type checking support for the Ruby ecosystem by utilizing the "Gradual typing" philosophy, it also provide type generation from YARD comments via the tapioca gem, allowing to grow alongside the already built Ruby codebase.

We have hundreds of thousands of lines of ruby code spanning many services / monoliths. Even now I find it somewhat annoying to open a controller / component that is basically an empty class def but somehow executes a bunch of complex stuff via mixins, monkey patches etc, and you have to figure out how.

We are turning to https://sorbet.org/ to reign in the madness. I'm keen to know if others are doing the same, and how they are finding it (pros and cons)

According to https://sorbet.org/ , the vast majority of code at Stripe is written in ruby.

Caso de Stripe, que tuvo que inventar Sorbet para tener type checking en ruby.

> I guess what I'm asking is: do you see a future where there is more explicit control afforded to people who want to pick their own tradeoffs without resorting to writing everything performance-sensitive in extensions written in C/Rust/whatever?

An approach exists already in the present, and it's Stripe's Sorbet AOT compiler (https://github.com/sorbet/sorbet/tree/master/compiler).

That's incorrect. You may be thinking of Stripe, and AFAICT it's not very actively developed anymore: https://github.com/sorbet/sorbet/commits/master/compiler