Hi there, I don't publish binaries publicly but they exist and they are digitally signed under my company's name.
It's not like you are describing it, it's more like:
You can build this yourself, trivially.
If you like what you see and want more, without the hassle, put some spare change in the Sponsor thinghy and just have it self-update.
Oh and if you are generous, you can actually get more than a terminal app...
(read my reply to the message above for more context)
I'll take this as a compliment. I don't know, I had sponsor even before I was actually ready to show it to people.
I guess I felt like I had to pay back the folks that believed in me and I will keep doing so to the best of my ability.
I still cannot afford CI so I wouln't use the word "hype" :)
It's all local in my homelab and sometimes I need to cut corners and I hate it but I will make it work.
I already started sharding builds and tests horizontally, I am getting a box for running fuzzy tests continuously, I forked Zig to have incremental builds and centralized content addressed caching.
It's a lot of work that unfortunately didn't go on the project itself but the benefits should become more and more apparent as time goes by and I plug things in.
One release/day is my goal but I am still far from that :(
Speaking of hype, did you check RAM prices lately? I can't take it anymore. I got kids to feed!
Hi there, I am the guy building Wintty.
Thank you very much for the mention and yes, I can confirm that it is trivially buildable from source. I have about a dozen of forks and it is mostly people setting up their CI to build it.
The sponsorship gating is for the convenience of having a signed installer that self-updates. Any amount would do ($1 is the minimum, most people donate $5).
Those that pay a bit more have also access to the Pro version, the Pro Legacy (for older devices and VMs that do not have DX12), ARM builds.
THe Pro version makes it a multiplexer with agent sessions restoring after reboot, it has full OS7501 support, narration, streamer mode, IME support, Windows integration, soon it will ship linux and mac servers that will allow remote control and there's a ton more feature coming. It is still quite unstable because it's just me building it and I have been investing time and money in the project. But my ambition is to really make it one of the best developer's/agents driver's/knowledge worker experiences on Windows.
I am already honoured and thankful to have about 60 paying sponsors and also the interest of a couple of companies as we speak but in all honesty, I don't get much feedback, just a handful is on my Discord and I literally built (released two days ago) an MSN-like mini-app inside Wintty to get feedback of any kind from my users. For privacy reasons I do not have any emails or ways to reach out so I had to be creative :)
This obviously took time away from stabilizing the app and it costed me a couple of sponsors... :(
Winning them back is the goal now XD
Anyway, anyone else that wants to join me in this journey is more than welcome to do so, I can only promise that quality will improve over time and that I will do my best to make it nicer to build on Windows.
Needless to say, none of this would have been possible without Ghostty, Mitchell and team. My initial aspiration was to merge most of it back to Ghostty but things change fast nowadays and we all need to adapt. :)
Thanks Jeremy, first star appreciated! On your question: my line so far has been that anything a client can't distinguish in a test suite belongs in the mock (state machines, pagination, signature schemes), but the semantics stay provider-native.
A Stripe refund and an Adyen reversal aren't the same object, and abstracting them is how payment integrations get burned IMHO.
The one place I'd promote to a shared contract is cross-cutting shape: cursor pagination, idempotency keys, webhook signature verification, retry-after semantics.
Vyral's evidence-qualified adapters sound like the other half of that — offline simulation vs live qualification if I am getting it right.
If I were you I'd add a demo or something to Vyral's README, make it shorter, like progressive disclosure with all the nice details on the website (link it so agents can find it). Show the money shot, if that makes sense.
I am going to look into Vyral in more depth because I am intrigued. I'll reach out if anything comes to my mind.
If you have any ideas about how a collaboration could look like, feel free to hit me up! I mean, we are already collaborating in a way :)
It's not like you are describing it, it's more like: You can build this yourself, trivially. If you like what you see and want more, without the hassle, put some spare change in the Sponsor thinghy and just have it self-update. Oh and if you are generous, you can actually get more than a terminal app...
(read my reply to the message above for more context)
reply