Hacker Newsnew | past | comments | ask | show | jobs | submit | pzo's commentslogin

Wish they explained more. Even though I'm mostly native iOS its seems react native is better stack for AI and iteration (hot refresh etc) - the main reason pretty much all AI vibecoding app were implemented via expo/react native.

I also believed that finally this year react native got mature enough with improved tooling and performance to the point that it started to being 'boring' technology.


There's a section linking to a more in depth article:

"The Shop app, which is regularly at the top of the list in the shopping category in the app stores, is the first to be migrated. Assisted by AI, the team was able to go from a proof of concept to a fully rebuilt native app published in the app stores in just 12 weeks. We’ve written about this migration in depth here [0].

The migration of the Shopify app (our biggest with 300+ screens, home & lockscreen widgets, Apple Watch app, complications, Siri Shortcuts, etc.), is also underway and will ship later this year. The rest of our apps will be migrated soon."

[0] Migrating Shop app from React Native to native https://shopify.engineering/shop-app-migration


There is a reason that South East Asia is popular for digital nomads and for retired expats. Thailand and Vietnam have still very affordable places if you avoid tourist traps. I would recommend first trying some easier destination like chiang mai or danang (if first time in asia), staying for 2 months (vacation/workation) and seeing if you still like it.

yeah some people are very orthodox and think having a partner, kids, pets, mortgage is a must. The easiest exceptions is being a monk or priest and they are fine and society accept it.

How then about monks or priests? I wouldn't clasify them as all of them being sad or having a fundamental need to be loved. Also loved can have different meaning - mostly people think about family and partners. There is also community.

probably less - I sometimes manage to burn like most of my 5h credits on Claude 5x Max plan in 2h.

The annoying things is that you gave bigger tasks and is such session finished maybe 70% and after 5h pool resets cache will expire so that if you "please continue" it will wipe out again a lot of your 5h pool)


This is a significant list but unfortunately not load-bearing enough.


The decision of which words to remove is genuinely yours.


a fork worth flagging


A game of Linguistic Jenga.


This baselines to a clear set


It is sufficient not at all


This simplify integrations. Right now you have to maintain your own billing credits for user and even maintain user database, abuse detection, planning when you have to top up your openrouter accounts etc. Lots of hassle and this is a reason why many developers charge e.g. more in subscriptions the end user.

It's more user and developer friendly when you tell your user:

- you don't have to create new account just log in to your openrouter account

- bring your own key

- you don't have to pay any subscription. we charge small markup fee (e.g. 5-10%) over your usage inside our app.


All of that plus all the privacy and user data stuff that as an app developer I may chose not to deal with.

"I am not touching your data, you are using OpenRouter and whatever provider, I am getting a small cut from your usage."

Not sure why this does not exist yet.


> Set your model and effort level before you start. Changing either one mid-conversation can bust your prompt cache, which can increase token cost.

I know we supposed to do this but is there any particular reason why such things cannot be supported? I thought its running on same model just different settings like reasoning. This would be super useful.


Wouldn’t that invalidate kv cache and you wouldn’t benefit from much cheaper cache read?


I'm frequently idle for five minutes while I review, at which point the cache has expired


I doubt they will match old cache read pricing- that’s most important in agentic coding.


CXL might save us. All the world's old DDR4 to the rescue. Either per box, where the job has to route back, or network attached, where there's now a pool of absurdly fast temp storage.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: