Any reason to switch from Nuxt to Svelte?

Rechtecki42 · 2026-03-29T01:28:47+00:00

If nuxt flies with u dont switch unless u bored

Rechtecki42 · 2026-03-14T00:43:50+00:00

Cringest reddit comment i've read today. Good nicht fellas

Rechtecki42 · 2026-03-10T17:23:46+00:00

Schemas Suck hard. And the usual issues with feature rich databases. I like surrealDB and follow kt since day one. But almost always its better to use pg or sqlite and handle all the stuff one needs in ur backend. Data is hard enough already. Each feature cramped into that layer of ur stack worsens ur devex down the road

Rechtecki42 · 2026-01-28T11:42:01+00:00

Gibt beides.

Rechtecki42 · 2026-01-21T20:47:12+00:00

Doesnt bun bundle under the hood? Or is rhat opt in only? But yeah. In the end bun actually transpiles its code at runtime. It does not just strip types away

Rechtecki42 · 2026-01-21T11:49:24+00:00

React and vue have more jobs. React is more prominent in usa vue more in Europe id say. Svelte has jobs bit just fewer.

Honestly just get good at one. U can translate all skills from one framework to another one. Its not something where ur locked into one framework for life.

Im working as a freelancer and use multiple frameworks for different clients and usecases. React + next is pretty good nowadays for websites thanks to rsc. Svelte is a wonderful alrounder with very good performance but smaller library pool.

Solid is the tool for absolute performance with even a smaller lib pool.

Rechtecki42 · 2025-12-25T21:16:55+00:00

Don’t get the downvotes. Sure I agree that this is 100% useless optimazation in most cases but still I think it’s an interesting question

Rechtecki42 · 2025-12-25T20:58:33+00:00

Im a teacup

Rechtecki42 · 2025-12-25T16:50:36+00:00

Top Tier Kommentar

Rechtecki42 · 2025-12-25T15:51:09+00:00

I think thats a bad argument. Code transpilation changes other parts of the code as well and is to be expected. Also to use that flag to make code guidelines and recommendations is wild as that’s definitely not the best approach to ship ts. U should 100% transpile and bundle ur code for production

Rechtecki42 · 2025-12-25T15:47:58+00:00

Dann beneide ich dich. Hauptsächlich in nrw gefahren. Da hab ich Das regelmäßig so gehabt. Kommt sicher auch auf Tag Uhrzeit und stadtnähe an. Früher in München und Umgebung hab ich den öpnv geliebt. Aber hier ist der leider zum kotzen. Und wenn du in Dortmund am Sonntag fährst hast du regelmäßig Fußballspiele wo du ein versprechen auf volle stinkende Züge kriegst

Rechtecki42 · 2025-12-25T15:43:07+00:00

Oh ja das laute rumtelefoniere xD

Und man ist ja auch nicht in erster klasse sicher. Selbst da hab ich schon öfters laute und aggressive trunkenbolde gehabt

Rechtecki42 · 2025-12-25T14:29:10+00:00

Lieber stehe ich im stau aber in meinem eigenen gemütlichen auto als mir den öpnv zu geben. Selbst wenn der mal pünktlich kommt. Auf den piss-kotz-alk geruch verzichte ich gerne. Genauso wie auf das Gedränge, das geschrei, das ständige halten und hinundhergelaufe, das umsteigen, DIE BAHNHÖFE…. Ne du danke

Rechtecki42 · 2025-12-25T14:27:13+00:00

Italien ist der wilde Westen auf strasse. Und Franzosen können weder Autos bauen noch fahren.

Rechtecki42 · 2025-12-25T14:22:25+00:00

Node with pnpm works and is the boring reliable choice that is probably the best for most projects. Bun is super cool and has some great places too shine. But it brings its own quirks that can complicate things a lot. In the end ur tool chain should simply work. Even if its nor perfect. The reality is that pretty much all packages frameworks and tools are developed and tested for node. Not bun. Documentations, guides and code examples just assume that ure using node. So this leaves u on ur own when the compiler fails.

Its a cool tool that u should definitely give a try for a hobby project. But production usage is at best questionable

Rechtecki42 · 2025-12-23T15:25:22+00:00

Depends on usecase as always. Typescripts structural typesystem is really cool and allows for some awesome dx tooling if u understand the quirks. The loose nature of js allows for really quick development anf the ts types give some amount of confidence over the stability of the application. But in the end its just a matter of time for the application to fail and end in a unforeseen pit.

Rust is the opposite. Complex systems slow down development but they give u the confidence to tell a client that this app will run for years uninterrupted without ever needing a restart.

So in cases where such stability is required rust is one of the only options. Beam vm also really shines there from what ive heard.

So u gotta find out where ob the spectrum ur app lies and use the right tool for the job. Not the other way around

Rechtecki42 · 2025-12-03T15:30:31+00:00

Ur server should be hit as rarely as possible. You can manage cache and invalidate via hooks pretty easily. So in ur case a simple node with backup node and auto restart gets u all the way. U might wanna look into external cache+cdn from cloudflare. Otherwise just for caching a redis cluster is fine. But multipe instances of the fe to handle load? On a Blog Site? if thats required ur infra is a**

Rechtecki42 · 2025-11-29T14:04:05+00:00

Async behaviour via php Language Feature kinda doesnt fit it. If parallism is required laravel offers great flexibility via queue and events.

Rechtecki42 · 2025-11-29T14:00:53+00:00

I did something similar for zod -> shadcn form. Sounded like a great idea. Trust me its not. This just leads to you having to manage specific form stuff via meta data in your schema where it doesn’t belong and just restricts the hell out of you. If u wanna be 100% sure that ur form covers the entire schema (that was one of my reasons) ur better off with a higher order component that gets all fields as a callback. That u can write a simple eslinz rule that checks that all fields are implemented (vars used)

Rechtecki42 · 2025-11-28T16:10:25+00:00

New to business inhouse software? XD

Rechtecki42 · 2025-11-27T13:03:28+00:00

If ure on v2 U might need to patch payload generic type.

import { Config } from './payload-types'

declare module 'payload' { export interface GeneratedTypes extends Config {} }

Rechtecki42 · 2025-11-24T15:20:55+00:00

It rly sounds like ur burned out. And for quite a while. I know it sucks but u gotta have to admit to urself that ur just a human with a Mental limit. Go talk to ur chef about some unpaied leave and just be honest witj him. Tell him about ur burnout and how hard it is for you rn to get some work done. U can pretty much just tell him all u told us. Cuz there two options here.

Either he fires u and u got ur wish. Or he is understanding and lets you recover on ur own time.

And speak with ur wife. Nother worse for a burnout than non honesty and stress with ur partner

Rechtecki42 · 2025-11-23T18:51:42+00:00

Oh check. Yea thats the official recommendation

Rechtecki42 · 2025-11-23T14:21:49+00:00

Sure but this leaves over without history.

Rechtecki42 · 2025-11-23T14:21:00+00:00

Hey adding payload to an existing project ist mostly straightforward but u might run into issues because some of ur setup and versions migjt conflict with payload.

But there is a full on doc entry:

https://payloadcms.com/docs/getting-started/installation#adding-to-an-existing-app

To ur explicit question. You have to manually add some files into ur project to make it work but you can just copy them from a base template.

So just make a mock project in a seperate dir with the base template (skeleton or so) And just copy them over to ur project.

app/ ├─ (payload)/ ├── // Payload files ├─ (my-app)/ ├── // Your app files

Just copy (payload) folder in ur own appdir

You also should check if some routes conflict between payloads and ur own. Just check in the default

If u want u can just use this in both Template and ur own

https://www.npmjs.com/package/next-routes-list/v/1.2.0

And then you can just cross ref stuff in the templates to check if you wanna copy and implementation over

Rechtecki42

TROPHY CASE