I'm a django developer but I want to continue learning other things, now asynchronous development.
I have been reading about node.js, I understood that it can be used with django and exists frameworks like express.js, so I don't know what to learn. Besides I read a bit about tornado because I'm better with python than javascript.
What do you advise me? tornado or node.js? another else? if node.js, should I learn it with django or it is better alone?
Which is more popular and has more libraries/documentations/jobs ?
Thanks in advance.
Tornado it's a good choice but I do not like the doc another one is Twisted this one has a good documentation I like so much.
I'm also a Django developer and I like so much Node.js this one has a big community a lot of documentation also has a very cool librarie for WebSockets socket.io about express It's the backend of MySpace but I do not like so much express.
Combine Django and Node.js It's not so hard but it's a quite dangerous. I did a demo of how to combine them here you have the github
Related
I was trying to make a web app with a complicated idea and at some point realised that I couldn't do it alone. When, I started to look around for friends with a skill set with node in their bag, I found out that everyone had experience with pure php or django. I was thinking if I could make the web app by combining different backend technologies. But I can't really understand where and how to start. What would I need to learn? How would I exchange values or data between the two frameworks or programming languages? What things would I have to learn? Where would I start?
REST API, you can use it to exchange data easly
I'm totally new to Python and Django - just getting started with both.
I wanted to see how I could work with MongoDB, while using Django framework.
I came across this site: https://django-mongodb-engine.readthedocs.org/en/latest/ - seems like a reasonable way of doing non-rel
I'd like to ask experienced Django developers: is using Django MongoDB Engine considered "mainstream" for connecting Django apps to a non-relational backend, or is there a different, more widely used / better supported alternative?
When it comes to more widely and used I personally do not think so.
There is Flask, but Django really does everything it does plus a little bit more.
What is the problem with mainstream if it is proven to work?
I would strongly recommend using Django, specially if you interact a lot with databases. It's migration system is the best out there.
If your project is rather small and does not need all those nice features I would recomend Flask instead.
I have recently inherited a non-finished web app written in Clojure, based on compojure and hiccup basically. It's a bad attempt to model some sort of MVC with OO style not in the FP style as seen here . So I bet to re-start the project almost from the scratch reusing the useful parts. I consider these alternatives:
The least breaking alternative would be Compojure+Enlive+jquery-pjax
Using a clojure web framework like Pedestal Any experiences about this?
The initial idea was to implement a RESTful API serving JSON so for the more elaborated solution I have Backbone+react.js in my mind for the front-end and Liberator for the back-end but it's likely to take longer to develop than a traditional server app.
Thoughts and alternatives taking into account that an Ajax experience is required please, thanks a lot!
I'm not sure what is the relation between RESTful API and responsive in your post. However ...
You have multiple options here: Pedestal, Liberator and Caribou.
If all what you need is a RESTful API, then I think Liberator is your best bet and it is not going to take longer time as you mentioned. I don't know how you got that impression.
Pedestal shines if you want to develop Single-Page applications but the framework in general requires a good time to grasp and understand how it is works.
Have a look at Caribou also. It is easy to use and feel familiar.
But again, it is your choice.
I have to create web application similar to twitter with a few tweaks using django. I am clueless if I have to use a CMS for this or any other existing django-application. Working from ground up is quite tedious to be honest. Can anyone recommend me which CMS( or anything else) I should attempt trying?
There is a project called trillr1. According to its page:
"Trillr is a Twitter-like microblogging service enhanced with user directory and group discussion features. " that's maybe what you want.
https://contributions.coremedia.com/trillr1
I guess, the closest you can come with an out-of-the-box software to imitate Twitter is Status.net, the software, that powers identi.ca. However, this is a PHP application.
I'm not aware of something similar in the Django world.
Guys i would like to use Django as my backend framework and qooxdoo as the frontend framework.
Is it practical to do this?
Has anyone tried to do this?
How did they do it?
Links and pointers would nice.
Gath
I have no direct experience using Django and qooxdoo, but the general answer to the question "Is it practical?" is: yes :). Although Django's default rendering behaviour is to produce HTML (which is unsuitable for a single page application like the ones you build with qooxdoo), it's easy to switch to returning e.g. Json on requests, which is a common format for the client-server communication between a qooxdoo frontend and a server. They just exchange data.
Has anyone tried to do this? - Yes, but they don't give much information on how, other than the before mentioned Json data exchange, implementing a Json RPC server in Django using RPC4Django.
AFAIK, there is no deeper Django integration, e.g. interfacing qooxdoo with Django views on the server (like dojango).
Hope this helps.
Update:
There is one elaborate product, Sava, using qooxdoo for the frontend and Django for the backend. There is a short overview, but I think it's closed-source so it only testifies to the "practicality" of using this technology stack. You probably won't learn in detail how it is realized.
There is also enre, a qooxdoo-based GUI for Django. But I'm not familiar with it, and couldn't find any documentation on first glance, so I'm not sure what this really means.