@seesethcode
Glad to hear you're going to be trying out Athena!
I plan to personally highlight the differences I notice between the Crystal framework and Rails
I think you're going to find it is quite a bit different than Rails, and even the other Crystal frameworks. The main reason for this is it was inspired by non Ruby frameworks, which ultimately have different design patterns and stuff. The plus side to this is it brings some super cool and unique patterns/features to Crystal.
I will point out Athena, at this point in time, is better setup for RESTful APIs than server rendering HTML like you're wanting to make. It definitely can be used for that, but that's a less developed area so some built-in features may be lacking.
However, your exploration of that may be helpful in identifying some quick wins or areas that can be easily improved. I look forward to seeing what you think.
Kemal and Athena are much lighter weight and are better compared to a Sinatra type framework.
Athena is deff lighter on features compared to Lucky, but this is mainly related to Lucky being much more mature of a project while Athena is relatively young. I wouldn't compare it to Kemal tho, as that's more of a fancy router than a framework IMO.
Of course if you have any questions, run into any issues, or just want to chat about the overall architecture/design of Athena, etc feel free to join the gitter channel, or message me on Discord:
Yeah man I’ll reach out with any questions when I get to Athena! The goal here with comparing everything to Rails is specifically to use a very familiar perspective of development and show how the same type of functionality would be accomplished on a Crystal framework.
I get married in two weeks and then we close on our house in 4 weeks and move in 6 weeks, so it’ll probably be January or February before I get to doing the Athena framework
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
@seesethcode Glad to hear you're going to be trying out Athena!
I think you're going to find it is quite a bit different than Rails, and even the other Crystal frameworks. The main reason for this is it was inspired by non Ruby frameworks, which ultimately have different design patterns and stuff. The plus side to this is it brings some super cool and unique patterns/features to Crystal.
I will point out Athena, at this point in time, is better setup for RESTful APIs than server rendering HTML like you're wanting to make. It definitely can be used for that, but that's a less developed area so some built-in features may be lacking.
However, your exploration of that may be helpful in identifying some quick wins or areas that can be easily improved. I look forward to seeing what you think.
Athena is deff lighter on features compared to Lucky, but this is mainly related to Lucky being much more mature of a project while Athena is relatively young. I wouldn't compare it to Kemal tho, as that's more of a fancy router than a framework IMO.
Of course if you have any questions, run into any issues, or just want to chat about the overall architecture/design of Athena, etc feel free to join the gitter channel, or message me on Discord:
Blacksmoke16#0016Yeah man I’ll reach out with any questions when I get to Athena! The goal here with comparing everything to Rails is specifically to use a very familiar perspective of development and show how the same type of functionality would be accomplished on a Crystal framework.
I get married in two weeks and then we close on our house in 4 weeks and move in 6 weeks, so it’ll probably be January or February before I get to doing the Athena framework