Live data from Hacker News

Shopify is moving from React Native back to Swift and Kotlin

shopify.engineering

801–810 of 963 posts

Re: Shopify is moving from React Native back to Swift and Kotlin

#801
post #636

Earlier quoted context omitted.

They don’t confuse them, he says both have the same issue. Perhaps you are the AI slop?

Seriously, it’s funny how confident people can be about something despite their awful reading comprehension.

Aight, I recognize I only skimmed through the comments, I was completely convinced it was a typo because it has to be a big coincidence that in a post about Shopify suddenly they talk about Spotify and it's not by mistake.

Re: Shopify is moving from React Native back to Swift and Kotlin

#802
post #45

Earlier quoted context omitted.

And people say AI isn't taking SWE jobs...

It ported overnight. I don't think it would create from scratch without a lot of hand holding.

This does seem like the kind of task LLM's are ideal for. Just like that port of Bun from one language to another.

Re: Shopify is moving from React Native back to Swift and Kotlin

#803

Earlier quoted context omitted.

In the corporate software world, especially anything to do with the web both front and back, most people really don’t know what they are doing. The goal is hiring/firing and agile. Compare that to companies that release actual software products. The goal is product release at high enough quality. There are real performance and security targets to achieve. Your typical corporate developer, on the other hand, does not…

What's an "actual software product" and why don't you think web products count as them? I'm a full stack web developer. I've worked for startups and F500 companies. There is always a push for release targets. The less technical the leadership, the stricter the release targets (its hard to sell a critical refactoring to management when they cant sell a shiny new feature or kpi to their own boss). We've kept our teams…

I worked at Expedia for a bit. Ask yourself if they are a tech company, software company, or travel company. It’s not a trick question. They have a shit ton of software developers that work there. Same with Bank of America where I also worked. In fact BoA has more software developers as employees than almost any other company.

Compare those to a company whose only product is software or is primarily a software service.

The difference is directness to the goal. If you are a big bank you need software and web services just like everyone else, but if you get it wrong it’s not going to bankrupt you. You can always hire an outside consultancy to fix it knowing your employees suck at what they do. If all your business does is sell a retail software product and it turns out to be slow broken shit then you have nothing. That’s the difference and layoffs aren’t a bandaid.

At places like Expedia and BoA you can absolutely suck at what you do. Sucking is actually the expectation because 20% of the people solve 80% of the problems, nobody provides substantive training, and everyone is easily replaceable. If you are the guy building innovative solutions on an original software product for a company that only sells software as a retail product you are still ultimately replaceable, but not immediately so.

One key identifier if the business intends to hire sucky people for a sucky job is degree of abstraction. Is the given job about solving a real problem directly, for example using JavaScript to create a new transmission system that achieves higher availability and lowers costs. Or, is it a tech stack nightmare pretending to not write JavaScript to do the same boring shit everyone is doing in a half ass way?

Re: Shopify is moving from React Native back to Swift and Kotlin

#804

Earlier quoted context omitted.

Are you saying you don’t trust ZDR claims from inference providers? They don’t care about your code. There’s more and better data on the public web.

Isn't ZDR only the case if you "opt out" through a setting? Lots of opportunities to make a mistake here, or for the LLM provider to play games. You could be unaware of the setting. The provider could reset the setting upon subscription lapse/renewal, application update, model release, etc. A developer could accidentally use their personal subscription (w/ setting on) on a work codebase. Also what's the timing on thi…

You should educate yourself about AWS Bedrock and Azure Foundry.

Re: Shopify is moving from React Native back to Swift and Kotlin

#805

Earlier quoted context omitted.

Plus they have an Amazon-scale infrastructure to manage...

I think Amazon is very much on another level in terms of scale. Not trying to be negative about Shopify — they have a very large system to maintain - but Amazon is just on another level.

Shopify is not far behind Amazon (the e-com business). It's network sees as many unique visitors as Amazon, though I imagine Amazon has more sessions per visitor, but the GMV across Shopify is just shy of half of Amazon. It's still in the same ball park.

Re: Shopify is moving from React Native back to Swift and Kotlin

#806
post #351

So, instead of paying humans twice for the same thing, Shopify will pay corporations to burn the planet a little bit more, waste water and energy - to build the same thing twice. Just because. There's no tech reason to do it. "LLMS are better now". There's no low level optimisations, no blockers, no app shortcomings, it's a shopping app for Christ sake. Instead of optimising, creating more with less, they will create…

Can someone explain the waste water thing to me, because unless they’re separating it into H2 and O2 how is it possible for water to be wasted?

evaporating it so it's relocated somewhere else. Damn clouds

Re: Shopify is moving from React Native back to Swift and Kotlin

#807

Earlier quoted context omitted.

Plus they have an Amazon-scale infrastructure to manage...

I think Amazon is very much on another level in terms of scale. Not trying to be negative about Shopify — they have a very large system to maintain - but Amazon is just on another level.

Amazon don't seem release any figures but I've seen estimates of 50,000 to 100,000 engineers. They do have 1.576 million employees worldwide (2025 figure).

Re: Shopify is moving from React Native back to Swift and Kotlin

#808

Numbers from GPT Astra - Shopify has 3000 engineers as of 2026 - Google Chrome when released in 2008 conservatively had ~ 60 engineers. - GTA 5 in its credits had 150 software engineers. Surprising even to me who has had many an experience of being in a bloated FAANG team, this 150 includes GTA Online! In a sane society, Shopify’s opinion on anything engineering related would be thrown into rubbish because they seem…

Shopify is handling customer payments worldwide, 90% of their work is probably localization issues rather than customer-facing feature development.

GTA V developers don't give a fuck whether the game is running on a computer in North Korea or in Sweden.

Extremely ignorant comment.

Re: Shopify is moving from React Native back to Swift and Kotlin

#809
post #737

Earlier quoted context omitted.

People who has not run software at scale have no idea what it takes to run it at scale. Google chrome is 60 engineers at launch but google same company has more than 100k engineers. Building first version was always easy and only gotten easy, scaling software was always hard and it is still hard. PS - Spotify i can't defend the product sucks.

I am quite curious about what people hat so much about Spotify. I made some excursions the last few years to competitors like Tidal and Apple Music but I just found myself coming back because the Spotify mobile app experience (and desktop) was just plain better. I wonder what gripes people have.

The article is about Shopify, not Spotify.

Re: Shopify is moving from React Native back to Swift and Kotlin

#810
post #571

It seems like Shopify has fallen into a trap thinking that more complexity costs nothing because of AI. In the age of AI we have to embrace the same principle as before that complexity needs to be tamed, not multiplied. Even as humans struggled with complexity, from what I see now AI struggles very much the same. Hence I don't think this will age well.

Always relevant - https://grugbrain.dev/

That was great! But here is one place, at least, that needs to be updated for the AI era:

> working demo especially good trick: force big brain make something to actually work to talk about and code to look at that do thing, will help big brain see reality on ground more quickly

One of the best things about AI is that you can have a working prototype almost instantly, which is great for iterating quickly over ideas. But it means this trick simply doesn’t work anymore.

Post reply on HN