Channels

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

Learning TypeScript

Printed in by 32 pieces from 4 sources · the whole ledger

  1. Biome and the Future of JavaScript Toolingsoftwareengineeringdaily.comaudio
  2. Biome and the Future of JavaScript Toolingsoftwareengineeringdaily.comaudio
  3. Biome and the Future of JavaScript Toolingsoftwareengineeringdaily.comaudio
  4. Biome and the Future of JavaScript Toolingsoftwareengineeringdaily.comaudio
  5. React Native at Scalesoftwareengineeringdaily.comaudio
  6. React Native at Scalesoftwareengineeringdaily.comaudio
  7. React Native at Scalesoftwareengineeringdaily.comaudio
  8. React Native at Scalesoftwareengineeringdaily.comaudio
  9. Open Source Sustainabilitysoftwareengineeringdaily.comaudio
  10. Open Source Sustainabilitysoftwareengineeringdaily.comaudio
  11. Open Source Sustainabilitysoftwareengineeringdaily.comaudio
  12. Open Source Sustainabilitysoftwareengineeringdaily.comaudio
  13. Prettier and Opinionated Code Formatting with James Longsoftwareengineeringdaily.comaudio
  14. Prettier and Opinionated Code Formatting with James Longsoftwareengineeringdaily.comaudio
  15. Prettier and Opinionated Code Formatting with James Longsoftwareengineeringdaily.comaudio
  16. Prettier and Opinionated Code Formatting with James Longsoftwareengineeringdaily.comaudio
  17. Next-Gen JavaScript Package Management with Ruy Adorno and Darcy Clarkesoftwareengineeringdaily.comaudio
  18. Next-Gen JavaScript Package Management with Ruy Adorno and Darcy Clarkesoftwareengineeringdaily.comaudio
  19. Next-Gen JavaScript Package Management with Ruy Adorno and Darcy Clarkesoftwareengineeringdaily.comaudio
  20. Next-Gen JavaScript Package Management with Ruy Adorno and Darcy Clarkesoftwareengineeringdaily.comaudio
  21. Node.js in 2026 with Rafael Gonzagasoftwareengineeringdaily.comaudio
  22. Node.js in 2026 with Rafael Gonzagasoftwareengineeringdaily.comaudio
  23. Node.js in 2026 with Rafael Gonzagasoftwareengineeringdaily.comaudio
  24. Node.js in 2026 with Rafael Gonzagasoftwareengineeringdaily.comaudio
  25. Blocking Software Supply Chain Attacks with Feross Aboukhadijehsoftwareengineeringdaily.comaudio
  26. Blocking Software Supply Chain Attacks with Feross Aboukhadijehsoftwareengineeringdaily.comaudio
  27. Blocking Software Supply Chain Attacks with Feross Aboukhadijehsoftwareengineeringdaily.comaudio
  28. Blocking Software Supply Chain Attacks with Feross Aboukhadijehsoftwareengineeringdaily.comaudio
  29. Running Doom in TypeScript with Dimitri Mitropoulossoftwareengineeringdaily.comaudio
  30. Running Doom in TypeScript with Dimitri Mitropoulossoftwareengineeringdaily.comaudio
  31. Running Doom in TypeScript with Dimitri Mitropoulossoftwareengineeringdaily.comaudio
  32. Running Doom in TypeScript with Dimitri Mitropoulossoftwareengineeringdaily.comaudio

A printed name is a run of capitalised words as a publisher wrote them. Equal spellings are shown together; that does not make them one person, place or organisation.

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