Luca is a Passionate Programmer
A deep insight on why Ruby on Rails has revolutionized web development.
This talk will focus its attention on the Rails "Golden Path", the reasons to its success, the most common problems, and how its API can be improved.
We will learn to benefit from a tool as powerful as it is dangerous, how to mitigate architectural, design and testability implications for our applications and how to improve the quality of our code.
@author I see where you stand - I'm almost in the same situation :) I would suggest to also update the proposal description to reflect what you said above.
I work with Rails from the 0.x era, and have seen a lot of projects evolve during their lifespan. As you know, maintaing and improve software is hard, and sometimes the Rails doesn't make our life easy. Based on my experience (especially on legacy projects), I started maturing my own point of view about the framework, which is still great, but not perfect.
I want to talk about: * How the Golden Path advices can be helpful at the beginning, but dangerous when the codebase grows; * The Rails applications architecture that violates OOP principles and why this is bad for code modularity (main point – with a lot of bad practice examples and related solutions); * Testability issues (integration tests vs unit tests, slow test suites); * How Rails discourages emerging design.
PS: I already gave this talk to another conf, and got a great feedback about it.
In general: Criticism of Rails is literally everywhere. There are hundreds of blog posts about it and at least one talk at every conference is at least in parts dedicated to the topic. Personally, I've seen and read to much of this already.
But I agree with Nikos: Way to generic to make an informed decision of whether or not I want to see this talk. If you can at least outline what you intend to present in this talk and how it will differ from the wealth of blog posts and conference talks that are already out there, I might consider giving it a +1.
Hello there author! The proposal sounds more generic than I'ld like. Can you give some more concrete examples of what your talk is going to be about?