About storing history rather than current-state: I think Urbit works similarly.
Web Applications from the Future: A Database in the Browser
61–70 of 75 posts
Re: Web Applications from the Future: A Database in the Browser
#62this site appears to have exceeded its API rate limit. I wonder if that is a problem what will be solved by 'web applications of the future'. but i guess ill never know now
[deleted]
Re: Web Applications from the Future: A Database in the Browser
#63Getting API rate limit exceeded.
What is this hosted on?
Re: Web Applications from the Future: A Database in the Browser
#64Earlier quoted context omitted.
The common abstraction is a shared log. I'm boiling down my current side project ( http://www.adama-lang.org/ ) into reusable components. I'm also looking at WebAssembly as the way of doing work ( http://www.adama-lang.org/blog/micro-monoliths ) versus generic operations. Something interesting to consider is how important is offline use these days? If we get to an online-99.9% world, then the solution feels ... simpl…
Not long ago for work I was forced to use office365. It has collaborative editing feature that at the surface looks equivalent to Google docs, but in practice it's not: it wasn't reliable, I lost some edits a few times and even when it worked it was slow and sluggish (I knew that because I could see another person's shared screen in zoom), and it actually co-editing a file definitely felt a different experience. The…
real time collab is a figment of coders. real business processes are async in nature. what people really want is a easy way to open someone elses work, review it or add to it, and move on without all the emailing, chatting, while important, tend to be wlso a aync need thats note mvp to the process
Re: Web Applications from the Future: A Database in the Browser
#65Just use Firebase (firestore) ... It's got: offline first, latency compensation, pubsub, partial sync, authorization rules and serverside timestamps, and global transactions, and 5 9s availability backed by spanner for umpteen languages. https://tomlarkworthy.endpointservices.net/blogs/firestores-...
But then one day your Google account is closed by AI.
Or the product is abandoned by Google.
Re: Web Applications from the Future: A Database in the Browser
#66Earlier quoted context omitted.
Not long ago for work I was forced to use office365. It has collaborative editing feature that at the surface looks equivalent to Google docs, but in practice it's not: it wasn't reliable, I lost some edits a few times and even when it worked it was slow and sluggish (I knew that because I could see another person's shared screen in zoom), and it actually co-editing a file definitely felt a different experience. The…
real time collab is a figment of coders. real business processes are async in nature. what people really want is a easy way to open someone elses work, review it or add to it, and move on without all the emailing, chatting, while important, tend to be wlso a aync need thats note mvp to the process
Yeah whatever, I'm not a product guy and I do not pretend to have any clue about what people really want.
My point of my anecdote was that "connected" is not a boolean property.
Re: Web Applications from the Future: A Database in the Browser
#67Earlier quoted context omitted.
anyway, Postgrest already existed before GraphQL Here's a frontend devs BAAS, replete with soup and desert. (if you don't mind using db users, you even get user-auth per route...) https://postgrest.org/en/stable/
But hey, now I'm suspicious... are there Meteor dev's here? IIRC, right on the heels of Meteor we got Apollo from the same folks... The thing is, I'm puzzled, given the insane unnecessary complexity all this ES2030 and "build toolchains" (who knew javascript needed to be compiled, are we making binary bitstreams? is this an embedded microcontroller? is this an FPGA?) and other esoteric "let's replicate all of comp-sc…
Is Couch more secure than what I've come to expect from other Apache stuff?
Re: Web Applications from the Future: A Database in the Browser
#68Having been a dev on EtherPad, Google Wave, Coda, and other real-time collaborative apps with OT, undo, and so on... I think it's correct that, ideally, there would be a framework that handles real-time collaboration, undo/redo, and offline support for you, and then you build your app with these problems already solved. I will probably create such a framework eventually. I don't see it as a database engineering probl…
The common abstraction is a shared log. I'm boiling down my current side project ( http://www.adama-lang.org/ ) into reusable components. I'm also looking at WebAssembly as the way of doing work ( http://www.adama-lang.org/blog/micro-monoliths ) versus generic operations. Something interesting to consider is how important is offline use these days? If we get to an online-99.9% world, then the solution feels ... simpl…
But you'd want to allow the client query a snapshot before doing a full sync on the shared log.
Re: Web Applications from the Future: A Database in the Browser
#69A lot of the principles here echo the same design principles that MeteorJS was built on. Why didn't that work and why now? Is there something about _today_ that makes the web application space different?
People actually corralled into using webapps by big boys, phones not being pieces of shite.
Re: Web Applications from the Future: A Database in the Browser
#70Just use Firebase (firestore) ... It's got: offline first, latency compensation, pubsub, partial sync, authorization rules and serverside timestamps, and global transactions, and 5 9s availability backed by spanner for umpteen languages. https://tomlarkworthy.endpointservices.net/blogs/firestores-...
Firestore is not really offline-first. Your app wont start without internet connection because the auth handler needs that.