Node 11.0

Thanks a lot for the clear explanation!

+1

In addition, since v6 [0], npm audits dependencies for security vulnerabilities, which is really useful to keep projects safe.

[0]: https://blog.npmjs.org/post/173719309445/npm-audit-identify-...

I've got a subscription to Safaribooksonline, and there's a plethora of books/videos there. I found most to be somewhat limited in their scope, when read individually, but after going through a few of those, it starts to make sense :)

Here's a few of them:

https://www.amazon.com/Django-Unleashed-Andrew-Pinkham/dp/03...

Thoughts: does not cover any html/css. The biggest negative I see here is that the book only shows a website twice or thrice. The rest of the book is pure-django-related stuff, which is very intersting/important but does not give a newbie a good understanding what he's actually doing (e.g. by showing real-life examples of a possible website). It contains some code-errors, unfortunately. I found it to be more useful as soon as I grasped the basics of django (models, views, urls, etc.)

----------------------------------------------------

https://www.amazon.com/Django-Example-powerful-reliable-appl...

Thoughts: absolutely the contrary to the above. Does show what sites you can create and provides the code for that so you can actually see what a website might look like, what a feature does etc., but it gives little to no explanation about the code. Without at least a basic understanding of how django works, the reader will have a hard time truly understanding what he's doing. It contains examples for multiple possible websites.

---------------------------------------------------

HTML, CSS & Javascript:

https://www.amazon.com/Web-Design-HTML-JavaScript-jQuery/dp/...

Thoughts: great books! Filled with code and the actual picture of what all of it means/looks like. it covers all the basics but doesn't go super deep.

---------------------------------------------------

HTML, CSS & Javascript:

https://www.udemy.com/the-web-developer-bootcamp/learn/v4/ov...

The only course I bought on udemy. Do absolutely not regret it. Content is vast, the instructor seems to know what he's talking about, many many many examples and explanation of all the basic concepts.

--------------------------------------------------

Django youtube:

https://www.youtube.com/playlist?list=PL-osiE80TeTtoQCKZ03TU...

After reading through the aforementioned books, I found this tutorial to be super helpful. I went through the whole playlist within 2 days and this helped me to deepen the basic knowledge from the books

-------------------------------------------------

And except for that, I visit the django docs and stackoverflow every day, of course :)

Hope that helps.

I'm in the process of moving a project from Django to Node, these are some of the reasons: 1) Typescript everywhere: we are developing several frontends using Typescript, mostly with Angular and some Nativescript. Too many times I terminated a Python backend line with ";", mixed "true" and "True" or tried to solve a problem with a stream of (reactive) functions; 2) Django is sta(b)le: major changes, like Django Channels for websockets support, tend to have a difficult time in replacing the status quo and being first class citizens. This has a chain effect on the ecosystem which usually rely on the stable core. You may see this as feature because of the stability or as a limitation. If you, like me, may need websockets or GraphQL subscriptions, you will probably see the limitation first. Another issue related to stagnation is some degree of features overlap: if you are doing REST with Django you are probably using the Django REST framework, a third party framework built on top of Django. If you are using the DRF you will probably notice some similarities between forms and serializers and, as a matter of fact, serializers can replace forms and it is a good idea to do so, to avoid repetition. There are other similar cases, this is just an example; 3) The Django automatic admin is a trap: at the beginning it is a dream come true. You can do those boring CRUD parts literally in seconds, right? Then you start to push business logic into it. You do the first compromises: "ok, adding this single feature to the admin may require a little bit more time than what it would have taken with a stand alone dashboard, but the admin saved me tons of time so who cares?". Then you do it again. And again. And you will even change the way you reason about models because they will impact the UI the admin will generate. Very soon you will have a nightmarish mutation which will fight every new line of code. Of course I'm not saying that a feature should be avoided or considered bad because it can be used in a wrong way. I'm saying that you must know the tool and its limits to avoid the side effects, and often the ability to better see the bad parts come with experience; 4) performance: this is a very complex topic and depends on many different factors. For starters you may not need better performance at all, maybe your application can handle your workload without missing a beat because often web applications are IO bound anyway. But you must know that Django use a blocking IO design and this has some consequences regarding the number of concurrent clients served, the process model, memory usage, etc...