As a backend developer, I was finding it difficult to use svelte kit to develop a SPA. Specifically it is hard to know from the docs how to handle authentication. The router is not much exposed. I hoped that 2.0 would add something in this area. nextjs docs have a section on server and client based authentication which is useful.
I have not said SvelteKit can't do it. In fact having different options(and for free) is a great thing. I was raising the point that messaging [1] is that it is not recommended most of the time, and does not say when it is good to have an SPA.
Also mentions about scenario JavaScript is disabled. I am not too sure if these frameworks help there with SSR. May be it meant the user can still see a pre-rendered page but with almost no interaction possible?
Essentially I was saying there is a push towards server based frameworks.
> Having a server component is just the natural step after a decade of bloated and unnecessary SPAs.
Not sure I buy that argument. While I am not totally against the idea of server based frameworks, what is disappointing is the frameworks are appearing to plant the above message.
SPAs provided us a good boundary and that is blurred by all these server based frameworks. You now have server for UI, server for BE. While I agree some SPAs are heavy, I think we have reasonable solutions for most. And these server based framework still need all the work that is done in SPA, just that routing and some aspects of bundling are taken care.
More and more frontend frameworks are now somewhat mandating a server part. I know pretty much all(sveltekit, nextjs) say you can do static export, but docs are more focused to use with a server. IMO it appears like this is being pushed by cloud vendors sponsoring those projects.
If you want to build a plain old SPA, the new react docs pretty much have no info. Sveltekit docs discourages it. I have not looked much into vue, but it appears like vue does better here.
Qwik while has a static export, looks like you lose all the good parts of you don’t use a server.
I can certainly see the SEO and other good thing that comes with SSR but not everyone needs it.
From the blog post:
Qwik is a next-gen web application framework (and meta-framework) designed for instant application startup, no matter how big the app is. Qwik uses a modern and innovative approach that “streams” chunks of JavaScript to the end user — and it does it automatically!
Yes, I think I get that. But it is not easy to pin on different packages. For example if I want golang 1.18, node 12, I need to find the commit corresponding to those and add them. I mean it is possible but not as easy as it should be.
Is there a way to pin a version of the tool with this? For me, the biggest problem with Nix is that version pinning is not easy, actually it is complex.
From the docs it looks like you have dedicated instance of service for each user, is that correct. Or it is a kind of multi tenant system where data might be colocated. I am guessing that it is a multi tenant system but If you spin off an instance for user, how do you do that?
I am working on a side project solving the exact same thing. The project is not open source yet and I am not very actively working on it. I kind of created it to learn golang and some web technologies and other infra tools that I normally don’t use at work. Good to know that there is a market for, not that i have plans to commercialise it but if i open source it people might be interested to contribute.
I am in late 30s, I recently switched jobs. Before this switch I never jumped for less than 20% hike. But this one I took slightly more than 30% cut. I never thought i would leave for less.
I was really disliking the tech stack, I could not change it even after trying. But there were lot of nice people, pay was above market levels. But i was still not satisfied, I could have stayed there and earn good increment every year by just doing 4-5 hours daily work.
The new company is a big Australian start up. My hope is that in the new company I’ll get to work with smart people and learn new things which I consider as an investment for my future growth.