Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Typebase – A single-folder back end you write in TypeScript

typebase.io

Post reply on HN
Print view View original

31–40 of 62 posts

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#31

Post by SifatAhmed »

optimisticedits wrote: post #8
SifatAhmed wrote: post #6

This looks great. Question specifically on the Cloudflare Workers target: when you deploy there, does Typebase use D1 for the DB, or does the Postgres/Neon backend stay the same regardless of which server target you pick (Vercel/Workers/Deno) - i.e. is the DB layer decoupled from the server runtime, or does choosing Workers also mean choosing D1? I ask because I've shipped a small Workers+D1 service and the main fric…

I see no code there to automatically pick D1 for the DB when you deploy to Cloudflare. On Cloudflare, it should use the `@neondatabase/serverless` driver configured here https://github.com/typebase-io/monorepo/blob/fa3af0b71126caa...

[flagged]

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#32

Post by shunia_huang »

NoItsDanger wrote: post #20
pyrolistical wrote: post #9

It’s like next.js but for backend. Personally not for me. These are very productive once you learn the shape they expect. But the wheel needs to be reinvented on how to do everything. I ran have straight forward verbose code with no hidden control flow

I’ve been saying for years we need CCR (Client Centric Rendering). What we do is have the server just serve the page and let the client handle most of the rendering. It’s novel and innovative

Isn't this html + javascript?

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#33

Post by hirako2000 »

chrysoprace wrote: post #29
apsurd wrote: post #15

Earlier quoted context omitted.

that’s likely the promise but it’s so confusing and high cognitive overhead to maintain that backend frontend relationship. ‘use client’ - i think the special sauce for why people use nextjs is all frontend based. the frontend that comes from the backend. nextjs dx is a special kind of hell. disclaimer: im just a simple rails guy.

Next.js is a poor choice for a client-side application. It is first and foremost a server-side framework, and trying to force it to be client-side is to work against it. There are so many better options than Next.js for dedicated client-side front-ends.

Nextjs is also a bundler for web applications. And it deploys the front end assets.

It's yet another backend framework, added that it only runs on vercel infrastructure.

There are better front end and back end servers, those that simply rely on nodejs to serve. Next.js does that, without vercel.

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#34

Post by socialest »

pyrolistical wrote: post #9

It’s like next.js but for backend. Personally not for me. These are very productive once you learn the shape they expect. But the wheel needs to be reinvented on how to do everything. I ran have straight forward verbose code with no hidden control flow

I let the LLM tokens flow. Usually it ends up saving me innovation tokens.

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#35

Post by virgil_disgr4ce »

apsurd wrote: post #15
virgil_disgr4ce wrote: post #13

Earlier quoted context omitted.

Am I missing something? The entire point of next.js is that it's backend+frontend in one project

that’s likely the promise but it’s so confusing and high cognitive overhead to maintain that backend frontend relationship. ‘use client’ - i think the special sauce for why people use nextjs is all frontend based. the frontend that comes from the backend. nextjs dx is a special kind of hell. disclaimer: im just a simple rails guy.

I don't understand this perspective. I've developed, delivered and maintained countless Next.js projects and never come close to considering it "high cognitive overhead." It's among the nicest DX I've experienced. It has a lot of features, I guess, but you don't have to use them if you don't like them. Next.js has very little to do with the frontend. The frontend is literally just react, which is why I commented in the first place. People keep acting like it's a "frontend framework" which doesn't make any sense at all.

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#36

Post by brianpg »

dinkleberg wrote: post #28
ramon156 wrote: post #7

Fake reviews are a hard no-no imo. Really weird addition, but I suppose it wasn't you who got the idea. Looks an awful lot like a orpc, just built on top of drizzle instead of raw queries. I'm sure some people want this, but it seems like gross duct tape that will bite you in three years

I’m very surprised to see others commenting here that they like the fake reviews. Claude loves adding that shit, but you’re allowed to modify and remove the junk it produces. > * None of these people exist. We checked. Twice. Legal is chill Maybe I’m just the old man yelling at the clouds, but can we not have some integrity and actually put the truth out there? There is nothing wrong with using AI, but we’re still re…

I don't know, I have plenty of gray hair, but I still love a little tongue in cheek humor. I still remember the first cold email I got asking for 12 minutes of my time - I replied. Now if the disclaimer was buried at the bottom of the page and this product was asking for money, I would agree there is more of a trust issue here.

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#37

Post by brianpg »

I have deployed and maintained plenty of diff setups on GCP, AWS, colo, and I have also used AI for coding, my concern is do we really trust AI to do prod deploy and maintenance of the backend yet? Not to mention what are the limitations here, someone already mentioned queues? But for a straightforward site with limited complexities, it might be cool to try out.

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#38

Post by apsurd »

virgil_disgr4ce wrote: post #35
apsurd wrote: post #15

Earlier quoted context omitted.

that’s likely the promise but it’s so confusing and high cognitive overhead to maintain that backend frontend relationship. ‘use client’ - i think the special sauce for why people use nextjs is all frontend based. the frontend that comes from the backend. nextjs dx is a special kind of hell. disclaimer: im just a simple rails guy.

I don't understand this perspective. I've developed, delivered and maintained countless Next.js projects and never come close to considering it "high cognitive overhead." It's among the nicest DX I've experienced. It has a lot of features, I guess, but you don't have to use them if you don't like them. Next.js has very little to do with the frontend. The frontend is literally just react, which is why I commented in t…

React is a frontend framework. How do you get around that? It's invented entirely to handle client-side UX and reactive DOM updates which have to be DOM because it for the browser which is a frontend. Are you saying nextjs is the backend and react is just react, it's not nextjs' fault?

I'd say we disagree on the simplicity then: hydration, nextjs API reinventions of every interaction else 'use client' as an escape hatch which means it runs on the client but then what does the non 'use client' code do if nextjs is not a client-facing framework?

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#40

Post by andrewww-dev »

optimisticedits wrote: post #8
SifatAhmed wrote: post #6

This looks great. Question specifically on the Cloudflare Workers target: when you deploy there, does Typebase use D1 for the DB, or does the Postgres/Neon backend stay the same regardless of which server target you pick (Vercel/Workers/Deno) - i.e. is the DB layer decoupled from the server runtime, or does choosing Workers also mean choosing D1? I ask because I've shipped a small Workers+D1 service and the main fric…

I see no code there to automatically pick D1 for the DB when you deploy to Cloudflare. On Cloudflare, it should use the `@neondatabase/serverless` driver configured here https://github.com/typebase-io/monorepo/blob/fa3af0b71126caa...

Hey! For now we only support Neon but the idea is too add more DB providers soon. I wanted to build a "base layer" to show that Typebase is versatile enough, I'll add D1 to the priorities
Post reply on HN