Channels

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

Android Developers

Printed in by 18 pieces from 1 source · the whole ledger

  1. Episode 213: Compose runtime and performancefeedburner.comaudio
  2. Episode 212: Happy birthday, Android Studio!feedburner.comaudio
  3. Episode 211: Rules about performance toolsfeedburner.comaudio
  4. Episode 208: Micro optimizationsfeedburner.comaudio
  5. Episode 207: AI development assistancefeedburner.comaudio
  6. Episode 206: Make it fasterfeedburner.comaudio
  7. Episode 204: Fan'otationsfeedburner.comaudio
  8. Episode 203: (W)rapfeedburner.comaudio
  9. Episode 202: AndroidX, Gradle and Metalavafeedburner.comaudio
  10. Episode 199: Compose performancefeedburner.comaudio
  11. Episode 198: Location location location, revisitedfeedburner.comaudio
  12. Episode 196: Android Studio, behind the scenesfeedburner.comaudio
  13. Episode 195: Mainliningfeedburner.comaudio
  14. Episode 194: Subtextfeedburner.comaudio
  15. Episode 189: Video Conferencefeedburner.comaudio
  16. Episode 180: Kotlin Magic Platformfeedburner.comaudio
  17. Episode 179: Flibberty Widgetfeedburner.comaudio
  18. Episode 53: ADB on ADBfeedburner.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