web2py VS Wagtail

For reference, YouTube runs on Python[1,2,3]:

> 1. Python and Django: YouTube’s backend is predominantly written in Python, offering a balance of performance and readability.

> 2. Google Cloud Platform...

> 3. Java and C++: YouTube also utilizes Java and C++ for specific backend services, as they provide better performance for certain tasks.

---

A long time ago, I looked into these Python frameworks:

- http://www.web2py.com/

- https://kivy.org/

[1]: https://blogopost.com/youtube-tech-stack/#backend

[2]: https://medium.com/@shanthanaroja99/technology-stack-behind-...

[3]: https://youtu.be/G-lGCC4KKok

At a previous job, not as a software developer, myself and a few others endeavoured to build a CRM for the church I worked at. We opted for web2py simply because it was the thing I had first learned after learning Python and had found incredible power in building something that people could use.

Its Github repository https://github.com/web2py/web2py although it was designed to reduce web development tasks such as developing web forms from starting and working like that. It is cross-platform means that you can run it on Windows, Linux, and other operating systems which can run on your computer.

Once mastered, frameworks like Django, Flask, Web2Py, and Bottle can significantly ease the life of a Python developer. Moreover, Python frameworks allow you to build an application prototype fast, as it essentially eliminates the need for repetitive input code.

Web2py

{{=T('Powered by')}} web2py

If you like Python 🐍 then check out this project. Wagtail is a popular CMS, combining Django’s powerful customization capabilities with a slick user interface. The newest update brings Django 5.0 support, a new searchable and filterable listing UI, the accessibility checker built into the admin interface, and a brand new 10-step tutorial for developers. This release marks Wagtail's 10th birthday 🎂. Happy birthday to the team and all the best for the next ten years and beyond 🥳.

Repo : https://github.com/wagtail/wagtail

- The discussion thread we use to track all public feedback: https://github.com/wagtail/wagtail/discussions/9553. Comments very welcome.

Not so long ago, I submitted a Pull Request in wagtail to improve the admin performance, especially for non-superusers. Basically, it caches all the user's permissions on first access. However, I was pretty sure that this would load a lot of model fields that we never need but there isn't a tool that gives us that type of report. Therefore, I started building an app that keeps track of all fields accessed so you can easily know which ones haven't been used and apply the only/defer optimisation for Django querysets.

Wagtail would be a good example https://github.com/wagtail/wagtail/tree/main/wagtail/tests

Paarth moving from no contributions to the 21st most contributions - https://github.com/wagtail/wagtail/graphs/contributors.

Over the last few years, I have had the incredible opportunity to be a core team member of the Wagtail project. In that time, I have reviewed many new pull requests, and I’ve also had the chance to submit many of my own across Wagtail and many other projects.

Wagtail 2.15 is the most recent LTS (Long Term Support) release, so it’s not a bad release to stick to at all, at least until February 2023.