atonse

I feel pretty good about the 27 series in a way I haven't in the past (I've been running iOS 27 and it's working well), except for one thing, they remove x86 support (no more Rosetta), so just keep that in mind in case that might disrupt anything for you.

I actually think this is what they ended up doing - just regular conversations with tool calling into your various apps, behind a Siri AI API. not HTTP based mcps (for now) but rather local ones.

Yeah that's totally fair. So am I, which is why I'm making sure we're still manually testing the hell out of it before we release it.

But our product now has a way more extensive test suite than it ever did, again, thanks to the agents writing pretty damn good tests.

How do you propose getting "rid" of "Vibe coders" (which I'm assuming you're pooling me into?)

I think probably GPT 5.5, or 5.6 Sol - it was ~ 2 months ago.

Each time I get access to a new model, I do two things on all our active codebases:

- Security review of all the code and vulnerabilities (new models will find new stuff)

- Code review of test suite quality, and idiomatic patterns/code for the language of that codebase.

And in the case of swift and kotlin, it's even more important that an agent helps me with the code quality since I don't know what "idiomatic" swift or kotlin looks like, the way I do with JS, Elixir, C#, Ruby, etc.

Others on our team use Android phones. So when I said that we spent the next few days actually polishing it, that's where others came in, providing feedback when they used it.

I could only sweat the details on liquid glass, etc because I'm a daily iOS user.

I used the emulator - but just like I can use an iOS app for 30 seconds and tell you whether it feels native or not, I can't do the same for Android, since I'm not a daily user of Android phones.

And in the past, I didn't care because when I was manually building the app, I would just do my best with react native. But now that I can actually sweat the details (with the help of agents), I do want to hear from android users and use as many OS-native APIs and features.

I answered elsewhere that I don’t personally use Android phones but we have people on our team that do. Which is why I don’t want to personally claim that it feels native.

But yes we are having real Android users test it.

So it’s quite the contrary. I care MORE what real users say. I can only guarantee that the app does things when I tap. So I’m not trusting the agent on UX, only on functionality. But whether it feels native, I am relying on those users in our team.

Maybe. Android might still be a mess, fair point.

I wrote every single line of the react native app we ported, and maintained it for 9 years. So suffice to say, I'm familiar with the code.

But I am going to always prioritize the user experience over a developer (like myself)'s need for satisfaction to see code. And a pure native app is _always_ going to behave better than react native.

This gives me a chance to do that.

What's more likely (as others have said) is that the other thousand companies that can't afford to have dedicated staff would've just used React Native. So no jobs were lost, they weren't there in the first place. The places that have dedicated Swift/Java devs can now be more ambitious in what they build.

We have people on the team that are android users. I just meant that I don't want to evaluate whether it feels "native" as I personally am not an Android user.

We did the same thing - had 90% of it overnight. Then spent a few days in the background tweaking for polish.

Our app is smaller, and has about 15-20 screens. I started at about 12:30am by giving codex a goal and it inventoried every screen based on the react native code, then created android and iOS directories, used maestro (I had already set up this tooling for a previous personal app build a few weeks prior), and had the whole thing working in android and iOS in the morning. Took it about 6 hours while I slept.

The app is way smaller, launches instantly, and the android app is (supposedly) native looking. I say supposedly because I don't use android phones. But it's using Jetpack Compose and Kotlin.

And I don't know Swift or Kotlin. I honestly don't see the point of React Native anymore. I know Expo is doing very cool agentic stuff, but I'm just not sure why I'd need any of it when I can write a native app.

But realistically - most things are standardized. Nominal sizes. 2x4's, a sheet of plywood or drywall is 4x8 feet, etc.

(In fact, the metric equivalents of construction units are all based on feet/inches converted to a round mm because construction sizes are much older than metric)

So yes maybe you're messing with lengths, etc. 100% true. But unless you're doing fine carpentry, it doesn't matter.

The other thing is that it's a system that divides by 2 multiple times - it's not totally random. But metric only divides by 10 and 5 cleanly. You can't do a "quarter" of anything. Which is fine... but I'm saying that both systems have their advantages and disadvantages.

Also the 0 and 100 is at sea level.

If you actually measure a boiling pot (assuming you aren't at the beach), it will likely not be exactly 100 degrees, but less (or more, haven't had my coffee so I can't calculate).

So for most day to day stuff, it's equally arbitrary. And pretty much _nobody_ needs a thermometer to tell if something's boiling, you wait for a rolling boil. Or frozen, you wait until it looks like ice.

So again, great on paper, but in day to day use, not necessarily more useful than F.

I put more details here: https://news.ycombinator.com/item?id=49635310

I do concede the overwhelming majority of people that argue that one is better than the other (both ways) are basically just arguing "the thing I grew up with is better" - because when you probe further, there isn't really any supporting argument, just "I understand this system better because I grew up with it" but it's equally vacuous coming from people who grew up with Celsius.

I came to the US when I was 12, so I grew up with Celsius but didn't pay attention to the weather as a young child. But still, I've lived in both systems.

Celsius in a lab (or in cooking) is perfectly fine.

But as a way to describe daily weather (and thermostats) it's woefully inadequate.

The sum total of "comfortable" temperatures in celsius has to be squeezed between maybe 17 to 24 - why? you never ever use anything above 40 except when talking about people that died from a heatwave.

It's based on the freezing and boiling point of water _at sea level_ which almost none of us ever encounter (whether it's sea level, or the boiling point of water).

Fahrenheit is a much more intuitive scale (again... to describe daily weather or human temperature) - 0 - 100 better models the temperatures we experience daily, and you can intuitively separate into 10s, the way you "feel"

For example...

100s - honey, please, let's move to a cooler place.

90s - uncomfortably hot

80s - hot in the sun, not too bad at night

70s - you'd probably want a light sweater at night

60s - light sweater all the time

50s - medium sweater

40s - sweater, maybe a coat

30s - coat

20s - sweater and coat

10s - why am i living in this region?

0s - honey, please, let's move to a warmer place.

The point is that there's enough resolution to describe the actual human experience with temperature.

For everything else, celsius is perfectly adequate, totally agree.

I often make the argument about whether metric is "better" being split by "is it better on paper" vs "is it better in day to day life" - and most metric stuff breaks down in the latter, meaning, the non metric systems seem to be perfectly fine in day to day life, but almost always better on paper.

Like Celsius - sounds great on paper, not any better (and in some ways, worse) in day to day weather/temperature.

One of the few exceptions I find is metric paper sizes. It's such a beautiful way of designing the sizes that is not only perfect on paper (pun proudly intended), is also totally practical in real life.

It's there via omission. Others have said in these threads that the concept of an HVAC company or others investing in a particular manufacturer, does cost them money, and that can change over time. It's not unique to Tesla, but the writing, by way of omitting this.

"That is the bind Tesla’s certified installers are in: dependent on a brand that just walked away from a product line they built a business around, while still needing to sell its remaining hardware."

there is _nothing_ unique about that situation. That could happen with any company.

It's the cost of doing business. training your workforce, etc. Clearly these companies are happy to sell other Tesla products to the point where they don't want to jeopardize those relationships.

No, I didn't mean ai-resistant as far as "don't need coding agents" - I use agents to do all my coding now. I'm saying, AI-resistant in the sense that a company like Shopify isn't going anywhere even in the AI world. If anything, they will thrive with more AI-assisted shops coming online.

That gives the Tailwind folks a more steady stream of income.

I don't agree with "nor should it be" - the market decided it was clearly needed. And this isn't unique to Tailwind. For decades, companies in many ecosystems (like .NET, JS, etc) have made lots of money selling component libraries that save developers and companies a lot of time. And I even bought UI.sh in April, and it really was great until the models just natively got much better.

I happily paid for Tailwind UI because it was worth it. I paid for ui.sh and got plenty of my $130 (or whatever) value. The market spoke in a good way initially, and now it's sending a different message.

They've just got to do the next thing, which is find an AI-resistant steward of the project now.

Unless this ban actually resembles something like global nuclear non-proliferation treaties, it would make absolutely no sense for us to cripple ourselves when someone like China continues full speed ahead.

I don't know what the solution is, but what I do know is almost nothing good will come out of _just_ the US pausing.

That may be true, but I feel that is a separate conversation (whether Elon Musk and his companies, taken whole, have had net good or net bad contributions to the world) from Lambert's coverage, which seems to pick any single _event_ and select the most heinous, corrupt, version full of malicious intent when often unwarranted, extremely bad faith and never adds informational value to that larger debate.

I've never seen a person have such a frothing-at-the-mouth hate for any company as Fred Lambert at Elektrek has for Musk/Tesla.

Just filter for his posts, it's kind of crazy. After a few posts I started noticing a while back. Lambert writes like Elon Musk killed his puppies with his bare hands.

It causes Lambert to have nearly zero credibility in anything he writes about Tesla. It doesn't come from a place of good faith reporting.

yeah i'm wondering the same way... especially in light of the 20x debacle (where we found that 20x of Max vs 5x only applies to the 5hr limit, not the weekly limit, whereas OpenAI's 20x actually is 20x overall).

Also Opus 5 has been really tough to work with. I can't understand half of what it says, it's just so damn obscure.

Not sure what’s there to apologize about. Canada can still call it Lake Ontario right? Or I wonder if it matters whether it’s on American soil or not whether international bodies recognize it?

I’ve concluded that if you already use a coding agent then openclaw adds very little (at least the multiple rounds I’ve tried it since mid Jan), it mainly brought the power of do-everything coding agents to your phone, available everywhere. But you exchange a low quality messaging interface for that ease of access.

Just to be clear, I’m not advocating that people that benefit from openclaw move to coding agents. This isn’t a “dropbox is just SFTP” comment, more that if you are already using coding agents, it feels like they do most of what I saw from openclaw at least a few months ago.

Am I missing something? Would love to be proven wrong.

Honestly the most impressive thing to me was the first video where the guy switches between four languages.... I was like "is he AI?" - very impressive, sir!

After watching a video about how the filesystems are > 2x faster (and testing this myself in my mac mini vs a linux machine), I feel like Apple is leaving a lot on the table, and I hope that they get APFS to be as fast as the linux filesystems.

Because otherwise a lot of this hardware (including their blazing fast SSDs) is wasted. Cuz my M1 mac mini is awesome otherwise.

Bun has been doing release videos for years. There's no drama here to create.