Live data from Hacker News

Postgres WASM

supabase.com

51–60 of 190 posts

Re: Postgres WASM

#51

Earlier quoted context omitted.

Nah I think Supabase will do well. Meteor also did well all things considered. My point is really that they are revisiting all the same technology and product decisions and coming to the same conclusions. There's only one way to architect a PaaS. Next.js and Vercel's offerings are, essentially, also the same. The real risk is having one person build it all. They have a team but not really. Personally I believe that's…

> The real risk is having one person build it all > having to pretend to have a team In case you're talking specifically about supabase here, we're a full team: https://supabase.com/humans.txt

I just want to say what you've built is really great and works really well.

Re: Postgres WASM

#52
post #40

Another implementation: https://xn--yv9h.fm/emu/?m=jbdf7ZqvfgR4dCizypXxMP

This is cool! It's running debian and posgres 11. It's quite a bit larger (that's why we went with Buildroot, and frankly, we could do a lot better at trimming things down even more). But it's definitely a great implementation!

Re: Postgres WASM

#53
post #40

Another implementation: https://xn--yv9h.fm/emu/?m=jbdf7ZqvfgR4dCizypXxMP

This is cool! It's running debian and posgres 11. It's quite a bit larger (that's why we went with Buildroot, and frankly, we could do a lot better at trimming things down even more). But it's definitely a great implementation!

yes. this is just a test dummy for something bigger I have. we should chat. Feel free to DM me.

Re: Postgres WASM

#54
post #53

Earlier quoted context omitted.

This is cool! It's running debian and posgres 11. It's quite a bit larger (that's why we went with Buildroot, and frankly, we could do a lot better at trimming things down even more). But it's definitely a great implementation!

yes. this is just a test dummy for something bigger I have. we should chat. Feel free to DM me.

I originally went with buildroot too, but then I realized some things...

Re: Postgres WASM

#55
post #34

Earlier quoted context omitted.

There are some things that are uniquely beneficial for Postgres beyond the data storage - the main one I'm excited about is using PostGIS inside the browswer. OSM + PostGIS in the browser has the potential to do for Maps, what Figma's WASM approach did for design.

But why is it relevant that PostGIS runs inside the browser?

It's only relevant in that it "extends" the browser with a set of capabilities that it doesn't already have. You could also run everything via hosted database, but there may be situations where that is less-optimal than downloading the dataset once and leveraging the "offline compute" of a browser tab (for example, applications like ArcGIS Online)

Re: Postgres WASM

#56
post #53

Earlier quoted context omitted.

This is cool! It's running debian and posgres 11. It's quite a bit larger (that's why we went with Buildroot, and frankly, we could do a lot better at trimming things down even more). But it's definitely a great implementation!

yes. this is just a test dummy for something bigger I have. we should chat. Feel free to DM me.

Would love to chat! Love to get your ideas on this.

Re: Postgres WASM

#57
Huh, thought for a second that was a WASM support for stored procedures or something and was excited for a second

Re: Postgres WASM

#59
post #43

Earlier quoted context omitted.

Supabase developer here. I worked on this project with the guys over at Snaplet. One thing we are working on is putting postgres on an alternative filesystem using 9p. There's some really cool work by humphd that creates a filesystem inside IndexedDB[0]. We'd also like to maybe use the browser filesystem component to let you store the database on the host device in a path of your choosing. Not sure if these are possi…

Using IndexedDB, the forthcoming SQLite support in Chrome, or the browser filesystem components all might be good paths. Either way, what do you think about using WASI instead of Linux? I think it would reduce the overhead significantly.

I'm not familiar with WASI but I'll take a look. We're using Buildroot now and it's nice and small, but we could make it smaller by optimizing the kernel. Now, if I only know how to optimize the kernel without breaking things :)

Where's all those kernel hackers? Your help, we need. :)

Re: Postgres WASM

#60
post #57

Huh, thought for a second that was a WASM support for stored procedures or something and was excited for a second

Well it's not what you were expecting, but your idea sounds interesting too! Maybe you could muster the same open source forces to make it a reality?
Post reply on HN