Mar '24 (edited) • 💬 General
Frontend-Frameworks Python and Beyond - Discussion
Hi everyone, just want to quickly drop a question concerning the "overall landscape" of frontend-frameworks.
Afaik, as Python Programmers we have the following options:
  • Templating Frameworks (Flask, Fast-API, Django): Uses Jinja, everything happens server-side, each small change forces a rerun and a refresh of the whole website, complex, slow
  • Streamlit / Dash / Gradio Frameworks: Varying degrees of speed/flexibility (rerun of the whole page or different components), uses ReactJS under the hood
  • HTMX: New framework which is like a templating framework but can be applied to single HTML elements, faster, more flexible
  • Full React/JS: Python is only used for the backend, the frontend is run by a JS-Framework, (maybe with GraphQL? - no idea what that does), professional, but steep learning curve
  • FastUI: No idea into which box to put th
  • Webassembly - no idea what that is either
I have used Streamlit, but I have found it a bit lacking in speed and flexibility. HTMX is promising, a full backend/frontend split and using JS for the frontend is probably the most professional approach.
What are your experiences, what is your opinion/preferences, do you agree with my assessment, or are there any factual mistakes?
9
19 comments
Bastian Brand
6
Frontend-Frameworks Python and Beyond - Discussion
Data Alchemy
skool.com/data-alchemy
Your Community to Master the Fundamentals of Working with Data and AI — by Datalumina®
Leaderboard (30-day)
Powered by