vaughan

21 ms·

211.
by vaughan 5y ago
It's driven by library developers wanting to prevent access to internals. I was annoyed by it initially because I love poking around in internals and it makes it easy to add missing functionality or fix bugs, but I can kind of understa
212.
by vaughan 5y ago
Yep, I know the pain all too well. ESM is also currently a disaster as many popular packages migrate without transpiling to CJS and you cannot call ESM from CJS contexts. As you said, it's good to separate the ecosystem from the langua
213.
by vaughan 5y ago
But not relational...
214.
by vaughan 5y ago
It is interesting that we use declarative SQL to query from the DB, but then when we get it into the app, we are manually doing further filter, mapping and joining of data. And then denormalizing it into a cache in a separate data store. Lo
215.
by vaughan 5y ago
JS and Rust are best friends. Deno is written in Rust. And many Node native libs are being written in Rust.
216.
by vaughan 5y ago
I'm not sure OC is asking for NoSQL - just a better experience with SQL migrations. The relational model always requires a judgement call about how normalized to go. If I have a deep nested json object of data, you could argue to defin
217.
by vaughan 5y ago
Wanting to make changes to your schema easier, doesn't necessarily mean you need NoSQL. I think it's a question of having the right tooling. It would be cool if you could dump an unstructured blob of data in a psql table. And then
218.
by vaughan 5y ago
I could see it as taking a typical day's worth of transactions, creating new test db from this log, and then letting a tool try out different indexes based on some common heuristics and re-run the queries and benchmark. Because often i
219.
by vaughan 5y ago
https://wiki.postgresql.org/wiki/Incremental_View_Maintenanc...
220.
by vaughan 5y ago
Becomes too complex. You have to maintain mapping of old columns to new columns and when you are splitting tables it becomes too crazy.
221.
by vaughan 5y ago
There are so many times I wish a blog post was an app that just had a nice gui to do guide me through the steps they suggest, instead of manually modifying config files and running bash scripts. SQL GUI tooling is lacking.
222.
by vaughan 5y ago
> Blurring (safely!) the line between database and the app using it What do you mean by this? > Comprehensive auto tuning...automatic schema tuning You should be able to maintain a logical database schema, and then flip a toggle for t
223.
by vaughan 5y ago
absurd-sql[1] is the coolest thing I've seen in this space so far. sqlite.js brings sqlite to the browser via wasm, and then absurd-sql implements the storage layer in IndexedDb. So now we have an sqlite compatible db in the browser to
224.
by vaughan 5y ago
Hasura discusses why they chose polling here ( https://github.com/hasura/graphql-engine/blob/master/archite... ). > WAL: Reliable stream, but LR slots are expensive which makes horizontal scaling hard,
225.
by vaughan 5y ago
I feel like Rethink would have done a lot better if it were started closer to today. Funnily enough, in 2009 it was originally an SSD-optimized storage engine for MySQL. The dev experience and API were great. It was the "relational mon
226.
by vaughan 5y ago
> and for that applications you should build something custom. Given the spirit of the original post, I think avoiding "build something custom" is the point. It should be a toggle in the database. > you don't have a 1:1
227.
by vaughan 5y ago
> 4. Support streaming I feel the same. Streaming is so lacking in most dbs today. RethinkDB's `.changes()` was really cool. I wonder if PSQL will eventually do it, or whether a new DB will take over. Everyone went to Mongo then ran
228.
by vaughan 5y ago
Very cool - I had no idea this existed. I wonder if this could be useful for using ramdisks when working with temp tables.
229.
by vaughan 5y ago
> good practice for client code to make no assumptions about the internal representation If your internal representation and API start to differ then it adds complexity fast. Its far better to have as close to a 1-1 mapping for your back
230.
by vaughan 5y ago
> Zero impedance mismatch I see the problem here being that too many manual optimizations need to be done when implementing a schema. You start with a logical schema (ERD diagram) and then implement it via a physical schema with denormal
231.
by vaughan 5y ago
1. Streaming SQL Real-time queries should be the default. Some kind of smart query invalidation (similar to incremental view maintenance) as a result of DML statements. 2. Can run in a web browser / mobile phone Your client-side cache
232.
by vaughan 5y ago
I don't think so, still feels primitive.
233.
by vaughan 5y ago
I only use CC for albums I want to share. LRC will always be my source of truth. The cool part of the workflow, is you can just tag photos you want to share in LRC, and then they sync and they're in the cloud for people to view at max
234.
by vaughan 5y ago
So I am only using CC for sharing albums which is the sweet spot. I just sync one album of photos I want to share to CC. LRC stores every photo I have ever took on a 10TB WD MyBook. I'm not sure how well CC syncs changes back to LRC th
235.
by vaughan 5y ago
I use Lightroom Classic (LRC), but recently tried Lightroom CC and its pretty good. I can sync an album from LRC to LRCC, and then can share the album instantly online - so friends/family can see the RAW quality photos. When I make som
236.
by vaughan 5y ago
> I've relocated internationally a dozen times, so a NAS doesn't work for me. Same here. I used to use 2x Seagate portable 5TB. Would mirror one to the other every week. Now I use a Western Digital MyBook 20TB in RAID 1, and ba
237.
by vaughan 5y ago
> well planned out data structure and proper migrations Schema design is a process of discovery and code-first approaches become too sticky to change. I think we need to head back to the ease of MS Access for data modeling and migrations
238.
by vaughan 5y ago
Schemas and requirements evolve over time. There is no perfect schema. Schema design always results in endless "are we gonna need this?" questions, and usually everything is postponed down the road because it adds needless upfront
239.
by vaughan 5y ago
Yeh, this is lacking right now. GQL makes joins much easier to write than SQL, which is what you want to be using in your components. But GQL is not great for offline-support and caching. You want your frontend to know about how your data r
240.
by vaughan 5y ago
Great post. Captured the problem nicely. I went on a similar journey recently. There is a moment when you step back and realize that all the data-wrangling code we write in apps is essentially what an SQL query planner does. And our fronten

More ›