Re: [9fans] Rails? (was Re: web server)
On Thu, Apr 16, 2009 at 2:51 PM, erik quanstrom quans...@quanstro.net wrote: without some constraints on the data, you can't show that your design works. without some idea of what the data could be, how do you pick appropriate algorithms? The point of the model is to enforce constraints. It is the gateway to the data store. The algorithms are part of the model code. and then two weeks later the director of marketing would be in my office talking about his new idea. it was uncanny how it managed to always ask for something we just couldn't do. Rails' model library gets bigger and bigger all the time! -- Tom Lieber http://AllTom.com/
[9fans] Rails? (was Re: web server)
Just a thought. Is Rails even necessary? Other server-side alternatives do exist, and they can be written. IIRC, the author of rit mentioned it being used in his Pegasus server...
Re: [9fans] Rails? (was Re: web server)
2009/4/16 hiro 23h...@googlemail.com: What is the advantage of rails anyway? I had a quick glance, but still don't really understand it's function. MVC development model. Allows you to abstract the data from the code from the design, but easily access needed parts from other needed parts. One of the big things here is the ORM, which basically maps information in a database to native language objects. --dho
Re: [9fans] Rails? (was Re: web server)
On Thu, Apr 16, 2009 at 9:22 AM, Pietro Gagliardi pietr...@mac.com wrote: Is Rails even necessary? If all you have is an object, everything looks like a method. ;) -J
Re: [9fans] Rails? (was Re: web server)
On Apr 16, 2009, at 1:50 PM, Devon H. O'Dell wrote: MVC development model Good point. I think I'll get started porting Cocoa to Plan 9. =P
Re: [9fans] Rails? (was Re: web server)
On Thu Apr 16 13:52:22 EDT 2009, devon.od...@gmail.com wrote: 2009/4/16 hiro 23h...@googlemail.com: What is the advantage of rails anyway? I had a quick glance, but still don't really understand it's function. MVC development model. Allows you to abstract the data from the code from the design, but easily access needed parts from other needed parts. One of the big things here is the ORM, which basically maps information in a database to native language objects. call me ignorant, but i've always seen such a model (ha) as provable wrong. in fact, it seems so obviously wrong that i never thought much about it. without some constraints on the data, you can't show that your design works. without some idea of what the data could be, how do you pick appropriate algorithms? when i worked in the web world, i took a couple of stabs at this and usually things would be great for a little while. new business logic would fit just fine and life was good. and then two weeks later the director of marketing would be in my office talking about his new idea. it was uncanny how it managed to always ask for something we just couldn't do. - erik
