You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My idea here is more like ... what if ramaze would become a bit more of a "do-it-yourself"
project? That is, you retain how it is, or perhaps even fix things here and there, but
a bit like a project that shows and demonstrates to people how things work internally.
With that I don't just mean to explain the examples, but actually the code in ramaze
itself, "what makes ramaze work". A bit like the old "Die Sendung mit der Maus" (but
only the variant with Armin Maiwald, his voice was great).
That way people could learn the inner workings of a web framework. Neither rails
nor sinatra do this as-is - there are of course books, but just about all these books do
is to NEVER explain the inner workings.
This does not necessarily have to document EVERYTHING, but more the main implementation
points, e. g. "this is how a controller works internally", and then the gist of it explained.
Not sure if this is worth your time, of course, but I just wanted to mention it nonetheless.
Please feel free to close this issue request at any moment in time!
The text was updated successfully, but these errors were encountered:
Sers manveru,
I know you abandoned ramaze a long time ago, even though I see you still doing
some changes every now and then, such as here:
59b0870
I am also reading your blog entries every now and then at https://manveru.dev/blog/!
Anyway.
My idea here is more like ... what if ramaze would become a bit more of a "do-it-yourself"
project? That is, you retain how it is, or perhaps even fix things here and there, but
a bit like a project that shows and demonstrates to people how things work internally.
With that I don't just mean to explain the examples, but actually the code in ramaze
itself, "what makes ramaze work". A bit like the old "Die Sendung mit der Maus" (but
only the variant with Armin Maiwald, his voice was great).
That way people could learn the inner workings of a web framework. Neither rails
nor sinatra do this as-is - there are of course books, but just about all these books do
is to NEVER explain the inner workings.
This does not necessarily have to document EVERYTHING, but more the main implementation
points, e. g. "this is how a controller works internally", and then the gist of it explained.
Not sure if this is worth your time, of course, but I just wanted to mention it nonetheless.
Please feel free to close this issue request at any moment in time!
The text was updated successfully, but these errors were encountered: