News for hackers. Stuff that matters.

simonhamp

Re:/dev/null: social network for developers on Friday October 16, 2026 @01:27PM (#50121498)
it was supposed to be public. maybe it got reverted. the team were moving super fast
Re:/dev/null: social network for developers on Friday October 16, 2026 @01:18PM (#50121356)
it's fully open source (https://github.com/nunomaduro/dev-null.sh/pulls) and received over 200 PRs in less than 48 hours
Re:Show HN: UpDown – free multiplayer Markdown documents on Tuesday October 13, 2026 @05:54PM (#50079423)
Here's a completely open document y'all can play around with

https://updown.laravel.cloud/5bd41bcc-28b0-4ba4-b5ce-db6ffa7...

Re:The 15-year search for a band that charted once and vanished on Thursday October 08, 2026 @08:49AM (#50005211)
Awesome story! Thanks for sharing. I will now go and have a listen
Re:Shopify moves back to Native from React Native on Friday September 11, 2026 @01:02PM (#49661677)
You need to check out what we've been building with SuperNative - it's one codebase, but you end up with two truly native apps.
Re:Shopify moves back to Native from React Native on Friday September 11, 2026 @10:41AM (#49659311)
But if you could get slick native mobile apps with less code (i.e. higher quality abstractions), that would be better
Re:Working with Git Worktrees in Magit on Friday September 11, 2026 @07:41AM (#49656747)
Yep. It's a full copy of the state of the origin
Re:Working with Git Worktrees in Magit on Friday September 11, 2026 @05:51AM (#49655834)
Just use copy-on-write clones. They're way more flexible, faster and easier to reason about.

I don't get spending all this time on tooling that tries to ease working with worktrees when they're just not the right abstraction for the way we're working now.

Re:Shopify moves back to Native from React Native on Friday September 11, 2026 @01:54AM (#49654040)
You don't have to ditch cross-platform building entirely just to escape dependency hell
Re:Shopify moves back to Native from React Native on Friday September 11, 2026 @12:19AM (#49653511)
Agree to a point, but human resource is literally the main cost in most businesses, so there's that

Conway's law also plays a big part here and it's kind of TBD to see if agentic development will minify or magnify its effects

Re:Shopify moves back to Native from React Native on Friday September 11, 2026 @12:11AM (#49653460)
100% with you. I'm fed up of having my M3 36GB run out of memory because I have Chrome, Slack, Discord and Claude all open at the same time

That's why I'm building SuperNative

Re:Shopify moves back to Native from React Native on Friday September 11, 2026 @12:06AM (#49653423)
I hate to break it to you, but we already have it: it's called PHP
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:52PM (#49653356)
Seems like you've never had to worry about accessibility in hybrid apps...
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:42PM (#49653296)
Hallelujah!

One other person in this place gets it: "fewer tokens, faster progress"

Electron, Tauri, React Native/Expo, Flutter (and countless others) are the wrong kind of abstractions, built for a time pre-AI, solving pre-AI problems

We need a new post-AI abstraction that embraces this opportunity!

That's why we're building SuperNative

Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:37PM (#49653265)
> you don't get native look-and-feel

You answered your own question

Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:28PM (#49653214)
We're only where we are in the world of computing because of abstraction layers

It's not the layers that are the problem; they're the point.

It's the quality of those layers. React is just a poor abstraction layer

Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:26PM (#49653205)
Working on this problem for the next version of NativePHP Desktop. Have dropped Electron entirely
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:23PM (#49653179)
Is more code the right goal?
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:19PM (#49653157)
We're doing it with PHP... we call it SuperNative (https://nativephp.com/blog/supernative)
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:14PM (#49653136)
What if you could have both great performance and UX for each platform AND a single codebase?
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:13PM (#49653130)
It's the cost of water processing and delivery, infra (plumbing) maintenance, chemical treatment...
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:10PM (#49653113)
I'm working to solve this...
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @11:03PM (#49653078)
Why would they need to worry about hiring for specific skills at all? As AI progresses, isn't the only skill that matters that you can drive it effectively (which encompasses testing and review) without needing oversight?
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @02:35PM (#49648347)
More code means more people. That's not peanuts
Re:Shopify moves back to Native from React Native on Thursday September 10, 2026 @01:30PM (#49647408)
As the builder of a post-AI, cross-platform native app building framework like React Native, I 100% believe this to be a backwards move.

I've written up a load of thoughts about that here[1], but in summary for the Shopify case, they're basically going to be spending a ton more than they have to by switching back to multiple apps and I'd predict another swing back to better cross-platform tooling in the coming years.

[1]: https://nativephp.com/blog/why-not-write-it-twice

Re:Rift: Better Alternative to Git Worktrees on Wednesday June 03, 2026 @10:09PM (#48392790)
CoW doesn't require reinstall of dependencies as they're part of the same directory tree, so should be immediately accessible (I've been using this way for a couple months now and it works fine)

The application running (port config) problem is an issue for frameworks and build tools to figure out around the shift towards multiple live working copies at once

The tools that facilitate this will win imo

I use Laravel Herd along with Polyscope (made by the same company). Together they enable CoW clones with their own dev domains - it's zero setup and works super well for my use-case

I can see a simpler version of the same thing being very neat dev experience across many stacks

Re: on Wednesday April 22, 2026 @05:57AM (#47861303)
This is a guest post from Saurav Pathak, CPO at Bagisto, the open-source Laravel eCommerce platform. Bagisto's mobile admin, NativeBagisto, is built with NativePHP and available on the Play Store.

This article has not been sponsored or paid for.

Fascinating! Thanks for sharing

Older »