23 jul 24

fugg. ive been working solo on a project for a client, basically a booking system for a small hotel. originally i intended to write the entire little shit in nextjs, which is a framework i’ve never used before, tbh. only thing i saw is that a lot of people/small companies used it, so i kinda hopped on the bandwagon.

having basically done 0 research and having hopped on a completely new technology, i quickly found p shit things bout nextjs:

prisma kinda sucks (at least compared to jooq/flyway, which is what i usually use)
nextjs cant do actual background tasks / cron / queues (kinda bad for this project)
nextjs isnt as lightweight as i thought, lol.

(i kinda already ranted here)

so yea, i think for that project ill keep nextjs as a react frontend which is quite nice, but ill switch to my usual backend (spring / jooq / flyway / other garbage)

btw, for the AI nerds, today meta is officially releasing their best text gen model lineup so far, llama 3.1. at this point they’re basically super advanced, top of the line models you can run locally, tbh. look at their annoucnement; it’s kinda insane. also for more info check out /g/’s /aicg/ breads or similar.

anon 2024-07-24 (3:16 pm) No. 123162 reply

Looks like someone fell for the Javascript meme
anon 2024-07-24 (8:07 pm) No. 123163 reply

>>123162
yup. but i mean, you can't exactly avoid javascript. tho, i never liked using it for backend. for frontend its a necessary evil, and with typescript it's passable, i guess. still heavy/clunky/patching a fundamentally flawed initial implementation, but that's more common than not in software.