3 ms·
This is incredibly cool. The template syntax you have going is awesome. Reminds me of the natural language of haml/ruby with the handy pipe filter stuff of djan
by whalesalad 14y ago
This is incredibly cool. The template syntax you have going is awesome. Reminds me of the natural language of haml/ruby with the handy pipe filter stuff of django/jinja. I can't stand mustache and handlebars.
The UI is great, it's responsive, and well thought out.
Also, the data modeling issue is a great selling point. Right now, MOST all applications are the same. Take this data, validate the person sending you the data is correct, validate the data is correct, and store it. Then apply the same methodology to fetching it, modifying it, or deleting it. I've been a django/python guy for years but after recently diving into Rails, I don't think anyone has done this any better. You can very quickly get things moving in CRUD/REST without much code.
That being said, it all comes back to the modeling. Modeling is relatively simple in Rails. The ORM you get with Django far exceeds ActiveRecord in usability but either way, at some point, a developer needs to sit down and define the data modeling. I realize you're marking this to developers (obviously) but I feel like with your cool UI and mongodb backing, you might even be able to expand this to administrators of the service.
Meaning, I can deliver a pre-configured product to my clients but if they want to add some fields to a product that are searchable/sortable/validatable/etc... they won't need to wait for me to do it. They won't need to wait for me to deploy it. I won't need to run a migration script.
Modern REST frameworks typically work based on a separation of a model and a resource. The model handles data storage and representation, and the resource handles serving it up, controlling access, etc... I think we need to couple these together. One unified object. I can create something, like a `Product`, give it some properties, set validations and permissions for those properties, and boom. Done.
Things like this and Meteor are shining examples of the radical change that we need in this current era of development. Yes, you guys will find faults in that statement. The neckbeards will come out and tell me mongodb does not scale, or node.js async development does not make sense. That is not the point. The point is that we're really not making it much easier on ourselves to build the things we want. Right now it makes more sense for me to pay Parse to handle an iOS back-end. Why? Because for the most part building it is a pain in the ass.
It doesn't need to be. I'm excited about Forward, very excited.
- randallsquared 14y agoI can't stand mustache and handlebars. Why do you dislike them? Separation of design and code seems pretty important, so having a template system that's really a (more or less limited) programming language of its own seems like a step backward to me.
- ericingram 14y agoI thought about this a lot, believe me. Is it right to allow a template to have so much control? The side effect of not having it is, designers can't do anything without a back-end programmer. Instead, Forward aims to make templates expressive and easy to understand by anyone. Time will tell if this causes problems, but for the projects we've built with it over the last year, it has been good and easy to maintain as there is no procedural connection between template/back-end.
- whalesalad 14y agoHonestly the django/jinja syntax and library of helpers/filters is virtually impossible to beat. ### Example User user: { name: "Michael", bio: "The quick brown fox jumped over the lazy dog.", products: [<Product>, <Product>, ... ] joined: "09-07-12" } <table> {% for user in users %} <tr class="{% cycle 'odd' 'even' %}"> <td class="user-name">{{ user.name }}</td> <td class="user-bio">{{ user.bio|truncatewords:3 }}</td> <td class="user-products">{{ user.products.count }} Product{{ user.products.count|pluralize }}</td> <td class="user-joined">{{ user.joined|date:"M jS, Y" }}</td> </tr> {% endfor %} </table> ### Would Display <tr class="odd"> <td class="user-name">Michael</td> <td class="user-bio">The quick brown ...</td> <td class="user-products">2 Products</td> <td class="user-joined">September 7th, 2012</td> </tr>
- ericingram 14y agoHere's what this would look like in Forward: <table> {foreach "/accounts"|get as $user} <tr class="{cycle values="odd, even"}"> <td class="user-name">{$user.name}</td> <td class="user-bio">{$user.bio|truncate:30}</td> <td class="user-products">{pluralize "{$user.products.count} Products"}</td> <td class="user-joined">{"M jS, Y"|date:$user.date_created}</td> </tr> {/foreach} </table>
- ericingram 14y agoIt's awesome to see that others are thinking about this stuff too, really, I'm excited you are excited. > you might even be able to expand this to administrators of the service. There is already a channel/entry system much like that of ExpressionEngine, and administrators can create new channels in the Admin, specify which fields belong in it, and start storing/searching documents without a line of code. Again, thanks to ExpressionEngine for the inspiration on that one. So far we've used channels to manage things like: Blogs, Knowledge base, Staff procedures, Bug reports, Customer reviews, and much more. It's early still but I expect the channel/entry thing to be a huge feature for administrators. Also for developers, channels/entries make it really easy to mockup new features without writing a new data model. For example... {put $params.custom_data in "/entries/custom-data"} It just works. This entry will appear in the Admin and can be fetched again with get("/entries/custom-data")
- rushabh 14y agoShameless plug, but I have been writing such a framework for quite sometime now. It has all the self-defining goodness you ask for - you can edit the models (a model is a model) via the admin interface. Also has an integrated front-end and back-end, so you can seamlessly share models in the client and push updates etc. https://github.com/webnotes/wnframework https://github.com/webnotes/wnframework Its complex and not documented. It is primarily built for an small business accounting + inventory app we publish (ERPNext, demo - http://demo.erpnext.com/ http://demo.erpnext.com/)