Re: Need help getting the company I work for to go with django
2009/9/2 Kenneth Gonsalves : > > On Tuesday 01 Sep 2009 10:55:18 pm mrsource wrote: >> - It has many tools for safety, with a normal opensource CMS you have >> many more issues with security holes because all the code is public. > > this is sheer FUD to say that 'many more issues with security holes because > all the code is public.' Openssl code is public, linux code is public, apache > code is public ... does one have many more issues with security holes??? That was my first thought, but I think he means that unlike standard PHP, you don't have to place your django files in /var/www, where bad configuration might expose your code. But still, bad argument. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Need help getting the company I work for to go with django
On Tuesday 01 September 2009 10:25:18 am mrsource wrote: > Two points: > - Django has good performance and scales well. > - It has many tools for safety, with a normal opensource CMS you have > many more issues with security holes because all the code is public. > Isn't django's code public, why would you use it if this is the case? Seriously man, security holes aren't there because it's public, it's because the programmers made a mistake, not because of how it is distributed, private/propietary code could be just as insecure or secure as open sourced code, open source just has the advantage of that many more eyes pouring over it closing those holes. Now to answer the question, you should convince them of it because of the scalability and the rapid application development environment django helps create. It's orm is also a big selling point, people I know who love sql, tend to fall in love with the orm. Mike -- diplomacy, n: Lying in state. signature.asc Description: This is a digitally signed message part.
Re: Need help getting the company I work for to go with django
On Tuesday 01 Sep 2009 10:55:18 pm mrsource wrote: > - It has many tools for safety, with a normal opensource CMS you have > many more issues with security holes because all the code is public. this is sheer FUD to say that 'many more issues with security holes because all the code is public.' Openssl code is public, linux code is public, apache code is public ... does one have many more issues with security holes??? -- regards kg http://lawgon.livejournal.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Need help getting the company I work for to go with django
> I work as a web developer at a reasonably large company in London. We > are just about to completely re brand and rebuild the companies website > (s) and implement a CMS. I'm having a meeting tomorrow to discuss > different avenues we can go down in regards to what technologies we > can use. I'm hoping to steer them towards Django! > > If you were me how would you sell Django to fellow developers and > business (non-techies) people?? > > P.S. I know django isn't a CMS. I want to build a custom one using it. Convenient that, as I started typing a response, I saw this http://sunlightlabs.com/blog/2008/cool-project-what-cms-did-you-guys-use/ fly by on my RSS feed from the Django aggregator which pretty much provides tangible data to my response: with a CMS, you get a CMS; with Django, you can easily make a CMS, but then add all sorts of features that would be far harder to tack onto something like Drupal. If your choice of CMS does _exactly_ what you want, and you don't see needing to readily bend it to your will, then go with your CMS. But if you foresee customizing it, adding your own flair, then Django is my recommendation. -tim --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Need help getting the company I work for to go with django
Two points: - Django has good performance and scales well. - It has many tools for safety, with a normal opensource CMS you have many more issues with security holes because all the code is public. On 1 Set, 18:52, "Rob B (uk)" wrote: > I work as a web developer at a reasonably large company in London. We > are just about to completely re brand and rebuild the companies website > (s) and implement a CMS. I'm having a meeting tomorrow to discuss > different avenues we can go down in regards to what technologies we > can use. I'm hoping to steer them towards Django! > > If you were me how would you sell Django to fellow developers and > business (non-techies) people?? > > The CMS will need to cope with million+ hits a month & have > multilingual support. > > P.S. I know django isn't a CMS. I want to build a custom one using it. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
