I have some confusions and will like to clear them by asking some questions.
According to this Ajax definition:
Ajax is a set of web development techniques using many web technologies on the client side to create asynchronous web applications. With Ajax, web applications can send and retrieve data from a server asynchronously without interfering with the display and behavior of the existing page.
1. Isn't it the same as async views feature offered in Django 3.0?
1A. If Async Django will not completely replace AJAX, Is it worth learning?
2. What does this mean for Channels?
Channels is a project that takes Django and extends its abilities beyond HTTP - to handle WebSockets, chat protocols, IoT protocols, and more. It's built on a Python specification called ASGI.
Can async django replace channels too?
Suggest things related to these topics with reasoning. e.g. Use AJAX with JSON (just an example)
I know that converting Django to async will take time so have this in mind when answering
According to info I have, (don't know what AJAX is but many Django tutorials mention it so it was on my learning wishlist)
AJAX stands for Asynchronous Javascript and XML. It boils down to performing asynchronous calls allowing for parts of web pages to be loaded dynamically. This means that only part of the page is refreshed when data is changed rather than the whole page. It allows you to have your page fetch data from a server or API and allow the user to still view the page simultaneously. Once the information is retrieved from the API, the view can be updated to match the new data.
Isn't this is what asynchronous views in Django will do too?
Yes, it looks like Django will allow for you to perform these sorts of techniques within the views themselves. There may be some use cases where AJAX can be used and Django's async feature can not, but without looking into it, I can not give a definitive answer.
1A. If Async Django will not completely replace AJAX, Is it worth learning?
Is AJAX still worth learning. I would say yes. I'm of the mindset of jack of all trades, master of none. If you plan on spending the rest of your life developing with Django, maybe it's not worth it. AJAX is very common to find throughout other technologies however, so if you plan on venturing outside of the Django stack, it would be worth learning. You would also have the added benefit of knowing some of the underlying principles of how asynchronous communication works if you delve deeper into AJAX.
- What does this mean for Channels?
Again, only speculation, but I'm assuming Channels will provide additional functionality that async Django will not have right out of the gate (in your excerpt you mention: handle WebSockets, chat protocols, IoT protocols, and more. Django being async does not inherently provide these functionalities). Over time, Django might adopt some of these features, but I would assume Channels will still have its niche.