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

I think there is another layer to that conversation. Frameworks become bureaucratic and boring because they are developed by large teams for large teams. Most developers are working on small projects and need more fun and less maintaining huge amount of boilerplate code that recreates the browser.

The framework that I feel makes development less ugly is svelte. But still, I really don't like the idea of heavy client side websites. It really makes everything more complicated and the user's device slower.

I love the simplicity of Turbolinks, I love how clean svelte code is and I am trying to figure out the "glue"



The only weak point for Svelte is there is no inline template composition (yet; already has a rfc). Anything that doesn't look like function is weak compossibility. Imagine recursively calling template itself with a bunch of condition logics, each branch renders different nested templates, and each of those calling its own ancestor root. Svelte is a joke to this thing.


I went down this route recently. There are a couple of different options depending on your preference:

• Write the glue code yourself if you only need svelte on a few pages • Inertiajs if you want to replace your view layer with svelte


I agree with you. I did give a look at Inertiajs just because Laravel was friendly towards it. Looks sweet.

Right now the "glue" I came up with is a silly connection between the server side router and the "Entry" component of Svelte. It works, it's 10 lines of code, it's clean and the website is super fast. But, both Inertia and my solution feel somehow "hackish". Not a proper pattern.

But really, anything to avoid client side routing, state management and auto-magic code splitting.


Wow, InertiaJS looks like exactly what I've been wishing for. Component-driven SFCs in Vue are the best tool I've used for interfaces in 20+ years, but I don't love having an API layer between the client and server. This is really interesting. Do you have experience with it and know how it handles frequently live-updating pages?




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

Search: