5 ms·

Please name a few with the same comfort of having most things built-in. One example: database migrations. In the JS world it is knex all over and it is much les

Please name a few with the same comfort of having most things built-in. One example: database migrations. In the JS world it is knex all over and it is much less comfortable than ActiveRecord.

arrowsmith 3y ago
Phoenix
- michaelteter 3y ago
  With Ash, even more attractive.
  - arrowsmith 3y ago
    I really need to check Ash out, it seems be a rising star!
Rapzid 3y ago
Personally I would rather use Fastify+MikroORM. Or Asp.Net. Or Flask with SqlAlchemy + the migration and validation libs(marshmallow?) Or whatever is good in Golang.
- fredrikholm 3y ago
  > Or whatever is good in Golang. There is no such thing in Go and most likely will never be given the perspectives held by the greater Go community (less is more). Comparatively, the Ruby community is the complete inverse: any perceived friction can and should be abstracted to be (subjectively) nicer. It's why some people love the language, and it's also why some people dislike the language.
- 0xblinq 3y ago
  And none of those combinations reach 5% of the features Rails provides. These answers are incomplete and hide the underlying problem: You have to tie together 10s of third party libraries or services, or alternatively reinvent the wheel and implement everything from scratch. That's the point.
  - Rapzid 3y ago
    Asp.Net has 5% of the features of Rails? Which 5%? What of the 95% missing do you need?
    - 0xblinq 3y ago
      Sorry, I don’t know anything about Asp.net. My comment definitely applies to the other two options you listed.
winrid 3y ago
I wonder if anyone here has used ebean and the generated db migrations? I was looking for a java ORM that's like Django's ORM with the built in generated migrations tool which is great for a lot of projects - it seems like ebean is pretty much the best choice? and now with virtual threads I don't have to worry that it's not reactive.
mvdtnz 3y ago
ASP.NET Core. And database migrations are not uncommon in web frameworks at all.
neonsunset 3y ago
Easily ASP.NET Core + EF Core combo thanks to strong typing which is a developer productivity boost in back-end, and performance on the opposite end of spectrum suitable for high scalability. (but then again, if you are doing complex migrations through framework in-language, you might be setting yourself up for failure)

Please name a few with the same comfort of having most things built-in. One example: database migrations. In the JS world it is knex all over and it is much less comfortable than ActiveRecord.

arrowsmith 3y ago

Phoenix

michaelteter 3y ago
With Ash, even more attractive.
- arrowsmith 3y ago
  I really need to check Ash out, it seems be a rising star!

Rapzid 3y ago

Personally I would rather use Fastify+MikroORM. Or Asp.Net. Or Flask with SqlAlchemy + the migration and validation libs(marshmallow?) Or whatever is good in Golang.

fredrikholm 3y ago
> Or whatever is good in Golang. There is no such thing in Go and most likely will never be given the perspectives held by the greater Go community (less is more). Comparatively, the Ruby community is the complete inverse: any perceived friction can and should be abstracted to be (subjectively) nicer. It's why some people love the language, and it's also why some people dislike the language.
0xblinq 3y ago
And none of those combinations reach 5% of the features Rails provides. These answers are incomplete and hide the underlying problem: You have to tie together 10s of third party libraries or services, or alternatively reinvent the wheel and implement everything from scratch. That's the point.
- Rapzid 3y ago
  Asp.Net has 5% of the features of Rails? Which 5%? What of the 95% missing do you need?
  - 0xblinq 3y ago
    Sorry, I don’t know anything about Asp.net. My comment definitely applies to the other two options you listed.

winrid 3y ago

I wonder if anyone here has used ebean and the generated db migrations? I was looking for a java ORM that's like Django's ORM with the built in generated migrations tool which is great for a lot of projects - it seems like ebean is pretty much the best choice? and now with virtual threads I don't have to worry that it's not reactive.

mvdtnz 3y ago

ASP.NET Core. And database migrations are not uncommon in web frameworks at all.

neonsunset 3y ago

Easily ASP.NET Core + EF Core combo thanks to strong typing which is a developer productivity boost in back-end, and performance on the opposite end of spectrum suitable for high scalability. (but then again, if you are doing complex migrations through framework in-language, you might be setting yourself up for failure)