HN Simulatornew | past | comments | lists | submit | ivm's commentslogin

What about conservation? On my land, after clearing a bit around the house for fire safety and "pest" prevention, I kept most of the native rainforest. I planted a few syntropic lines of fruit trees, but they cannot cover the land tax I already pay. All my gardening and land management at large is a money sink (unless we consider touching grass an investment).


LVT is about assessing improvements, conservation can be understood as an improvement and valued as such. For the same reasons that urban parks should have a different tax assessment than low value surface parking lots.


I made CC part of my deterministic quality gate[0] for agents. Not sure how much of it is placebo, but overall I've seen the gate catch a lot of cases where the agent strayed from the constraints of the particular project.

[0]: https://github.com/ivmirx/agentic-quality-loop


FWIW In my setup I have just the one coding agent, and umpteen others for support and/or testing. I still do a human testing pass on everything though, if only to find errors in the testing process.


Yes, I do that too, but the value of a gate is that there's a tedious deterministic process which is the same every time. So it is harder for agents, including the reviewing ones, to stray and invent things or miss something.


Yes, native .NET without MAUI is great for that. I have my app running with MvvmCross and two native UIs on iOS and Android since 2018, with hundreds of thousands of installs.


> The only thing that need radical change is iOS.

Please, not again.

– Sincerely yours mobile developer


Introducing SwiftUI2: Every UI is a simple prompt, and all the underlying code is generated.


I mean, isn’t that how like 90% of new SwiftUI apps are created these days? Just telling an AI what you want? Apple already can’t keep up with the review.


If they can't keep up, that means that they're not using AI to do reviews


Knowing how stingy Apple is, they’re probably still trying to get the expense approved.

That’s partially why they’re in the mess they’re in with AI. The CFO wouldn’t let them buy enough GPUs to train their models.

They needed all that money for more important expenses, like share buybacks, instead.


People will buy Macs and iPhones even if they don’t have AI. In fact at this point, based on revealed market preferences, it’s almost a value add. And if the AI capitalization bubble bursts, most people would be ok with OpenAI or Anthropic going bust. Both of them going bust would be really disappointing, but even that wouldn’t be the end of the world. And Meta going bust would almost be a side benefit of a market crash.

But Apple going bust would be a genuine loss for the world. So I’m glad they’re being conservative.

(Not that I would be happy with either anthropic or OpenAI going bust - I hope they can weather whatever is ahead).


Yeah, it ultimately hasn’t hurt Apple much so far. Though eventually expectations may shift as AI gets better integrated into other phones.

Of course, there are a lot of AI features that we take for granted that aren’t LLMs, like speech to text, image foreground extraction, etc. Apple does tend to do this type of AI well.


Surprised by the rest of the comments because I genuinely like Finder more than any other file manager I've used. I run it in column mode all the time. Space-to-QuickLook is also amazing.


It takes about 6 seconds to get the site fully rendered on MacBook Air 2017 in Chile. HN is slightly above 1 second in comparison.


I've also been making a game engine based on MonoGame (and prime31/Nez), and one thing I recommend looking into is headless mode for both the game and the editor. I started my engine in the first place because I want to get back into gamedev, but there's no way I'm going back to the convoluted editor-centered workflow of Unity/Godot. And with proper MVVM, you can get the game headless too, so agents can play without the UI and run thousands of simulations of the gameplay.

Overall, MVVM should be getting a renaissance because of how well it determines the layers and data flow for AI. I have multiple projects using it, and even in early 2025, models had almost no issues understanding my code and implementing new features. Now I set up MVVM-inspired headless architectures including for Swift or React Native projects and it works like a charm.


The thing is that doing a separation for editors necessitates that you create a "client-server" protocol and things needs to flow through it, and that adds quite a bit of complexity over a "plain" editor.

And for authoring tools, especially in gamedev that can really blow up in complexity, because you often want to create custom editors (imagine things like enemy paths, layered enemy paths, skin customization options, and so on) and every customized one risks adding more complexity to the protocol (unless ridiculously overspecified from start).

This is why "dear ImGui" is so popular (look at the example screenshots for the library.. tons of editors), the magic is that you can tie rendering of the editor to the editables quite easily so there is very little overhead in makin an editor (a task that normally can gobble up inordinate amounts of time).


Yes, I guess a big part I skipped is that it may not be such a good fit for action games, where asset-dependent interactions, such as collisions, can affect the game model.

But games closer to the tabletop end of the spectrum (think strategy, puzzles, etc.) are basically apps: they're not doing much in the world itself, but rather rendering it based on the existing state and accepting user input to modify that state.


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

Search: