Studying users

[EduardoRFS]

Ruby stdlib, mostly utils, same name to make easy of finding(think filter and find_all).

Java builder pattern. Lambda in Python is bad. Lambda with context in Kotlin.

Ruby is great for DSLs, common lib in DSLs.

Python is like ruby, but worse. Import system in Python is better than Ruby, Ruby recursively imports everything(reminds me of OCaml). Import system in Ruby, no LSP for imports. Auto import in Rails.

Don't mind Python syntax, don't mind whitespace sensitivity.

Operator overloaded in Ruby.

Type system in Kotlin, null safety. Kotlin constraints. Kotling DSLs, use case similar to Ruby but different to define, json { blablabla }, related to lambda with context.

It should be elegant and it should be fast. Go is ugly, Kotlin is nice.

Kotlin auto setting. Kotlin data class.

Active record is disgusting.

Database split domain from database data. Like the model data mapper, automatic data mapping. Hanami framework.

JPA create magic queries based on the name of the function(find_all_record), magic is interesting but kind of bizarre.

Like an intermediary between Rails and Sinatra, mix and matching such as different ORM and logs.

Played a bit with Haskell in the APDA, Hackerrank using Haskell, got some of the vibe from Haskell.