31–40 of 127 posts
Earlier 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.
Are you really 15yrs old? is the biggest question here..
Earlier 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.
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
Edit: It looks like some of the hot-paths are implemented in C. Interesting! (I would recommend pointing this out in the readme)
“modern” and “lightning fast”
What 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.
"Streamsync is an open-source framework for creating data apps. Build user interfaces using a visual editor; write the backend code in Python." [0] https://github.com/streamsync-cloud/streamsync
Flask is decent. Can’t we use that?
However, my opinion is that is a PITA that every Flask project has a different structure, unlike a "batteries included" framework like Django, Rails, etc.
Flask is decent. Can’t we use that?
Earlier quoted context omitted.
Then you've invented Visual Basic in the 90s, WordPress in the 00s and I don't know Squarespace or something in the last decade. For business cases beyond that, this is simply not how "the backend" works.
Visual Basic and other "RAD" builders were pretty neat and I think platforms like WordPress or Drupal never captured their charm. For one, any apps built on them need a rather complex runtime, which feels worse to me than a language's standard library or the JVM. It's a far cry from dragging in a button and then referencing it as a variable in code. Second, the graphical niceties of these platforms often run "in-proc…
I would say, focus on what makes your web framework different. i.e. if you want to implement py-to-js, don't also reinvent routing at the same time. Grab an existing py-to-js engine and make something tiny with it. If it shows the value of the idea, then it will be picked up by the wider community. I like the idea of decorators for turning query and body parameters into function parameters, I haven't seen that before…
However, fastapi manages this without a decorator, only a type hint. Is there any gain doing it like this?