Hi. As pointed out I believe this is not getting accepted as GSoC project for Django.
But if you really believe that your approach is beneficial to larger audience and you feel that it is right thing to do just do it. It is only way to prove that you're right. Of course you could be wrong as well but hey at least you did tried. Having JavaScript builder pipeline might provide more fruitful though getting such as GSoC project is really long shot. la 17. maaliskuuta 2018 klo 6.49 Manasvi Saxena <msmana...@gmail.com> kirjoitti: > Hello Sir, > > Hey Manasvi, >> >> I'm perhaps a bit biased but I would be very interested in anything that >> can make JavaScript a real first class citizen in Django. There are a >> number of third party packages out there that attempt something like this >> (i.e django-webpack-loader). Django is classically quite conservative, >> and up until relatively recently the JavaScript ecosystem has been in flux >> with a relatively high amount of churn when it comes to build tools and >> best practices. >> >> Things have somewhat stabalized recently with webpack achieving >> widespread adoption so perhaps it's time to evaluate the landscape and see >> if we can improve in this area. I'd love to see some kind of pluggable >> JavaScript build system that would make modern JavaScript a first class >> citizen alongside templates and other static assets, separate or as an >> extension to the classic static assets functionality in Django. >> > >> All in all I am quite jealous of how Rails handles JavaScript >> integrations[1]. Again, this is just my personal opinion and I cannot say >> if pursuing this will in any way effect your chances of being accepted but >> this seems likes really interesting direction to investigate and more >> practically useful than yet another way of generating static server side >> HTML. >> >> Tom >> > > > Thank you for this new approach that you have shared. I would love to work > on it since I have the required skills in both HTML and JavaScript to do > this. > I'll make a new proposal keeping in mind what you have suggested and will > get back to you as soon as I have it ready. > Would really love to know your views on that too. > Thank you so much for the advice. > > Regards, > Manasvi Saxena > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/00e13803-b9af-4c76-9f0d-9d1f226c0acf%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/00e13803-b9af-4c76-9f0d-9d1f226c0acf%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAHn91oeKEmdRAwBqWjeBdt2BbT9aYsrUnBMoUAL0tD4Mg6Jnug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
