Also,

2026 web dev: 4MB of JavaScript to render a button. 2026 N64 dev: entire FPS in 1MB

It's a sync infra product that is meant to cut down 6 months of development time, and years of maintenance of deep CRM sync for B2B SaaS.

Every Salesforce instance is a unique snowflake. I am moving that customization into configuration and building a resilient infrastructure for bi-directional sync.

We also recently launched a pretty cool abstraction on top of Salesforce CDC which is notoriously hard to work with: https://www.withampersand.com/blog/subscribe-actions-bringin...

not certain if this should be the status quo for the longer term.

> We had to implement techniques like client side prediction, server reconciliation and entity interpolation so that players look smooth when they are moving in the 3D space.

Curious: what kind of tools/frameworks could have helped in shipping to wasm faster and better?

I think the default UI needs a little more work. Intercom also lets you email users based on certain triggers, is there an email integration that you are building towards?

Edit: Just curious, what made you code the server in Go?

Apologies Matt - we'd love it if you gave the platform a try, but will not include you in any future email-campaign, going forward.

Categorisation of a data set like this can be non-trivial and will false positives. We can cherry-pick such a false positive and ignore all the actual positives. That said, thanks for this feedback - this is exactly what is needed to improve status quo. We are on it and will report back in a few hours with the category split I suggested in the previous paragraph. Do let me know if you think it can be broken down into a different type of granularity?

We have 40K+ products in the DB, so you are in good company :)

0) We analyze products that have a public footprint.

1) We analyze products that don't have a public footprint.

2) For 0), we crawl the internet periodically and create a time series curves of B2B product usage for companies.

3) For both 0) and 1), our verified community has trained our algorithms with tens of thousands of data points on usage and sentiment, thereby reinforcing or nullifying these deductions.

4) If you have stopped using Angular and started using React (or vice-versa now that Angular 5 has better server-side rendering), it is deductible at a global context.

This is merely v1 and we intend to iterate quickly on this dataset and provide more intelligence/decision support for buyers when they are looking for alternatives to switch to for a specific product or across a category.