If they are simply using Git under the hood, storing every single revision is exactly what it's doing. It's currently a foundational issue with Git. Git-lfs exists as a clunky workaround (but almost certainly wouldn't work with Abstract).

Wow that was fast. Thank you!

That all makes sense, thanks for answering my questions!

I am confused. Does this curate listings from all the job boards listed? What will entering my email address to get notified actually notify me of? What is a "golden remote"?

Sure

We had an issue where text in symbols was showing up as a bulleted list. Heads up that they moved the list type options from the right sidebar to the Text menu at the top.

It's when you get feedback on a design asynchronously, not in real-time. For example, you might email a Google Doc to someone asking for their thoughts. They can comment when they have time, on their own schedule. I've done this with InVision, where people can add comments over a few day span.

Definitely fits in with my experience, nice work! Have you tried out async critiques at all?

IMO, Framer made it wayyyy easier to prototype using code than starting from scratch with HTML/CSS/JS. Sure, it's easy to get a basic webpage up, but what happens when you want live reloading? Need to find and add tooling. What happens when you want to be able to drag things around the screen? Either find a library or understand the web's low-level interaction APIs.

Framer abstracted all of that into an IDE and API that was very easy to pick up and use compared to a "from scratch" approach.

I could see that working. I think PMs would miss a lot of the details, but the designer would catch them. The only downside is that it could be a lot of manual work, depending on how many pages you have to repeatedly do design QA on.