jcollins
Joined 17 years ago
Joined 17 years ago
One downside for sure is lack of deep knowledge on all these platforms can make it difficult to see issues.
I'm trying it now with an app and so far it's working really well. I build what I can cross platform, the non-ui stuff, then have AI build the UI for each platform.
It even implemented native low-level graphics on each platform: metal, vulkan, and d3d12. It builds SwiftUI on Apple platforms, WinUI3 on Windows, GTK4 on Linux, Compose on Android. The cross platform stuff is Zig with a C ABI.
And yeah, it's a bit terrifying how fast you can iterate. I've built for all these platforms in about a month. It would have taken at least a year, maybe more before. I haven't even optimized the process by having AI agents follow my lead automatically, so as I finish features on the primary platform they could start building the others by watching. Requires some setup I haven't tackled yet (VMs for all platforms with agents waiting).
I imagine memory consumption is on par with running on Intel. I don't think Docker Desktop can really change that.
Gyro, a command-line cloud automation and management tool, started as internal tool over 5 years ago. We had a vision of building one tool that would pull together several different tools (Chef, Service Discovery, Authentication, Deployments, etc) into a single interface that would greatly simplify the day to day management of our systems. This goal was very successful in transitioning to a DevOps model. Our developers are able to make configuration changes, do their own deployments, and build there own test environments without help from the operations team. And most importantly they've embraced this model because it gave them the power to make changes without waiting for an operations team and in turn it helped the operations team by reducing their work.
We decided to clean up the code and open source it. The result is Gyro (getgyro.io).
What makes this different than what exists?
- Designed with logic (for loops, if conditions, etc) from the beginning (https://gyro.dev/guides/language/control-structures.html)
- Workflows provide the ability to stage complex changes and rollback (https://gyro.dev/guides/workflows/)
- Extensions allow for tight integrations with other operations tooling (https://gyro.dev/extending/)
For some screenshots of Gyro see (https://getgyro.io/introducing-gyro), source is available one Github (https://github.com/perfectsense/gyro)
We're really excited to open source Gyro and see how people extend it!