Re:New Languages Considered Harmful: "Learning new languages...
by jjburka on Friday April 04, 2008 @09:41AM
(#154765)
I think really what he is arguing is the marginal benefit of learning a new language diminishes with each new language. Which is probably true if you only learn the syntax and then move on. But thats not what software development is ,the language is a tool that a culture uses. Using your example with Rails , alot of its culture (MVC , TDD , etc) seem to be being adopted in other communities. I would argue that the reason is someone had a extended vacation in Hotel Rails liked what they saw and then brought it home. Finding out how different people do different things and adapting them to your needs is valuable in all contexts.
[ Parent
| on HN ]
Re:New Languages Considered Harmful: "Learning new languages...
by jrockway on Friday April 04, 2008 @12:30PM
(#154950)
Rails isn't really MVC, though.
Re:New Languages Considered Harmful: "Learning new languages...
by jjburka on Friday April 04, 2008 @01:06PM
(#154994)
how so? I'm rather new to rails and from my understanding of rails and mvc it seems to follow that pattern. Good Practice wise atleast
Re:New Languages Considered Harmful: "Learning new languages...
by jrockway on Saturday April 05, 2008 @04:02AM
(#155562)
In real MVC, you want to put everything related to your business rules, storage access, etc. in your model. Then you wrap the View and Controller around that as a very thin web <-> model glue. That's all a web framework should do, web-enable your model classes. Things that should not happen in the Controller include touching the ORM (or SQL queries), validating input, any business logic, etc. Just pass the request to the right model, see if the model did what you asked, and display the success page or the error page.
Here's a short talk I wrote on the subject: