> On Aug 25, 2017, at 3:33 AM, Christoph Zwerschke <[email protected]> wrote:
> 
> Am 25.08.2017 um 09:00 schrieb Mikko Ohtamaa:
> > * Front end and back end codebases can live in separate repositories,
> > with some third repository for integration tests if needed
> 
> It makes also sense to separate them as IDE projects, as most IDEs do not 
> understand the concept of a hybrid projects very well. Better to have one 
> Pyramid project and one React project.

Obviously I’m biased, but…PyCharm Professional (which embeds WebStorm) does a 
really good job on this front. I do hybrid projects frequently.

> 
> > * Communicate with the backend using REST, AJAX
> 
> Or use GraphQL (with graphene and webob-graphql). If you use REST, you can 
> make good use of Pyramid's traversal mechanism with e.g. SQLAlchemy objects 
> as resources. When you use GraphQL, you do the traversal outside of Pyramid 
> in the resolvers.
> 
> Besides React, you should also consider other frontend frameworks (a good 
> overview is here 
> https://www.sitepen.com/blog/2017/06/13/if-we-chose-our-javascript-framework-like-we-chose-our-music/).
>  I particularly like Angular and Vue.js. I found that it is much more 
> enjoyable to write the frontend code with TypeScript, not only because of the 
> typing aspect, but because you can use all the modern JavaScript features 
> which make JavaScript more similar to Python.

+1 for the use of TypeScript. It takes some extra fiddling. But this extension 
to create-react-app makes the pain go away: 
https://github.com/wmonk/create-react-app-typescript 
<https://github.com/wmonk/create-react-app-typescript>

—Paul

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/17A5B5A8-6C9A-48B4-B234-A7EB963D405A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to