Hi, I work on Lakebase (but not on storage), here's how I understand it.
For Lakebase and Neon, our architecture needs the caching layer regardless (what we call Pageservers). Performing reads from S3 directly is too slow so we reconstruct pages and keep them on an nvme server for faster querying. Changing the format on S3 to be Parquet effectively introduces no additional copies over our existing architecture
How is it a poor choice of words? It might not be "native" UI, but they never claimed as such.
I've always felt that native UI on Linux always looks incredibly ugly and I'd much rather use a nicely styled HTML+CSS layout instead.
In my experience, Electron mostly gets flak for being bloated and slow, it not being native is sometimes a secondary point people add on top.
I've always wanted to build a direct-browser integration that could use HTML+CSS for the layout, but avoids needing a JS runtime. Idk how lightweight servo is but one day I hope I will see my idea come to light
It can also be encoded as a bloom filter for very fast checks. Then you can defer to the replicated LSMTree that's stored replicated on your local node
Glad I've jumped ship to Zed+ACP. I liked the idea of the new agent window view, but it's obviously slop and hasn't had a any polish or care put behind it given the number of bugs I keep seeing.
Zed is so much more stable and sleek and the agent view (threads) actually integrates nicely in a real editor. The side editor in the agent window was so much worse than the vscode base I expected, I have no idea how they dropped the ball so hard here.
> I take this to mean they threw a bunch of incoherent bullet points at the AI for it to denoise and render into paragraphs
What I generally tend to do is have a long conversation with an LLM for at least 30 minutes, and then have that turn into the first draft. It might be considered lazy, but I've never been very good at editing prose - I always end up making a mistake that makes it more confusing.
If after the conversation I find it's an idea worth sharing (usually with colleagues), then getting the LLM to turn it into something readable is the best option available to me. If I had to do it myself, it likely wouldn't make it before I move onto something else. And it has had my genuine input throughout the long conversation, I wouldn't call it incoherent nor am I an idiot for not being able to express myself in long form writing
This might apply to the AI integrations in Gmail, but someone's own agent setup might have more references saved privately than yours. You can't ask your AI to search through my personal notes.
It's a signal, and probably a high success signal in open source slop discovery, but it's more of a correlation than a causation. I've seen lots of changes that bear the co-authored tag that have had a lot of thought behind the code changes.
I haven't experienced these issues with latest models writing performant and correct rust fwiw. It does seem to understand Rust's safety concepts quite well when working on reviewing or writing code
It's worth stating that historically these right-wing culture protests have been a bit more violent in nature than most protests are. I'm not suggesting that everyone in the protest is violent, but there's enough mob mentality that makes me (someone who lives in London) uncomfortable.
It's not a one-shot prompt. I'm chatting with the agent for a while collecting knowledge and forming a substantive set of documentation or references. This takes a lot of time and effort to collect.
After this, I just get the agent to refine a doc for humans to read. I'm not very good at writing for humans, and it takes me far too much time that I usually give up and move onto other more important things instead. So it benefits everyone that I have vetted a set of documents in my expertise domain and shared them, even if not written by me they contain my ideas.
I'm very aware when I pick Apache-2. I want attribution for my work, but I don't care about open source purity. I respect closed source software and I put my open source code up for free because I don't care to profit off of my hobbies.
For Lakebase and Neon, our architecture needs the caching layer regardless (what we call Pageservers). Performing reads from S3 directly is too slow so we reconstruct pages and keep them on an nvme server for faster querying. Changing the format on S3 to be Parquet effectively introduces no additional copies over our existing architecture