3 ms·
I take it you've never used Rails' scaffold generator ... it does much of what you speak of (db schema, basic html/css forms, etc.)
by callmeed 9y ago
I take it you've never used Rails' scaffold generator ... it does much of what you speak of (db schema, basic html/css forms, etc.)
- copperx 9y agoSure, but going from there to doing simple stuff (e.g., handling a file upload, authorization, client-side validation, client-side form modification [e.g., make a selection on this dropdown and this other dropdown changes], making the app multi-tenant) requires a lot of additional code, which should, IMHO, be part of the framework.
- tmzt 9y agoHmm, ask Equifax how simple file upload is. It's actually a pretty complex problem to solve securely, leading to scripts that try to support every configuration including off-the-shelf PHP hosting. An ideal would be something like S3 where invariants like size, type, file format could be verified at time of upload and then exposed in on-demand manner to the rest of the application.
- VeejayRampay 9y agoExactly my thought. It shows that Rails really grew organically from real-life business patterns as a way to automate the mundane. The Rails resource generator generates views, controllers, models, migrations and routes.
- davidjnelson 9y agoThat sounds useful. The thing is rails is just one of many frameworks. What if you're using a go backend for instance? Also, does the generation output single page apps for popular frameworks such as react and angular?
- flukus 9y agoThen you'd use another templating language for those languages or a generic one like m4.