python - Django from Java developer perspective -
I am a long time Java programmer and lately I am digging in Jiggang to see it.
It seems to me that Django Java does not fit the web developers' taste.
I mean that in the MVC java web framework we usually have a controller class that receives the request, get the argument and then the next
the train also follows this pattern is.
On the other hand, Dengig looks a bit procedural, you map requests to a file, write your handlers in the other, write
So, I think the rail Java Java The developers are friendly to the taste and the DJGENGO is suitable for PHP people.
If you are a Java web developer, how do you see Django?
Are you a Java programmer who is happy using the Django?
(I do not underestimate DJ ango, Django Framework is indisputable).
On the other hand, the jigs look a bit procedural, you map requests to a file, Write your handler in one another, write another one to your domain classes ...
As a Java developer, how is it different from traditional Java MVC pattern? It's just different names :, etc.
Do not you have a domain class in your Java applications?
In Java-land, when you have an MVC WebApp, you have the same type of partition as the argument:
- You write a request-handling argument in your controller
- You represent "domains" in your model / domain sections
- You write performance logic in your visual template / sections
I think that whatever you think is very different about Django beyond those names.
Comments
Post a Comment