I'm neither a Mac uset nor is our team exploring a Rust rewrite ... however I appreciate this post. This is what I hope for from "Show HN", a just long enough summary of technical tradeoffs required to solve a real-world problem for a relatable small business (admittedly that part is an assumption). Thank you for sharing your experience.

Happy to share the experience. It was something we debated for a long time. Rebuilding something that is already kind've working is daunting, but in this case we are happy with the results.

The level of your effort really shows through. If you had to ballpark guess, how much time do you think you put in? and I realize keyboard time vs kicking around in your head time are quite different

Thank you! I started this back in October, but of course have worked on plenty of other things in the meantime. But this was easily 200+ hours of work spread out over that time.

If this helps as context, the git diff for merging this into our website was: +5,820 −1

Make sure you're on the latest BIOS as many improvements have been made since early AM5.

Anecdata: I just bought a used AM5 mobo and threw in this memory kit CMK64GX5M2B6400C32; hitting 6400 was as simple as turning on XMP and that's it.

Which legal jurisdictions are you familiar with? Serbian? European? US?

Thanks everyone for the advice.

No one has chimed in about some "magic words/phrasing" I need to use.

Like I mentioned, it seems like the rep will escalate it to another refund department if I say something in a particular way.

Providing user UI flexibility is never a "problem".

Obviously there is a tradeoff - there is always a tradeoff in software.

Having just gone through a re-design, our team's tradeoff was how much time to spend tweaking media-queries/screen-size responsivity for the countless permutations of device-resolutions & dpis vs just picking a handful of density-levels.

launch Windows Terminal -> winget install voidtools.Everything

if you're on windows and haven't discovered the newest Terminal experience nor winget, you're welcome

This is finally the Windows experience that developers wanted. I thought that OneGet (PackageManagement) was going to be the way almost a decade ago, but that fizzled out. The guy that wrote that one seems to be totally on board with this though: https://github.com/microsoft/winget-cli/discussions/186.

I think that the guy that wrote OneGet had it mostly right, but it seems (as a layman who knows nothing about Microsoft) that he simply did not have the political power to make it actually get picked up by the higher ups at Microsoft and that someone else did which is why it took an extra half-decade to actually happen.

I do wonder what would have happened in my career had OneGet actually taken off . Previously I used to work exclusively on Windows, and I now work exclusively on non-Windows machines. At the time that I switched developer experience was one of my primary frustrations - and lack of a proper Homebrew/apt/yum like experience on Windows was a non-insignificant part of that. Chocolatey was OK at the time, but paled in comparison to its MacOS and Linux equivalents.

Is it different/better than choco?

ditto. just cancelled my monthly $ubscription too

I'd start polishing up that resume.

I was responsible for roughly a dozen Signal converts. They will all be uninstalling when this takes effect. It seems like everyone else in this thread is saying the same.

Prepare for a mass exodus of users.

None of us want to be responsible for training/tech support for how to use 2 messaging apps for non-technical users

The complete lack of awareness of this decision is astounding, the userbase is about to disappear. Those of us that convinced non-technical friends and family to use Signal are now expected to explain to them how to juggle 2 messaging apps? yeah it's not happening, the uninstall rate is going to be huge and there will be no recovery of those users