91–100 of 222 posts
I never built a web app in my life. I have always been on the server side. Recently I spent a couple days building the same web app in Next, Nuxt, and SvelteKit just to get a feel of how to build a web app today. The web app was pretty basic. A couple of pages showing data from different apis and auth with user setting page. My favorite by far was SvelteKit despite being the one with the smaller community. It was act…
Earlier quoted context omitted.
> I never built a web app in my life. > I would highly suggest people to try SvelteKit. I feel like this is a good summary of tech trends these days.
A beginner suggesting something to try seems fine to me. They have something no amount of study can give, a fresh perspective.
I like the fact minimalist approaches, like svelte, htmx and alpine.js are getting more and more traction. I felt like fighting this fight alone for years in the golden years of node, webpack and react where everybody was creating crazy stacks and adding GraphQL and so on, to basically get what Django + jquery did 10 years ago in a tenth of the time and code. So far I also survived: - xml is the future - let's use no…
I like Svelte but I’m not sure I’d describe it as “minimalist”. It’s a new language with its own compiler and reactivity system.
I've used Next.js quite a bit, but once I tried SvelteKit, I never looked back. One of the things I built with it is https://landing.gallery/
Earlier quoted context omitted.
> Standards-based is really the only thing that challenges react these days I feel like Vue would be a better fit for this role, especially since now they have a Composition API that's as pleasant to use as React, except that they do lifecycle hooks better than React (no messing about with dependency arrays): https://vuejs.org/guide/extras/composition-api-faq.html There's also Pinia which is a lot simpler than trying…
I like Vue as much as the next guy, but comparing Nuxt to Next doesn't really do Next justice. Nuxt is pretty much a glorified blog engine, a conceptually broken tech demo. Its performance is abysmal, the developer experience frustrating, and many things that seem convenient when you read the docs turn out to be a hassle in production. Next is so much more refined compared to that.
> After several meetings, we came to the conclusion that the best approach was to simply halt the old website development and build a new one from scratch using the best technologies and practices. Spoken like a true developer. Trash the old system, reinvent the wheel, prioritize the delight of the devs, leave the client with something that is totally obsolete and nobody else knows how to work on in a couple of years…
Maybe i’m dreaming but i’m starting to feel a new « let’s stop with the fashion addict attitude to tech » vibe on HN, which i really really like :)
Earlier quoted context omitted.
React state is a hot mess, yes! We kept the same interface as the Svelte store, but with different semantics: - special management of undefined values - error management - promise management
Curious - what makes react state a mess? Is it just that there's not much batteries included?
Spend an hour, a day, or a year (depending on how broad you want your "introduction" to this topic to be) reading the various blogs and docs on state management systems if you want to see how crazy this gets.
I never built a web app in my life. I have always been on the server side. Recently I spent a couple days building the same web app in Next, Nuxt, and SvelteKit just to get a feel of how to build a web app today. The web app was pretty basic. A couple of pages showing data from different apis and auth with user setting page. My favorite by far was SvelteKit despite being the one with the smaller community. It was act…
I like them both, but tend to lean more toward Nuxt for the modules ecosystem and layers/extends. I also find composing reusable props with typescript to be nicer in Nuxt, but that's more of a Vue vs Svelte thing than Nuxt vs SvelteKit.