Hacker News Reader

Comment by synergy20 | Hacker News Reader

This is an amazing project, it tells yet another story how one guy can start a project ended up challenging big companies like Google(Angular) and Meta(React).

While React is adding all those complexity by SSR and server component etc these days, Vuejs separates them wisely, if you need just the original SPA, use vuejs as-is, if you want SSR, add Nuxt.

I am moving back from React to Vuejs after realizing how heavily React is nowadays affected by VC company Vercel, which has its own agenda of SSR-first(Next.js) and make React even further complicated, Vercel hijacked React in my opinion and made it no longer a "neutral" OSS project, so long, thanks for all the fish.

On the same note, Vercel also bought up Svelte and made it SSR first.

If you just need SPA and has no need for SSR, which made frontend even more complex, go with Vuejs.

View on HN

React with SSR is fine. Astro and Remix both do it well and it's effortless.

Vercel pushing Next's terrible app router has a VC stink to it. That's the only way I can explain their downright awful solutions.

Svelte is not SSR first. Svelte has nothing to do with the server. There is no server related code in Svelte. Svelte is a UI library/framework/language w.e you want to call it.

SvelteKit can be bundled with server code, but it's just as easy to bundle it without any server code. SvelteKit is essentially just a Vite plugin.

You can add adapter-static and have to bundled as an SPA and not change anything with you code as long as your not using .server.js files which are files meant to protect server code from not being bundled with the client.

You haven’t described anything different from what the OP is saying: the main dev behind svelte now works for a company that wants you to use SSR for all your projects. That absolutely impacts feature development to favor sveltekit. The same thing is happening with react.

The same thing is happening with deno as well: most active dev is with deno deploy.

VC has infiltrated open source development and is driving how features are built. Not saying it’s necessarily bad but it does change the incentive structure.

What feature was added to SvelteKit on the behave of Vercel?

I don't see where the person said that some feature was added to SvelteKit on behalf of Vercel.

Svelte has no routing for client-rendering, and itself recommends everyone to just use SvelteKit as boilerplate, which is SSR-first.

I spent two months with SvelteKit for a SPA project,it did not fly, the SSR-first (e.g. documentation etc) made CSR-SPA a second class citizen plus added unnecessary burden for those who does not need SSR, no it's not as easy as just "setting this flag you will be golden for CSR".

If I need SSR sometime, I might as well just do Django, Rails, Laravel etc which are solid. Please give me a true SPA as it used to be, and make SSR optional instead of the default.

SvelteKit is the "router".

We use SvelteKit for a internal application that we embed into a Go binary. It as simple as adding adapter-static as the adapter and not using .server files.

You can use SvelteKit the exact same way as the API for server and client are nearly the same. Load function on the server work the same as the Load function on the client expect for where they are called.

What problems did you have?

I build React apps without SSR all the time. What has changed in React besides optional support for it?

If the preponderance the documentation and examples favor SSR, I can see what the poster is speaking of.

CRA is officially not supported and the official react documentations do not mention creating spa with Vite. They mention using next or remix.

From what I recall, most of the early development was funded due to Patreon, and if you looked at the list of donors, something like 75% of the money came from a few large companies.

Reply on news.ycombinator.com