typingmonkey

9 ms·

31.
RxDB 11.0.0(github.com)
6 points by typingmonkey 5y ago|0 comments
32.
by typingmonkey 5y ago
As I understood, they will directly begin to dismantel the plants. So there is no way back.
33.
by typingmonkey 5y ago
Like telegram did with the translate api, there is also a way to have an unlimited api for search results. You have to find one of the old mobile pages of google.
34.
by typingmonkey 5y ago
I can totally relate to that. When designing the RxDB GraphQL replication [1] protocol, it made things so much easier when the main data runs via normal request-response http. Only the long-polling is switched out for WebSockets so that the
35.
EventReduce optimizes database queries that run multiple times(github.com)
3 points by typingmonkey 5y ago|0 comments
36.
by typingmonkey 5y ago
Whenever I research the performance problem of a JavaScript library, I stumble over many deep clones even when it is not necessary most of the time. People are just not aware how CPU expensive a deep clone in JavaScript is, even more on big
37.
Demystifying Storage for Web Apps(expressflow.com)
2 points by typingmonkey 5y ago|0 comments
38.
by typingmonkey 5y ago
I analyzed [1] that problem and tried to reproduce data loss with LokiJS, which also has everything in memory and only partially writes to disc. It is very hard to reproduce a loss. You can call the saveDatabase() when the window 'unlo
39.
by typingmonkey 5y ago
LocalForage is similar slow as IndexedDB https://pubkey.github.io/client-side-databases/database-comp...
40.
Why IndexedDB is slow and what to use instead(rxdb.info)
105 points by typingmonkey 5y ago|45 comments
41.
by typingmonkey 5y ago
Is it possible to also expose a websocket that emits changes?
42.
by typingmonkey 5y ago
Does DuckDB support multi tab usage? How big is the wasm file that must be loaded?
43.
by typingmonkey 5y ago
I just described the world how it is. I did not create it, I did not made the browser. I do not understand your point. You want to complain about what exactly?
44.
by typingmonkey 5y ago
The browser is an abstraction layer. It will always be slower. But all this does not matter because your user will not write 20 chat messages / second.
45.
by typingmonkey 5y ago
Yes, this is exactly what is happening. But still you only have one CPU in JavaScript, so the GUI part will take the resources from the database part.
46.
by typingmonkey 5y ago
> Syncing that local CouchDB to your web based CouchDB is very fast This is not true. When you compare the CouchDB replication with other replication protocols, it is slow. The reason is that CouchDB supports replication with many instan
47.
by typingmonkey 5y ago
Replication, Encryption, Conflict Handling, Multi-Tab-Support, Compression, Observability and many more..
48.
by typingmonkey 5y ago
I wrote so much things and posted it on HN over the years. There is just no way to make everyone happy, someone always complains that some infos are missing or too much. I now leave things out that can be googled and are already known by &q
49.
by typingmonkey 5y ago
When you insert 20 messages, there is way more happening than 20 db writes. Each insert will affect the UI which will cause a layout change. Also the changes will be replayed in different browser tabs and might also be replicated to the bac
50.
by typingmonkey 5y ago
Yes RxDB conflict resolution is equal to PouchDBs. At least for now, there are plans to improve from there where you have a global resoluting function instead of listening for conflicts in the changestream.
51.
by typingmonkey 5y ago
It is benchmarking the firestore JavaScript library that runs at the client.
52.
by typingmonkey 5y ago
Author here. I am using RxDB with Capacitor (iOS and Android app). You can use the SQLite based pouchdb adapter with capacitor. It keeps your data and is (sometimes) faster. Here [1] I have documented a whole section about how to use RxDB+S
53.
by typingmonkey 5y ago
I considered to add Supabase, RethinkDB and meteor. But they are not really client side databases. They realtime stream query results from the server to the client.
54.
Offline-First Database Comparison(github.com)
415 points by typingmonkey 5y ago|155 comments
55.
by typingmonkey 5y ago
So the plain data is smaller because some information comes from the schema instead of the object. Guess what, you can do the same with json already [1] [1] https://github.com/pubkey/jsonschema-key-compression
56.
by typingmonkey 5y ago
I would say most browser users do not care about developer tools. They are normal people, they do not debug stuff.
57.
by typingmonkey 5y ago
Yes this clarifies it, thank you.
58.
by typingmonkey 5y ago
I do not understand this. You have better "desktop CPUs" and want to be 4x faster then github actions? Most of CI time is spend on downloading stuff or moving files, how can this ever be 4x faster with just better CPUs? > On av
59.
by typingmonkey 5y ago
Yes, most of them. I think the risk by using strike is much less and you do not have to be online to accept payments. Which is not a good sign for general LN adoption.
60.
Why NoSQL(rxdb.info)
90 points by typingmonkey 5y ago|120 comments

More ›