Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. OpenAI hacked Australian health site, notified authorities 3 months later (bmj.com)
    —discuss
  2. Schools are experimenting with AI with little evidence or policy to guide them (npr.org)
    —discuss
  3. ESP-SDR: Raw IQ Capture with Espressif's ESP32 Chips (espargos.net)
    —discuss
  4. Early AMD 'Gorgon Halo' AI mini-PC packs 192GB RAM for an eye-watering $7,099 (tomshardware.com)
    —discuss
  5. A-ha, Take On Me – recreated in JavaScript (dittytoy.net)
    —discuss
  6. Zuckerberg Loses Another $11B Monday as Meta Shares Slide (forbes.com/sites/fionariley)
    —discuss
  7. KeePassXC 2.8.0 (Beta 1) released (keepassxc.org)
    —discuss
  8. Dobium: $0 commission prediction exchange (dobium.com)
    —discuss
  9. Show HN: PHNTM ONE: Self healing AI assistant running on a Raspberry Pi5 (phntmcore.com)
    1comments
  10. Plugging the leaks in your browser (privacymagic.com)
    —discuss
  11. Bringing life back into the Facebook Portal (github.com/dekayrekords-oss)
    —discuss
  12. Monzo in talks with Brazil's Nubank about sale (ft.com)
    —discuss
  13. Roaring Twenties (wikipedia.org)
    —discuss
  14. Towards Universal Post-Training for Robotics (pd-perry.github.io)
    —discuss
  15. AI chatbots give us a narrow slice of knowledge (ku.dk)
    —discuss
  16. App Store: a few bad apples or one bad Apple? (lapcatsoftware.com)
    —discuss
  17. GrapheneOS – When an App Is Slow (wirelessmoves.com)
    —discuss
  18. Comparing fuel pumps to electric vehicle public chargers (gov.uk)
    2comments
  19. Natural History of a New Idea (kevinkelly.substack.com)
    —discuss
  20. Why Dogs Fight Bears (nytimes.com)
    —discuss
  21. Anti-Modern Modernism and Its Antidote: James Joyce and HART Crane's the Bridge (sociological-eye.blogspot.com)
    —discuss
  22. Nvidia Open Agent Safety Platform (nvidia.com)
    1comments
  23. Show HN: Nibia Fabric – Turn everyday computers into a shared AI compute cluster (github.com/nibia-ai)
    —discuss
  24. Redis Still Chasing Valkey: 50M Sorted Sets, Round Three (gomomento.com)
    —discuss
  25. Dstv installation Kyalami tech Installations (techinstallations.co.za)
    1comments
  26. Asciicity.live (asciicity.live)
    —discuss
  27. DKLM 2026 and the Silent Crisis of the German Healthcare System (labnews.ai)
    —discuss
  28. A private alternative to cloud image converters and compressors (imagerry.com)
    —discuss
  29. What's New in Git 2.56.0 (about.gitlab.com)
    —discuss
  30. 'The PR guys hated the name': The 1k-year-old story behind Bluetooth (bbc.com)
    —discuss

Ask HN: React Native or Flutter when the back end is Node?

4 pointsby 39m ago
8 comments
Really confused between React Native and Flutter. I’ve mostly worked with Flutter and a little bit with React Native, but that was quite a while back, so I’m not sure how things stand today.

I’m building a project with a Node.js + tRPC backend, so React Native is looking really tempting cause of that Typescript.

While researching I've seen mixed reviews about performance in React Native like people saying they've spend weeks finding and managing performance issue which does makes me worry.

The app I wanna build doesn't have complex canvas work or crazy animations. For a typical production app, what’s the performance situation with React Native vs Flutter now? Are there any major concerns which I should know before looking in React Native?

35m agoHN ↗

If you aren't doing native apps, my recommendation is to use the same language across full-stack apps. You can share things like zod types and validation logic (in the frontend for quicker user feedback, on the backend because you never trust user provided values)

33m agoHN ↗

That's why it looks so tempting but the main reason having mixed feelings because of reviews everywhere about React Native that it's doesn't have that kind of performance! And yeah zod and tRPC is a lovely combo for building app loving it with Next.JS

29m agoHN ↗

There are a lot of React Native apps out there, the issues I see are more around platform glitchiness or workarounds than performance.

The main thing to watch out for is blocking the rendering or event loop. I've definitely seen apps where a slow API call blocks everything else. So less about performance and more about knowing how to do concurrency well.

27m agoHN ↗

absolutely! got any tips that I should be using while working on it :)

25m agoHN ↗

let the agents debug these things, without needing images, the feedback loop is key

I haven't done any mobile stuff in a while, but there should be enough around to wire the agents up into a good environment, like remote chrome-devtools (with or without the MCP).

pnpm workspaces, makes having multiple packages with internal dependencies (like core and components) easy to manage in the dev workspace

32m agoHN ↗

I have a similar stack (using oRPC instead of tRPC, recommended!) and I'd say React Native, specifically Expo UI: https://docs.expo.dev/versions/latest/sdk/ui/

This will get you the most native feel across all platforms (e.g. Liquid Glass) and keeps you in one language (TypeScript).

No performance issues to note in particular because Expo UI is (basically) native - it just uses SwiftUI and Jetpack Compose under the hood.

29m agoHN ↗

what about app size and ram usage like heard bad review about that. I just wanna be sure before I start like real sure :)

6m agoHN ↗

It depends do you want to maintain ii? Do you use AI? Performance issues can always be solved. Do you want to use browser’s capabilities or keep control in your own backend ? Less frameworks is better, use e.g the same for everything.