mininext

here is one that uses the fact that the raf loop will slow down when the tab is out of sync. makes state handling much easier. similar to dearimgui frontend example https://github.com/spirobel/counter/blob/master/frontend/cou... on the backend this obviously runs only once. the main issue with backend frameworks is, that the request and other context data has to be passed through the business logic + VIEWS. leads to tight coupling of all the components as it is downstream from the data structure + presentation this is resolved by resolving the html template strings at the end and allowing functions (that also produce html template snippets) to be passed into the template strings. this decouples views, business logic and data https://github.com/spirobel/mininext/blob/master/docs/archit... worked on this for the last few years. But it is st

after having used both: sortablejs is better than reactdnd. that being said: htmx makes it too hard to quickly add a fat frontend to a page when necessary. The points about the react ecosystem are very valid, even if drag and drop is an exception. The network effects of react and others are hard to beat. Its probably even more npm as a whole than just react. wrote myself a framework with bun that solves this for me: https://github.com/spirobel/mininext still get the pure html+css feeling like with htmx, but can throw in a big frontend when needed. https://x.com/spirobel/status/1827231794934247674?t=moRzsWIP...

my webframework: https://github.com/spirobel/mininext (my goal with mininext is to provide index.php like productivity but with all of npm and typescript at your fingertips) currently busy using it to build things. will document everything in detail soon. https://x.com/spirobel/status/1827231794934247674

I am building an alternative to nextjs that consists of just 3 files and has no external dependencies. https://github.com/spirobel/mininext (my goal with mininext is to provide index.php like productivity but with all of npm and typescript at your fingertips)

there is a small difference: you also need to make your own hmr reloading script when using bun. But it does so much more than just frontend bundleing. If you need an hmr script you can use the one I wrote for my webframework: https://github.com/spirobel/mininext (my goal with mininext is to provide index.php like productivity but with all of npm and typescript at your fingertips)

why not just use es6 template strings? (I do that for my framework mininext https://github.com/spirobel/mininext would be happy to receive feedback, other view points on this :-)

yes. took part in a hackathon and decided to make my own webframework while doing it. It was supposed to be compatible with deno and bun and I chose deno deploy to deploy my stuff. But 17 hours before the deadline this happened: https://twitter.com/spirobel/status/1786665928954085562 deno deploy just showed a completely useless error message and stopped working. I installed caddy on a vps and got it to work in 5 minutes. I ripped out the deno compatibility and switchded to bun sqlite instead of turso and the website got even faster. That is because the server has the data in the sqlite db. No need to roundtrip to turso. btw. the framework is open source now: https://github.com/spirobel/mininext It is like a non bloated version of nextjs. My intention is to displace php and wordpress. It is possible to get started with just html and css kn