Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I am building an open source web framework comparison.

The idea is to put together a project that gives an overview of how to set up a minimal viable web application from scratch via all the different frameworks.

For each framework the project features a self explanatory shell script that builds a web app with routing, templates and user accounts. So there is no ambiguity of how to reproduce the results. And it is even possible to just copy&paste the steps into a docker container and see the framework in action.

Here is the repo:

https://github.com/no-gravity/web_app_from_scratch

So if you want to compare how the frameworks do templating, you can look at the "Let's use templates" part and have a quick overview of how it is done in Django, Laravel, Flask, Symfony, NextJS...

I wrote the beginning of the Django script and two developers contributed Laravel and Symfony scripts. So far we have routing and templates. All three still need user accounts.

If you are experienced in a web framework, feel free to add to one of the scripts or a new one and send a pull request!



I want to do something similar, only...for UI frameworks...

So on the sidebar you have components...one is a sidebar right? so you click on it..on the right pane it shows implementations on the top of the pain is a dropdown so you can switch from say. MUI to AntD to Vuetify, etc... some are narrow scoped frameworks (Vuetify for example is only Vue), some are Wide... Tailwind Kit for example or Daisy UI... they target tailwind but are JS Framework agnostic...

So under each implementation of each component might be code for Rails, Laravel, Django, views and maybe even some sort of api integration where you can have a webhook that can either connect to your dev and push the code to the right places, OR it could put it in a queue if your local dev can't receive incoming normal http requests, you could just use a cron job or manually import the code from your localhost backend...

I'm imaging this sort of being like a mixture of low-code meets Storybook with already developed ui components, and you could even import full templates, etc... So for backend devs w/ an idea 90% of the UI stuff is just drag/drop etc.... you could even have a way to combine elements somehow so you can build up a whole page of elements...and some sort of marketplace where people could share designs and maybe charge like $1 for the code snippet MIT license, but access to the code is $1.

Edit: It'd also be cool to extend this to data-layer..so say I am designing my migrations/models... and I want an Employees table....well maybe I type in employees and it organically lists all the columns previous people have used for employees tables and ranks them by how often it was used... so you can basically have most of the data points that are pretty common across similar apps be shared and almost done for you...and then you can export to django, rails, prisma, hasura, laravel, etc...



Yes, there are a couple of these "build the same thing in different stacks" projects.

The main difference is the "no ambiguity" approach I take. When you look at the Django part of the project you linked to, you see it starts with 8 manual steps and then a bunch of optional steps in case it does not work.

I want to have no ambiguity. No manual steps. That is why every framework is handled by a script that is guaranteed to work on Debian 11 and leads to a running web app.


I'd suggest keeping the project templates in Cookiecutter-style repos (https://github.com/cookiecutter/cookiecutter) instead of embedding them as heredocs in a shall script.


That sounds really cool, I have no knowledge of frameworks but I will definitely be a beta-testing user if needed.


Great! You can find me on Twitter to be updated on the progress of the project:

https://twitter.com/marekgibney




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: