Live data from Hacker News

Shopify is moving from React Native back to Swift and Kotlin

shopify.engineering

991–1000 of 1001 posts

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

#991

Earlier quoted context omitted.

Shopify works well for me but it used to push nonsense like podcasts or audio books that I had no interest in, with no way for me to hide them. I just want to listen to music. Upon looking just now, seems like they have been relegated to their own tabs now, which is great.

I can’t tell if we’re trolling at this point with the mixing up of Shopify and Spotify

I thought we were talking about Sportifei - the new outdoors retailer ?

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

#992
post #916

Earlier quoted context omitted.

I don't need an audit log for my audio. What I do need however is to remove something so it doesn't influence the algorithm. I may not remember every time I play music for a kid to turn on the right mode.

That would also then require them to invalidate caches and rerun scripts to rebuild those lists and recommendations, which costs extra compute.

Invalidate the recommendation cache

You mean like, when a new song is added to the list???

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

#993

Earlier quoted context omitted.

When Chrome 1.0 came out in 2008, it only ran on Windows, and it couldn't do basic things like print or export to PDF, didn't have any accessibility, didn't work in RTL languages, and didn't have any graphics acceleration, among other limitations. Don't get me wrong, it was a marvelous piece of engineering - but it was extremely incomplete. By the time it was what we think of as a modern, complete browser, they had m…

I agree with what you're saying that it's not exactly what we're seeing which makes it not as simple. However, I've seen this play out in many a big companies where there's a big mess going on. Answer is always similar pointing to -> "clearly it's not simple" and that's kind of the whole point. They made it not simple. 3k ENGINEERS, my sweet dude. THREE THOUSAND. By any and all account that's half as much as current…

Very much this. If you have 3000 engineers (and all the associated non-engineering roles that inevitably come with that) then you have guaranteed that no problem will ever be easy to solve. Possibly you might be able to solve some extremely difficult problems that you couldn’t solve with fewer engineers.

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

#994
post #980

Earlier quoted context omitted.

I think there is something like Parkinson's Law: "Work expands so as to fill the time available for its completion." This is more like the engineering team scales to match your budget. It is why successful companies, when starting out and getting to their defining project completion state have significantly less engineers then 10 years later when they are massively more successful. The cost of having the engineers is…

Twitter is an empty shell though. Yes it technically works, that’s about that.

I certainly wouldn’t go anywhere near Twitter these days, but the question is how much of that is to do with engineering failures and how much is to do with the overall change of culture and moderation practices that Musk has introduced.

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

#995

I agree w/ advising people to move off React Native, though I think the story that "LLM enabled an otherwise too-expensive migration to consider" is not correct. I say this because I was part of a migration from a mid-size React Native app to a Swift/Kotlin native app redo. I did the majority of the technical work on it. The majority of the work occurred before January 2026 and without LLM code assistance, though lat…

  >  cause your business to really spend a lot of time shepherding the tech over the finish line
some may be better than others, but isnt this basically true for all these 'multiplatform' systems? i have nightmares of all the time it took with handling platform-boundaries/integration and lots of other grinding...

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

#996
post #956

Earlier quoted context omitted.

I agree with you. I don't think LLMs magically solve the problem that comes with writing twice. Even if they were to write for two platforms, they'd likely want to have a whole bunch of business & state management logic that would be shared between the two with the native part being a thin platform layer. It seems like a mostly shared codebase (reglardless of specific tech choice) would let them get precisely the end…

Besides API features, it won't require downloading 0.5 GB of web browser in order to run. Sure, you can make it smaller, but how many companies actually do this? Sure, you can make it faster, but how many companies actually do this? Accountants and product managers don't care about speed or size -- that's a user problem. Judging by the app sizes I download (and try to avoid), few companies really care about the user…

I'm on your side regarding this sentiment.

I happen to work on a product that is built for accountants. You would not believe how slow these apps are and all they do is display forms!

I believe customers do care about performance even in these B2B industries.

But it feels like they sink into some form of learned helplessness. We were interviewing our customers to learn how to build a better PDF viewer for them. Their biggest complaint had about Adobe Acrobat? Too slow!

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

#997

Earlier quoted context omitted.

> We live in a time now where libraries are free and plentiful and pretty good. Specifically what are you talking about here? Chrome is c++ I thought?

Chrome was invented in 2008. Abseil[1] didn't exist publicly until 2017, derived partly from Chromium. HarfBuzz wasn't ported to C++ until 2010. I don't know the entire constellation of libs Chrome would use if it was designed in C++ today, but I bet a lot of them didn't exist before Chrome or were even created partly as a downstream byproduct of Chromium. In other ecosystems: if Chrome were designed in Rust in 2008,…

I think you've come from an npm world because c++ still doesn't have a great library ecosystem if thats what you mean.

> In other ecosystems: if Chrome were designed in Rust in 2008, there would be no crates.io to pull from. There would be no NPM, since Node followed V8/Chrome's invention in 2009. Maven Central had ~50K packages in 2009[2], which was a lot back then. In 2026, Maven Central hosts over 3 million.

Yeah, this is all web development stuff.... Doesn't apply to c++

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

#998

Earlier quoted context omitted.

> Spotify or Shopify Both. The post is about Shopify, but some of the comments expanded the conversation to include Spotify as well. > In a sane society, Shopify’s opinion on anything engineering related would be thrown into rubbish [...]. > This is unfortunately not an isolated case, Spotify for one has the same issue, [...]

fwiw the post mentioned Shopify and Spotify, hence why you see discussion of both

[dead]

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

#1000
post #783

Earlier quoted context omitted.

This is wildly overblown. I've been working with agents for a good while, read tens of thousands of generated Python and the language factor is actually the part they get right that humans don't.

Do you know Python? What do you think has more training data Python or Kotlin?

20+ years of using Python. I don't really think that lack of training data for Kotlin is a problem.
Post reply on HN