Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend project to include server side APIs. #268

Closed
cakey opened this issue Aug 16, 2012 · 8 comments
Closed

Extend project to include server side APIs. #268

cakey opened this issue Aug 16, 2012 · 8 comments

Comments

@cakey
Copy link

cakey commented Aug 16, 2012

Bit of a curve ball idea, (and sorry if it's not the right place, I briefly looked for a google group/irc etc )...

The other half of client side development is generally going to be an accompanying REST API. There might be merit in piggy backing off the success and exposure of todomvc's framework comparison for the client side, to showcase comparisons of the different code needed to get a basic todo rest api implemented in various languages and frameworks.

The comparison would span a number of popular langauges, frameworks and app/modules/plugins for those frameworks, similar to the client side. For example, nodejs express, ruby rails, scala play, python django etc. I feel this projects targets people that are competent programmers, happy to switch between languages and frameworks, and use this site to get a flavour of everything, to quickly start with something that looks appealing to their preferred style. In that sense, it seems to make sense to extend the comparison.

It might be nice to make the client side and server side apis match, but I don't feel that matters.

I'd be quite happy to work on a few initial implementations if this was a road the community felt it was worth exploring.

Ben

@sindresorhus
Copy link
Member

We've been discussing this for a while, and it's very likely this is happening.

Addy current has a bunch of server-side implemenetations in his backbone-boilerplates project which we might make use of. If you see something missing there, feel free to open a ticket and if accepted, submit a PR.

@cakey
Copy link
Author

cakey commented Aug 16, 2012

Ah awesome! (I really didn't look hard enough!) Looks fairly light on python from a brief look, so I'll see what I can do there.

@sindresorhus
Copy link
Member

Yes, I also thought so too. I was going to create a Django app, but seeing as my time is limited and it would be better to wait on Django 1.5 with Python 3 support, it never happened. Feel free to take on that when the time is right. I opened an issue about it at addyosmani/backbone-boilerplates#12

Are there any other Python frameworks we should feature? Flask?

@addyosmani
Copy link
Member

@cakey @sindresorhus The boilerplates project is definitely in need of more Python. I'll add some Flask references to the ticket that was opened.

@addyosmani
Copy link
Member

For 2.0 (probably not 1.1) I think it'll be useful to bring backbone-boilerplates under the TasteJS org and try to look at upgrading them to the newer template. We might also need to figure out if there's a special app specification that needs to be written for handling those. Right now its fairly loose, relying on the TodoMVC 0.4/0.5 template and a readme for setting up the stack being used. I also wonder whether the project should be renamed or just fold into TodoMVC somehow.

todomvc-stacks maybe? or something.

@sindresorhus
Copy link
Member

TodoMVC Stacks would work, or a /server folder in TodoMVC, not sure. I also feel strongly that we should be clear about only wanting the most popular frameworks for this.

The current App Spec can be mostly reused, with some additions to how the back-end API should be modeled.

@addyosmani
Copy link
Member

We've decided to address this is a new repo under TasteJS. Closing.

@devinrhode2
Copy link

Perfect name: RestMVC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants