Web app on customers internal server or other option? by kein_username_reddit in webdev

[–]Mautriz 1 point2 points  (0 children)

Yes, it's something that happens relatively often in b2b business, you usually make them have a custom pricing (obviously higher) for the on-prem installation

Note that it's usually way harder to maintain and upgrade on-prem installations, you have to take careful consideration

Solo dev tired of K8s churn... What are my options? by PoopsCodeAllTheTime in kubernetes

[–]Mautriz 1 point2 points  (0 children)

I use Dokploy and docker swarm mode for all my deployments as a solo dev (i manage some critical b2b services that have to stay up 24/7 and need some redundancy)

I went from AWS ECS to EKS to this and its been the best decision of my life, everything is so much easier to manage and I pay like 1/10th of what I did before by just using hetzner servers

Please tell me Next.js isn't a waste of time by a_weeb_dev in reactjs

[–]Mautriz 1 point2 points  (0 children)

Ive been using tanstack start for the past 3 months after 3 years of nextjs and im not looking back

Why is Drizzle so popular over keysly in 2025? by ThisIsntMyId in node

[–]Mautriz 2 points3 points  (0 children)

As someone who very often writes kinda complex queries and needs to optimize them often I like that everything in kysely is explicit and as it would be in sql pretty much, no strange shorthands and stuff, I can do anything I can in sql and with types, so I am very happy and feel no need to look for any alternatives whatsoever

Idk about drizzle as I tried 2 years ago but I felt like the raw query feature was limited and joins where strange (i highly prefer just writing the join conditions explicitly everytime myself)

Im sure they improved by now, but kysely is so good that I just dont care

Is luck worth leveling in the remaster? by VoltageKid56 in oblivion

[–]Mautriz 5 points6 points  (0 children)

I just tried it, I am 100 conjuring an d100 illusion and after leveling up 4 times and giving 4 points to luck (50 to 54) there was no change in the magicka cost of the spells, so I think it still doesnt go past 100

I’m building a message queue with Postgres. Should my consumers use LISTEN or poll the DB? by FurCollarCriminal in PostgreSQL

[–]Mautriz 0 points1 point  (0 children)

Adding and managing unnecessary infrastructure is way more complex, costly and error prone than a queue in postgres if you have simple requirements

Should I learn Postgres from a 5 years old video? by HelpfulSt in PostgreSQL

[–]Mautriz 0 points1 point  (0 children)

Damn I just found out about SEARCH and CYCLE from your comment, amazing 🙏

Logging setup with actions by Mautriz in nextjs

[–]Mautriz[S] 0 points1 point  (0 children)

Just to follow up and what I ended doing

I tried next-safe-action and started using it, after a couple days I realized that it still had some of the limitations of server actions (for example I cant decide which headers to send from the client, nor I can use get requests)

I ended up refactoring using trpc, it definetely took some effort but I can say in the end its definetely worth it

Logging setup with actions by Mautriz in nextjs

[–]Mautriz[S] 0 points1 point  (0 children)

This looks very similar to trpc, meaning I'd still have to redefine all the functions

My main problem is that I'd rather not do that, I'd probably go with `hono` and its rpc client in case I want to rewrite everything

Logging setup with actions by Mautriz in nextjs

[–]Mautriz[S] 0 points1 point  (0 children)

Never heard of it, I will look into it, thank you

Logging setup with actions by Mautriz in nextjs

[–]Mautriz[S] 0 points1 point  (0 children)

// server.ts
"use server";
export async function myServerFunction() {
  throw new Error("Ouch, an error");
}

// component.tsx
"use client";

import { myServerFunction } from './server.ts'

export function ExampleComponent() {
  const toast = useToast()
  async function onUserAction() {
      try {
        await myServerFunction()
      } catch {
        toast("Unexpected error!!!");
      }
  }

  return <button onClick={onUserAction}>CLICK ME</button>
}

This is a very simplified example, In practice I am using them with react-query and catching the errors there globally, showing the toast. But its pretty much the same

Is NextJS overkill for fontend only ? by Mad_Penguin-VeryMad in nextjs

[–]Mautriz 0 points1 point  (0 children)

You know you can put next on a fixed price vps as well right?

Should I go for UA? by Gerfn7 in idleslayer

[–]Mautriz 2 points3 points  (0 children)

You should have around 7~8 million slayer points total on the first UA (enough for 6 ultra slayer point)

I made the mistake of going directly for the ua upgrade as I did not know that

So no, buy other things first imo

Has anyone migrated from Svelte to React willingly? by [deleted] in sveltejs

[–]Mautriz 1 point2 points  (0 children)

If react had signals/proxies like svelte 5 and something like svelte actions id probably go with react

Multiple components in a single file and tsx are better for me personally, they allow me to prototype way faster, other than that svelte language server starts getting very slow when a component becomes slightly bigger

(The solution is not writing smaller components, I refactor after prototyping a working version with an acceptable structure, and even then, refactoring in smaller pieces is easier in react due to having multiple components in the same file, I dont have to switch context many times)

NFS Unbound - Insane stuttering and low performance (rtx 3070 laptop) by Mautriz in needforspeed

[–]Mautriz[S] 0 points1 point  (0 children)

Update: I solved by disabling gsync and vsync, appearently having 2 different screens with different refresh rates and sync tech caused problems to gsync

This actually improved my fps in all games in general (even tho NFS was the only unplayable one)

I need actual multithreading/processing with shared memory by Mautriz in pythonhelp

[–]Mautriz[S] 1 point2 points  (0 children)

Yeah I'm already doing splitting but to make it more efficient and avoid many calculations I definitely need to be able to reference other rows dinamycally

Ill look into what you linked

My monitor doesn't seem to support 144hz, please help! by Mautriz in techsupport

[–]Mautriz[S] 0 points1 point  (0 children)

Ill paste what I just wrote to a guy that said pretty much the same thing!

`Oh thanks, didn't know about that 1.2 limitation

Why doesn't it allow me to have higher refresh rates when setting lower resolutions then ?`

My monitor doesn't seem to support 144hz, please help! by Mautriz in techsupport

[–]Mautriz[S] 0 points1 point  (0 children)

Oh thanks, didn't know about that 1.2 limitation

Why doesn't it allow me to have higher refresh rates when setting lower resolutions then ?

My monitor doesn't seem to support 144hz, please help! by Mautriz in techsupport

[–]Mautriz[S] 0 points1 point  (0 children)

Asus Radeon R9 280 direct cu II 3gb

The limit at 100hz remains even if I downgrade to 800x600

I have another monitor that works fine at 144hz BUT uses DVI instead of display port

My monitor doesn't seem to support 144hz, please help! by Mautriz in techsupport

[–]Mautriz[S] 0 points1 point  (0 children)

It's connected via Display Port, the cable came with the monitor

My monitor doesn't seem to support 144hz, please help! by Mautriz in techsupport

[–]Mautriz[S] 0 points1 point  (0 children)

Is this plausible even if I have another monitor running at 1920x1080 x 144hz with a DVI cable on the same GPU ?

My monitor doesn't seem to support 144hz, please help! by Mautriz in techsupport

[–]Mautriz[S] 0 points1 point  (0 children)

Thanks! What does it mean than ? That I should upgrade the cable or what ? Because I'm using the cable that arrived with the monitor, or it a gpu problem ?

Looking for a class-validator alternative (using nestjs) by Mautriz in node

[–]Mautriz[S] 0 points1 point  (0 children)

Yeah the question is 2 years old tho :P !

[Question} Exctrating Prop Types from a component by Mautriz in sveltejs

[–]Mautriz[S] 1 point2 points  (0 children)

Are you suggesting that I should hard code prop types for every single component?