Live data from Hacker News

Jazz – Apps with Distributed State

jazz.tools

91–100 of 179 posts

Re: Jazz – Apps with Distributed State

#91
Opening a demo chat app URL in Private Mode in Firefox results in perpetual "Loading..." screen and the following error on the console:

  Uncaught (in promise) DOMException: A mutation operation was attempted 
  on a database that did not allow mutations.

Re: Jazz – Apps with Distributed State

#92
post #69

Founder here - thanks for posting this! It’s getting late where I am so everyone who has questions please don’t be shy to ask, will elaborate in detail tomorrow!

The first question I have when I visit the site is, how is this different from Firebase?

On a high level, it solves a similar problem: a full backend so you mostly only have to write a frontend.

But Jazz does so in a completely different (local-first) way: it implements shared state on top of CRDTs and implements user identity and permissions based on public-key cryptography. This means you can create, store and share data from the client (even while offline) while still benefitting from cloud storage and real-time sync between devices and users by default.

Re: Jazz – Apps with Distributed State

#93

Mild nit: your website hijacked the back button, I had to spam click back like 30 times to get back to this hacker news comment thread

Just wanted to apologise to everyone for this, this kind of stuff drives me nuts and I'm not sure how I never noticed - it seems to be a result of how we use the iframe to render the chat example. Investigating!

Re: Jazz – Apps with Distributed State

#94

Earlier quoted context omitted.

It is already persisting and syncing data (fully encrypted) between the cloud and other users. You can think of Jazz as a distributed database itself. The coming-soon badges are about interop with traditional systems and higher level features we will add later. The fundamentals are solved and you can build full multiplayer, local-first apps with it. Does that make sense?

That sounds a lot more promising! Which brings in even more questions. What is the performance of these multiplayer experiences? Can I have 1000+ users all connected to the same chat session? What about 10,000? (these numbers might seem high, but they're what I'm expected to deliver in my day-job)

Not to go off topic but isn't performance metrics your responsibility ? Those are small numbers in reality, but if you are not performing your own tests and trusting the maintainer/publisher instead then you're not doing your 'day-job' properly.

Re: Jazz – Apps with Distributed State

#96

I love building with Jazz. It's so refreshing to build apps without thinking about backends. The number one thing I'm looking forward to is React Native support. Having local data that syncs is essential for many mobile apps, but there are no easy solutions yet. (Besides iCloud, which is limited to iOS/macOS) With Jazz, I can see a future where building syncing, cross-platform apps becomes effortless.

Thanks, Timo! Couldn't ask for better early adopters than you guys

Re: Jazz – Apps with Distributed State

#97

Earlier quoted context omitted.

Seems like you have lots of real world mobx experience. Have you ever read this article, basically saying that every front end state (including mobx) basically ends up being a worse version of a standard database? https://sqlsync.dev/posts/stop-building-databases/ I ended up finding that article after running into lots of the challenges with mobx State tree. I ended up trying to use watermelondb, a sqlite wrapped for…

Not GP but isn't it like saying that every database ends up being a worse version of a standard filesystem?

The analogy is more like an easier to implement version of a system(Custom Frontend Data Store) is worse than the standardized system (Database) rather than one system(database) being implemented on top of another system(filesystem).

The database has more features relative to filesystem, so we wouldn't miss the filesystem whereas a powerful indexing system is a feature in database missing in frontend data stores.

Some other examples below(Firefox plugins which are file browsers, FTP clients, C programs informally implementing subset of Common LISP features).

https://en.wikipedia.org/wiki/Inner-platform_effect

https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule

https://wiki.c2.com/?GreencoddsTenthRuleOfProgramming

Re: Jazz – Apps with Distributed State

#98

Earlier quoted context omitted.

Investigating why it’s breaking, was there a lot of people in that room?

when it broke there were 3-4 people in it

update: it's not the amount of people in it that broke this room https://news.ycombinator.com/item?id=41775047

Re: Jazz – Apps with Distributed State

#100
post #66

Curious how this compares with Meteor.

Meteor works on top of a traditional backend (typically MongoDB afaik?) to give you full-stack reactivity.

Jazz implements essentially a distributed database with permissions based on public-key cryptography, so you can meaningfully create, edit, share and store data on the client (even while offline), which gets synced to other users and devices (and stored in the cloud) whenever you're online

Post reply on HN