>So this argument has now been forked into Django's ORM capabilities and wether or not you should use Django for an API.
The two are inextricably linked as far as this thread is concerned.
>Rate limiter is framework independent, can be built using Redis with a few lines of code. So not applicable.
Mine is apparently 200 lines of code (library total) and tied to the framework. I guess you are more of a "reinvent the wheel" type programmer.
>Pluggable social media authentication backend is for websites not APIs
APIs do all manner of different things.
Last time I built an API it was a back end for an iphone app. It needed an authentication backend. By using a pluggable framework I could not only let the app log in/sign up using facebook tokens, I could with one added line add twitter or ~40 other back ends, saving me from... reinventing the wheel.
> for an api you can still build your portal in Django and do all authentication/whatever there and simply sign requests for the API.
Or you could just use django for the API as well the portal since it handles everything about making APIs pretty well (with the exception of high load APIs).
>for APIs you most commonly use API key/secret.
For APIs there are many common ways of doing authentication. There's no standard. Basic auth over https, token, oauth, key/secret, cryptographic signature. If you ascribe to a "one true way" you lack judgement and experience.
>I am familiar with Django, and I know that you can (not the ORM though), but do you want to drive a monster truck when all you need is a car to get around?
I already refuted your point that it was a monolithic heavyweight beast. It's composed of multiple small modules all of which exhibit loose coupling and each of which can be used independently or not at all.
>Since you can't use Django's ORM anywhere else
Utterly false. You can use it wherever you like, independently of everything else (sometimes I do that).
Feel free to argue that you don't like it or it's wrong for whatever situation but please refrain from making shit up to justify your point.
Some advice also: curb your instinct to reinvent the wheel, no matter how simple that wheel may seem.
I'm not arsed to explain to you half of what is wrong with that comment, wtf I know you can use the ORM outside of Django but why the f*ck would you.
You're just arguing like a 10 year old fan boy now. Django is great for sites I love it. I also use other tools when I need different things. As for reinventing the wheel it's a very simple code snippet taken from a reliable source then changed to fit needs. So go home sleep learn new things... Don't attempt to build the next OS in Django.
The two are inextricably linked as far as this thread is concerned.
>Rate limiter is framework independent, can be built using Redis with a few lines of code. So not applicable.
Mine is apparently 200 lines of code (library total) and tied to the framework. I guess you are more of a "reinvent the wheel" type programmer.
>Pluggable social media authentication backend is for websites not APIs
APIs do all manner of different things.
Last time I built an API it was a back end for an iphone app. It needed an authentication backend. By using a pluggable framework I could not only let the app log in/sign up using facebook tokens, I could with one added line add twitter or ~40 other back ends, saving me from... reinventing the wheel.
> for an api you can still build your portal in Django and do all authentication/whatever there and simply sign requests for the API.
Or you could just use django for the API as well the portal since it handles everything about making APIs pretty well (with the exception of high load APIs).
>for APIs you most commonly use API key/secret.
For APIs there are many common ways of doing authentication. There's no standard. Basic auth over https, token, oauth, key/secret, cryptographic signature. If you ascribe to a "one true way" you lack judgement and experience.
>I am familiar with Django, and I know that you can (not the ORM though), but do you want to drive a monster truck when all you need is a car to get around?
I already refuted your point that it was a monolithic heavyweight beast. It's composed of multiple small modules all of which exhibit loose coupling and each of which can be used independently or not at all.
>Since you can't use Django's ORM anywhere else
Utterly false. You can use it wherever you like, independently of everything else (sometimes I do that).
Feel free to argue that you don't like it or it's wrong for whatever situation but please refrain from making shit up to justify your point.
Some advice also: curb your instinct to reinvent the wheel, no matter how simple that wheel may seem.