Channels

Public threads, grouped by where they are happening. Pick a place to read its topics.

Reactivity

Filed under this by 16 pieces from 1 source · the whole ledger

  1. Can your database do this? Ep. 1: Magic cachingconvex.devstory
  2. GPT Streaming With Persistent Reactivityconvex.devstory
  3. Help, my app is overreacting!convex.devstory
  4. Implementing Presence with Convexconvex.devstory
  5. Fully Reactive Paginationconvex.devstory
  6. Launching Features Right on Time: Feature Gatingconvex.devstory
  7. The serverless revolution deserves more than just a serverless databaseconvex.devstory
  8. The future of databases is not just a databaseconvex.devstory
  9. Convex and the future of streaming infrastructureconvex.devstory
  10. Build a Reactive Backend for a Web Appconvex.devstory
  11. Managing Reactivity with useBufferedStateconvex.devstory
  12. Local and Remote State (Making Fast5 #1)convex.devstory
  13. Data Interactivity in the Serverless Future (HYTRADBOI 2022)convex.devstory
  14. Convex vs. Relational Databasesconvex.devstory
  15. Building reactive web apps on Convexconvex.devstory
  16. The unfulfilled promise of functional ideals on the webconvex.devstory

A topic here is a label each publisher printed on its own piece. Equal labels from different publishers are shown together; that does not make them one subject.

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Where this comes from

Solid branches are exact SourceFrontier census edges used by this page. Folded branches share the publisher but did not supply these items.

Hacker News

1 feed · 1 available · hn.algolia.com

text1 channel · 1 available
  1. Used here by hn-new hacker-attention Hacker News
    used on this pagehacker-attention

Latest

It's enough - vibecoding tag crossed from useless to harmfulThe vibecoding tag has been getting more and more useless for a while now. It lost the original meaning as the culture of software engineering with LLMs matured a bit. It got silly when posts talking about LLMs in general got tagged. It got useless when posts even mentioning some project created with LLMs in passing got tagged. Now it actually got harmful to the community when tagging posts turns away very valuable members https://lobste.rs/c/vecuxj I sighed and moved on for a while now as almost everything gets tagged - you can skip a word. But now it not only carries no signal whatsoever, it turns away people creating original technical content - which is what I assume anti-vibecoding people would actually like to see more of. Please split it or kill it. But we'd be better off without what exists today. Added: To be clear, I totally support people filtering out llm-generated or llm-centric posts. But right now everyone loses. And every day we lose a little bit more. Whether it's an original, interesting arviraptor lobste.rs