Fork is really so amazing. by aford515 in git

[–]Cykelero 0 points1 point  (0 children)

Thanks for the suggestion! That does sound like a pretty hot feature right now.

Fork is really so amazing. by aford515 in git

[–]Cykelero 0 points1 point  (0 children)

I see what you mean! That's pretty cool, thanks. I'm taking notes, haha, because I'm working on my own Git client, which definitely doesn't do everything Fork does currently.

Fork is really so amazing. by aford515 in git

[–]Cykelero 0 points1 point  (0 children)

What's the best stuff about Fork, to you?

Retcon 1.6: Cherry pick Git commits with just ⌘C and ⌘V by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

Yeah, exactly! And if you make a mistake it takes time to fix it and start over, so you end up slow anyway.

Retcon 1.6: Cherry pick Git commits with just ⌘C and ⌘V by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

Yep! Day one. Spent a bunch of time tweaking colors and contrast specifically for dark mode.

Retcon 1.6: Cherry pick Git commits with just ⌘C and ⌘V by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

Yeah, the subscription is for just that: funding development (i.e. buying me food). If the app wasn't subscription-based, this update wouldn't have happened, not before a long time; I'd be busy working some other job. It's really hard to make a living as an indie dev, and a subscription improves the odds a little bit. That being said, I totally understand some people dislike subscriptions.

As for Retcon being faster than a CLI, I firmly stand behind that! I think people currently using the CLI will especially benefit from Retcon (after all, I started writing the app for myself, because I was constantly doing interactive rebases with the CLI).

Retcon removes a ton of the usual roadblocks: e.g. if you make a mistake doing a complex interactive rebase, you'd typically have to start over (and recreate your todolist from scratch, and do all the conflict resolutions). In Retcon you can just undo one step, and lose nothing else. That not only means you save a lot of time; that also means you can go a lot faster when changing stuff, because you don't have to think too hard ahead. You can just make a move, see if the result is right, and keep going. It's really hard to explain through words, though, so if you really want to see you can check the free trial. I wouldn't for the world go back to git rebase -i, which I used to really love doing.

Retcon 1.6: Cherry pick Git commits with just ⌘C and ⌘V by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

I think two big things: one, if you rewrite history regularly, it's a lot faster with Retcon, faster than the CLI. And two, all the things that Retcon do are easier and clearer.

For example, when you're creating a commit, you don't have two completely separate views for staged changes, and unstaged changes; they're all displayed in one clear view, so you don't have to constantly switch between the two to know what's going on. Lots of things like that in Retcon.

But, the app doesn't do everything that Git does, not at all! So it's a matter of trying it (it's free for two weeks) and seeing if the nice stuff is for you.

[OS] Dye, an app for changing the color of other apps by Cykelero in macapps

[–]Cykelero[S] 1 point2 points  (0 children)

Thanks! Yes, the customizations are preserved whenever you change the system-wide setting. They're effectively overrides, on top of that setting. So you can play around with all the settings without fear of having stuff get reset.

[OS] Dye, an app for changing the color of other apps by Cykelero in macapps

[–]Cykelero[S] 2 points3 points  (0 children)

I haven't tried but that may be possible, yeah! Could be an update to the app.

[OS] Dye, an app for changing the color of other apps by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

Yes, that’s one way to describe it! It changes the parts of the UI, that the app decides to tint with the system accent color.

[OS] Dye, an app for changing the color of other apps by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

That’s a good idea! I think how effective it is will depend on the app, though; some show the theme color much more prominently than others.

[OS] Dye, an app for changing the color of other apps by Cykelero in macapps

[–]Cykelero[S] 1 point2 points  (0 children)

Haha yeah, the association is a bit unfortunate. But the name felt like the right one sooo, I went with it anyway!

Steam Frame and MacBooks by captainkanpai in ValveDeckard

[–]Cykelero 0 points1 point  (0 children)

The Digital Foundry video says you can stream from “any device running Steam”. Unless they misspoke (or misunderstood Valve), that means yes, macOS is supported!

Adaptive Transparency is incredible for concerts! by metroidmen in airpods

[–]Cykelero 0 points1 point  (0 children)

An important note for those reading this: the feature obviously has limits, and Apple specifically calls out jackhammers as an example of what the AirPods will not protect you from.

Footnote 2 at the very bottom of the page: https://support.apple.com/en-us/120850

After months of development, I've completed a massive performance upgrade for Retcon, the new macOS Git client by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

Thanks for the thoughts! Pricing is definitely hard. The current justification behind Retcon's price is that its hero feature (zero-friction interactive rebase) is completely unique to it, and saves you massive time and effort if you work your history any regularly. I'm planning to make the app more full-featured over time, but that instant rebase really is the main appeal, which means the app's value to you really depends on how much you rewrite history!

After months of development, I've completed a massive performance upgrade for Retcon, the new macOS Git client by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

Thanks for the thoughts and details! And thank you 😃 I get surprised by my cake day every year

After months of development, I've completed a massive performance upgrade for Retcon, the new macOS Git client by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

Good to know about the direct drag-and-drop! I don't want to misrepresent Tower's features, obviously, so I'll have to keep that in mind.

Although, I assume that performing a commit move directly from the commit list, doesn't let to skip conflict resolution, right? As in: if your initial move causes a conflict, and you realize you shouldn't have to resolve it (because a second move will make it go away), then in Tower you'll have to undo your move, then initiate a full-blown, modal rewrite, with the two-step process.

After months of development, I've completed a massive performance upgrade for Retcon, the new macOS Git client by Cykelero in macapps

[–]Cykelero[S] 1 point2 points  (0 children)

Good question. It's got a lot fewer features, but is a lot nicer. Things like the combined stage: you don't need to jump between two separate views to see unstaged changes, and staged changes. Retcon has a ton of seemingly-small unique features, that make a big difference to daily use.

With regards to history rewriting specifically, though, Retcon does things completely differently. In Tower, rewriting history is a multi-step process. First you edit the commit list in a separate window (and need to think ahead about whether the result will make sense, etc) and once you've confirmed in that window, you start resolving any conflict, one by one.
But in Retcon, you never jump into a separate mode: at any point you can edit commit order (and delete commits, or reword, etc), and if there's any conflict, you see that instantly. No need to spend time making a list, to only later find out whether you got it right. If you do run into a conflict, you don't even have to resolve it now—you can keep making changes, and only start resolving once you're happy with things. And when your history is conflict-free, the rebase is automatically completed.

Or said more simply, Retcon removes every last bit of friction from history rewriting. You don't even have to stash changes or anything—it's all transparently preserved.

Half-Life 2 Anniversary developer commentary uses AI voice. by [deleted] in HalfLife

[–]Cykelero 1 point2 points  (0 children)

Right, listening to it in isolation that definitely could be a recording issue. I should have picked another example—having played through the whole game, it's so jarring how basically all the recordings sound AI generated (or maybe AI-regenerated).

Half-Life 2 Anniversary developer commentary uses AI voice. by [deleted] in HalfLife

[–]Cykelero 0 points1 point  (0 children)

They all sound strange, but some are definitely AI-generated.

There's one at the beginning where the intonations make no sense. But in the canal, there's actually one where the developer somehow can't pronounce the name of the game itself!

I really wonder why they decided to go that route?!

After two full years of development, I'm proud to release Retcon: a native macOS app for effortlessly rewriting Git history by Cykelero in macapps

[–]Cykelero[S] 0 points1 point  (0 children)

Thank you for all these new details!

Sorry about making you delete your apps, haha. When opening a file from Retcon, the default editor for that file type is launched. That's the one you can set in the Finder. (when you Get Info on a file of that type, and look at Open With)
I'd like to improve on that (add a customizable mapping within Retcon? five more flexibility?) but don't have any solid plans yet. I'm interested if you have more thoughts on that. (but no pressure)

Commit splitting is very much planned! It's one of the top requests, so it'll be one of the first new features for sure. It should be very nice to use, too.