Python is great when your goal is to have the highest environmental footprint.
Yeah, because when we implement it in C++ we surely are going to save the planet now.
Or Julia, or one of the many options you have if the community was more open minded.
Show HN: I built a Python web framework
41–50 of 127 posts
Re: Show HN: I built a Python web framework
#42Re: Show HN: I built a Python web framework
#43What is missing from the web framework space is a headless ui components merged with a db layer. Most of these frameworks repeat old patterns. Nothing has been able to break through and give us something truly revolutionary like Rails did. Web frameworks need to be a visual medium where you can create ui using visual tools and the "backend" side of things merge seamlessly.
Not quite what you are describing, but sort of in the same space, are SSR heavy frameworks like Next.js. Those solve problems by having the backend do most of the heavy lifting and streaming UI updates to the browser. This makes the browser a thin client instead of a node in a distributed system.
Personally, I think it's a great direction and hope it sticks.
Re: Show HN: I built a Python web framework
#44Earlier quoted context omitted.
What do you mean by headless UI components?
Basically the ui layer and the backend layer which and the operational layer need to be combined into one seamless tool. Right now you have the write a "frontend" and a "db connection + backend logic layer". And by headless I mean something which builds on what the web provides like buttons but adds a whole lot more of components which are used but are unstyled.
Sounds like a DSL to facilitate building CRUD.
I wrote one in PHP and 3 devs were able to build and maintain a 800 page CRUD system with it (still going strong, makes a ton of money). It has complex business logic, is fully unit testable and allows for escape hatches when needed.
I'm in the process of rebuilding the DSL in C# with the lessons learned (because Entity Framework is awesome). And might open source.
Re: Show HN: I built a Python web framework
#45Earlier quoted context omitted.
Basically the ui layer and the backend layer which and the operational layer need to be combined into one seamless tool. Right now you have the write a "frontend" and a "db connection + backend logic layer". And by headless I mean something which builds on what the web provides like buttons but adds a whole lot more of components which are used but are unstyled.
> Basically the ui layer and the backend layer which and the operational layer need to be combined into one seamless tool. Right now you have the write a "frontend" and a "db connection + backend logic layer". Solving this “problem” just doesn’t seem like a good use of a time. There are now 4738484 different viable ways to build a website, adding another way is just a waste of everyone’s time
I'd argue web dev is largely a solved problem for large complex apps, but largely unsolved for simpler use cases.
The problem is the amount of boilerplate and tool complexity involved. In a large project, the boilerplate can become a small fraction of total work put in (hopefully), with most to the work spent expressing the logic of the application.
In smaller projects, the boilerplate can be the vast majority of the work. Building a backend, a frontend, and a communication protocol between them (that includes reactivity). On the backend you need to learn HTTP/Websockets and a backend framework. On the frontend you need node, nvm, npm, yarn, React/Svelte/Vue. To do it right you need to implement automatic reconnect/resubscribe on reconnect, etc.
Several projects try to reduce this complexity in various ways, but they all have trade-offs and I don't think we've found a sweet spot. Drag and drop tools like Squarespace and Retool are heavily biased toward expressing UI and integrate clunkily with backend logic. Backend-based tools like Streamlit and Pynecone (Reflex) get closer to a sweet spot IMO but are either severely limited in what you can do (Streamlit) or ultimately expose you to the full complexity of the frontend (Pynecone).
I think further work in this space is warranted.
Re: Show HN: I built a Python web framework
#46What is missing from the web framework space is a headless ui components merged with a db layer. Most of these frameworks repeat old patterns. Nothing has been able to break through and give us something truly revolutionary like Rails did. Web frameworks need to be a visual medium where you can create ui using visual tools and the "backend" side of things merge seamlessly.
This is basically what React Server Components is trying to be.
Re: Show HN: I built a Python web framework
#47What is missing from the web framework space is a headless ui components merged with a db layer. Most of these frameworks repeat old patterns. Nothing has been able to break through and give us something truly revolutionary like Rails did. Web frameworks need to be a visual medium where you can create ui using visual tools and the "backend" side of things merge seamlessly.
Like ASP.NET web forms? Drop in a datagrid and select your ado data source…
Re: Show HN: I built a Python web framework
#48I am waiting for someone to finally give me just a wysiwyg tool to make web pages and apps so I don't need to program anymore. I just want to make content, not make a machine to then make my content with. It's like building a wood cutting machine when I just want to be warm in the winter.
Re: Show HN: I built a Python web framework
#49I am waiting for someone to finally give me just a wysiwyg tool to make web pages and apps so I don't need to program anymore. I just want to make content, not make a machine to then make my content with. It's like building a wood cutting machine when I just want to be warm in the winter.
WYSIWYG UI-builder with LLM-based ability to describe what you want. "Form with username and password and when you submit it creates an account".
Re: Show HN: I built a Python web framework
#50has someone wrote yet a good, brief comparison of this to the other Python web libs?