phrasecode

86 ms·

1.
by phrasecode 9mo ago
You're welcome. And of course achieving that "exceptionally high throughput and performance" is the ultimate goal for a system of this nature. Now, yes — LinkedQL reasons explicitly in terms of transactions, end-to-end, as co
2.
by phrasecode 9mo ago
Thanks — this is a really good scenario to walk through, and I’m happy to extend the conversation. First, I’m implicitly assuming your 10 ECS tasks are talking to the same Postgres instance and may issue overlapping queries. Once that’s the
3.
by phrasecode 9mo ago
Would you clarify what a "transaction" in this instance would mean? LinkedQL definitely optimizes at multiple levels between a change happening on your database and the live result your application sees. The most significant of th
4.
by phrasecode 9mo ago
Great questions — happy to clarify how deployment and lifecycle work today. Let me begin by answering: what exactly is this engine? It's simply a computation + cache layer that lives in the same process as the calling code, not a serve
5.
by phrasecode 9mo ago
Honestly, that was solely crafted by me. That comment needed to be formatted and properly sectioned.
6.
by phrasecode 9mo ago
Ah yes — good catch. The commit history definitely isn’t following Conventional Commits right now. Things got a bit loose during fast iterations, but I’ll follow the convention going forward.
7.
by phrasecode 9mo ago
Thanks for spotting that — to clarify: the current production implementation of Live Queries is Postgres only. MySQL/MariaDB support is in progress (binlog-based) and is why the docs say “coming soon.” The post wasn’t meant to imply th
8.
by phrasecode 9mo ago
Author here. Sad to hear that you perceive the docs and comments here as LLM generated. I'm genuinely curious what in particular gives you that impression.
9.
by phrasecode 9mo ago
Author here — thanks for checking it out. Short answer: the core LinkedQL live query engine runs on the backend today, and there’s an embeddable variant (FlashQL) that runs directly in the frontend with the same LinkedQL capabilities – live
10.
The LinkedQL engineering paper – the Live Queries engine(linked-ql.netlify.app)
2 points by phrasecode 9mo ago|0 comments
11.
by phrasecode 9mo ago
Thanks for reading through and for these questions. I'll take them in their order: --- Auth / RLS Yes — LinkedQL works with Postgres Row-Level Security. Each LinkedQL connection is equivalent to a regular DB connection (e.g., new
12.
by phrasecode 9mo ago
Author here — a bit more detail on architecture and guarantees Happy to dig into internals if anyone’s curious — how live updates propagate, how JOINs and complex queries resolve, consistency expectations, worst-case scaling, etc. To keep t
13.
Show HN: LinkedQL – Live Queries over Postgres, MySQL, MariaDB(github.com)
31 points by phrasecode 9mo ago|22 comments
14.
by phrasecode 2y ago
I'm glad at that. Would you also consider leaving us a star on github?
15.
by phrasecode 2y ago
Thanks for a particularly exciting feedback. I'm sure you'll have more to say after you've tried this out. That said, I agree that I haven't done a perfect job there in the sample schema.json area. Nice catch! I'll
16.
Show HN: Linked QL – a "magic wand" query client for your database(github.com)
6 points by phrasecode 2y ago|4 comments
17.
by phrasecode 3y ago
I love how we can talk about differences and preferences here like this. Now, I can't wait to put my thoughts further together on the pros and cons of a HTML-first approach like OOHTML's vs a JS-first approach like React's an
18.
by phrasecode 3y ago
Monkey-patching native DOM APIs is really how polyfills are made. This way, people are able to simulate an idea and have a more productive conversation around it. All with a view to having it succeeded by a native implementation.
19.
by phrasecode 3y ago
LOL
20.
by phrasecode 3y ago
Thanks for your sharing your thoughts.
21.
by phrasecode 3y ago
Your feedback really stands out here dude. I'm hoping that the whole conversation here and some of the frustration will lead to something even better for OOHTML.
22.
by phrasecode 3y ago
Author here. Looks like you missed something about the last update thing. I do actively work on it and ever poised to incorporate feedback. Don't hesitate to open an issue on project repo when you do use it on a hobby project.
23.
by phrasecode 3y ago
This is a great feedback and I'm sure that this conversation and some of the frustration around will help us get even better.
24.
by phrasecode 3y ago
*building a Progressive Web App
25.
by phrasecode 3y ago
This is a great feedback and I'm sure that this conversation and some of the frustration around will help us get even better.
26.
by phrasecode 3y ago
Why not we think in terms of "tradeoffs"? You'll find that there a million alternative syntaxes that could work but which would require seeking the right balance. Evan You's on this comes to mind again: https:/&#x2
27.
by phrasecode 3y ago
I do understand the frustration with syntax. The good thing is, none of that is finalised and we are in fact seeking people's idea of whats best. But one thing that always holds on this subject is "tradeoffs"! It's an in
28.
by phrasecode 3y ago
Feels good to know. It really already saves the day for me. If I get you correctly, is it that the other features like scoped styles and scripts, or html imports, don't look as good? For data binding, I can see peoples frustration: syn
29.
by phrasecode 3y ago
I might have done of lot of hating on DSL just like this. In fact, if you had followed the progress of OOHTML, there was never data binding. But there's something you find when you follow a practice driven process, and the realisation
30.
by phrasecode 3y ago
Nice catch. But yes we're currently buying a Progressive Web App right now with OOHTML. I'm happy to share after we've made progress.

More ›