expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-09 07:14:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

reformatted, added URL to 2025 comparison article - online edit of handbook/troggle/trog2030.html

Browse Source
This commit is contained in:
Philip Sargent
2025-06-28 08:03:17 +01:00
committed by Expo on server
parent e5e208ee45
commit 88c6b59976
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
handbook/troggle/trog2030.html
View File

@@ -198,11 +198,15 @@ A GIS db could make a lot of sense. Expo has GIS expertise and we have a lot of
<h3>Django and Flask</h3>
<p>The idea that we should replace Django with Flask comes up from time to time: "No! This is a really <em>shit</em> idea":<br>
<p style="margin-left:40px">"The true comparison of these web frameworks depends on your project's needs. Are you building a traditional web application that connects to a database, requires CRUD (Create-Read-Update-Delete) functionality, and user authentication? If yes, Django has built-in solutions for all of these needs. By comparison, Flask requires installing multiple third-party libraries: Flask-SQLAlchemy to connect to the database, Flask-Migrate to manage database migrations, Flask-WTF and WTForms for forms, Flask-Login for user authentication, FLask-Mail for email support, Flask-Security for security features, Flask-Admin for an admin interface to manage application data, Flask-Caching for caching support, Flask-BCrypt for password hashing and so on."
<br>
<p style="margin-left:40px">"The true comparison of these web frameworks depends on your project's needs. Are you building a traditional web application that connects to a database, requires CRUD (Create-Read-Update-Delete) functionality, and user authentication?
<ul style="margin-left:40px"><li>If yes, Django has built-in solutions for all of these needs. <li>By comparison, Flask requires installing multiple third-party libraries: Flask-SQLAlchemy to connect to the database, Flask-Migrate to manage database migrations, Flask-WTF and WTForms for forms, Flask-Login for user authentication, FLask-Mail for email support, Flask-Security for security features, Flask-Admin for an admin interface to manage application data, Flask-Caching for caching support, Flask-BCrypt for password hashing and so on."</ul>
<p style="margin-left:40px">
"The power of Django is that you don't have to worry about any of these things. They are included, tested, and supported by the community. For Flask, the third-party libraries are not as tightly integrated and require more manual installation by the developer. This affords greater flexibility but also requires more programmer expertise."
<br>
<a href="https://learndjango.com/tutorials/flask-vs-django">flask-vs-django</a>.</p>
<a href="https://learndjango.com/tutorials/flask-vs-django">flask-vs-django</a> which also talks about FastAPI.</p>
<p>For an updated (June 24, 2025) comparison, see <a href="https://judoscale.com/blog/which-python-framework-is-best">Choosing the Best Python Web Framework</a>
<h3>Postscript</h3>