4 ms·

Have you taken a look at another Java-based framework www.scooterframework.com? All your experiences in Rails can be found there: ActiveRecord, associations, ro

Have you taken a look at another Java-based framework www.scooterframework.com? All your experiences in Rails can be found there: ActiveRecord, associations, routes, named sql queries, i18n, ajax, etc. I particularly like the one-click routes link. I think Scooter's routes which is based on Rails is much better. Also I like Scooter's ActiveRecord over Play's JPA. I just cannot tolerate annotations polluting my Java class everywhere.

alexdj 17y ago
Scooter is very impressive. I can almost convert my Rails app to Scooter-based app in Java line by line. ActiveRecord is awesome. I think that is probably why it took only 260 lines of Java code to write Twitter in Scooter.
- rufugee 17y ago
  Definitely looks interesting...I'm going to dive deeper. They really, really need a site re-design however. :/
- bad_user 17y ago
  Personally I think ActiveRecord is the weak link in Rails (2.x ... I see they are doing some fixing in 3.0). Coming from Hibernate and such, it may seem like a breath of fresh air, but the result of a find ain't lazy, the query language sucks making you drop to SQL even for sub-selects, and the model definitions look weird ... inferring the columns from the DB schema is the wrong approach IMHO (they should take a look at Django sometimes).
  - alexdj 17y ago
    Scooter framework allows you to use both ActiveRecord and direct sql queries which you either embed in code or list in sql.properties file. See http://www.scooterframework.com/docs/lovely_features.html#namedsql http://www.scooterframework.com/docs/lovely_features.html#na... Django is a nice framework. But don't you think that listing table columns in Django model code is a violation of DRY (Don't Repeat Yourself)? Database already holds meta data. Repeating it in model code is unnecessary.
    - bad_user 17y ago
      > But don't you think that listing table columns in Django model code is a violation of DRY (Don't Repeat Yourself)? Database already holds meta data. Repeating it in model code is unnecessary. No, because the columns definitions in Django are complete. You specify their meaning, not their internal representation. And you can also add your own types easily. In ActiveRecord you have to look at the DB schema for, well, the table definition, and you have to look again at the model's definition for validation rules or for relationship rules. It may be DRY, but it's not KISS. And I never have to work with the database schema directly, like writing SQL for the schema definition (I only drop to the db's console for debugging purposes, nothing else). A migration utility like South can detect the code-changes I've made and write the migrations for me.

alexdj 17y ago

Scooter is very impressive. I can almost convert my Rails app to Scooter-based app in Java line by line. ActiveRecord is awesome. I think that is probably why it took only 260 lines of Java code to write Twitter in Scooter.

rufugee 17y ago
Definitely looks interesting...I'm going to dive deeper. They really, really need a site re-design however. :/
bad_user 17y ago
Personally I think ActiveRecord is the weak link in Rails (2.x ... I see they are doing some fixing in 3.0). Coming from Hibernate and such, it may seem like a breath of fresh air, but the result of a find ain't lazy, the query language sucks making you drop to SQL even for sub-selects, and the model definitions look weird ... inferring the columns from the DB schema is the wrong approach IMHO (they should take a look at Django sometimes).
- alexdj 17y ago
  Scooter framework allows you to use both ActiveRecord and direct sql queries which you either embed in code or list in sql.properties file. See http://www.scooterframework.com/docs/lovely_features.html#namedsql http://www.scooterframework.com/docs/lovely_features.html#na... Django is a nice framework. But don't you think that listing table columns in Django model code is a violation of DRY (Don't Repeat Yourself)? Database already holds meta data. Repeating it in model code is unnecessary.
  - bad_user 17y ago
    > But don't you think that listing table columns in Django model code is a violation of DRY (Don't Repeat Yourself)? Database already holds meta data. Repeating it in model code is unnecessary. No, because the columns definitions in Django are complete. You specify their meaning, not their internal representation. And you can also add your own types easily. In ActiveRecord you have to look at the DB schema for, well, the table definition, and you have to look again at the model's definition for validation rules or for relationship rules. It may be DRY, but it's not KISS. And I never have to work with the database schema directly, like writing SQL for the schema definition (I only drop to the db's console for debugging purposes, nothing else). A migration utility like South can detect the code-changes I've made and write the migrations for me.