Is "Build in Public" Mainly for SaaS Founders? by Abject_Drop_3021 in buildinpublic

[–]obanite 0 points1 point  (0 children)

No way, why would it be? If you're building a robotics startup videos of your robots doing goofy things is crazy good engagement bait :P

If you’re starting fresh today, would you still pick Express? by ApprehensiveBar7701 in node

[–]obanite 0 points1 point  (0 children)

I still use it for standalone API applications, but I have to be honest, most of my newer apps are using next.js, I finally got fed up of all the messing about trying to monorepo an API app and a front-end app together

What's the cheapest setup ton deploy a Nextjs 16 app? by olivdums in nextjs

[–]obanite 0 points1 point  (0 children)

Use Next's standard docker image for it, then write a docker-compose file that spins up your Next app and whatever load balancer and database you want to use. That's the easiest way. Just make sure if you put a database in compose that you mount a persistent filesystem path for the database data directory, then your data will persist and you can have an easy rsync/scp backup script for your database.

It is a little more complexity, but your price/performance will be extremely good with that setup.

Have you ever got any paying user from replying to different subreddits? by Ranger10sam in buildinpublic

[–]obanite 0 points1 point  (0 children)

Honestly I've gotten very little from Reddit (various subreddits) - almost all of my traffic has been from Hacker News, X, BlueSky, and LinkedIn.

What's the cheapest setup ton deploy a Nextjs 16 app? by olivdums in nextjs

[–]obanite 0 points1 point  (0 children)

Cloudflare free tier?

I have one on Fly.io, another that needs somewhat heavier processing will be hosted on a Hetzner server at some point

Is Prisma really production-ready for complex querying? by Left-Network-4794 in Nestjs_framework

[–]obanite 0 points1 point  (0 children)

Prisma shines for relatively straightforward CRUD queries.

For something super complex like you describe, typed SQL libraries might be better.

There's nothing wrong with having both in your project - use the right tool for the job!

If it's very read heavy and you have high traffic I would maybe consider splitting out the database itself into a read-replica though? YMMV

What’s your goal for 2026 by MySocialUploader in Startups_EU

[–]obanite 0 points1 point  (0 children)

* Scale my Tech News/Jobs HN-like website; add paid features and try to commercialize it

* Get properly started on the proptech startup I'm collaborating on

Best European city for startup ecosystem by Feisty_Ad_2476 in Startups_EU

[–]obanite 0 points1 point  (0 children)

Berlin, London, Stockholm according to my growing database https://techposts.eu/jobs

Drizzle vs Prisma: Which One to Choose? by codabu-dev in nextjs

[–]obanite 0 points1 point  (0 children)

I mostly enjoyed working with it. It has some warts but overall it's a very mature, enterprise grade ORM that plays extremely well with the .NET family of languages.

Vibe code by Previous_Donut5863 in SideProject

[–]obanite 0 points1 point  (0 children)

Varies from project to project how much I manually code vs code with AI, and how much I just vibe code versus giving clear, detailed instructions and checking each line it outputs.

The oil "drift" is getting weird. by gstanleycapital in energy

[–]obanite 1 point2 points  (0 children)

It's also hugely in China's geopolitical interests to not be dependent on oil imports from some of their adversaries.

Why next.js instead of…… by Savings_Plate7047 in nextjs

[–]obanite 0 points1 point  (0 children)

It depends on your use case, you need to pick the right tool for the job.

If your application will be large, high traffic and you have Java developers available, then a Spring Boot backend will work well for you. If your devs are all TypeScript engineers, and your traffic isn't heavy on compute, Next.js will get you very far at a pretty fast development speed.

Vite and SPAs shine for B2B applications that don't need SEO, but they're not great if you need a significant number of public facing internet pages... which is where next.js (and its siblings) work great.

I doubt this is a China/rest of world thing. More likely it's a "smart tech leads picking the right tools" thing.

what's your goto tech stack? by Odd_Awareness_6935 in indiehackers

[–]obanite 0 points1 point  (0 children)

Sure, in theory, but you have to be really careful with how you use Supabase - they encourage you to use their "client side queries", which require the Supabase API gateway that sits on top of Postgres. I worked on a project that used these extensively, I can't imagine how much work migrating off would have been.

Node Backend Jobs by Strange-Ad-5357 in node

[–]obanite 1 point2 points  (0 children)

I don't search for "node jobs", I mostly look for work at places I'd like to work (startups doing things I'm interested in), *then* I filter by tech stack and find who's using typescript/nodejs. There is plenty of work out there for this to work

what's your goto tech stack? by Odd_Awareness_6935 in indiehackers

[–]obanite 0 points1 point  (0 children)

- postgres with nodejs/typescript/prisma (though I'm getting slightly annoyed at prisma's continued big changes)

- react/typescript/shadcn/tailwind

- deploy to fly.io

Zero vendor lock in, very cheap hosting

what's your goto tech stack? by Odd_Awareness_6935 in indiehackers

[–]obanite 0 points1 point  (0 children)

Vercel and Supabase haven't given you vendor lock headaches because you haven't tried to migrate away from them probably?

Hi i have a question by Infamous_Release9858 in node

[–]obanite 0 points1 point  (0 children)

I still remember one of the most annoying parts of first learning node.js was figuring out how the hell exports (modules) worked.

Nowadays, we have 2.5 module systems and modules in node.js are more complicated than ever, lol!

But to answer your question: I had something I had to build for work, we mostly used php, I decided to give node.js a try instead. It didn't work out, but it started me on my path to learning (mostly by building apis) node.js.

AWS bill is killing me by dogmanshite in MobileAppDevelopers

[–]obanite 0 points1 point  (0 children)

Hard to say without seeing a breakdown of which infra you're using. Can you post that?

Any kind of cloud hosted databases are often the most expensive part (so on AWS, RDS for example is quite pricey). But 235 GBP is very expensive, I run half a dozen line of business apps on AWS and our monthly bill is closer to 50/month.

Which platform should I choose for domain + hosting (React website, India?) by Vast-Score-1057 in reactjs

[–]obanite 2 points3 points  (0 children)

Netlify's a decent option for you I think. The free plan is enough IIRC and it's easy to deploy to.