ayanb

Super interesting article - thanks for sharing your journey. As AI slop takes over the internet, well written and original technical content like these will be important.

Also,

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

Thanks for highlighting. I just realized this is open to developers who aren't city employees, which is unique. A city can pay a vendor for a deliverable, but paying an outside individual to improve something the city doesn't own is interesting (to say the least)

>> this is how Java, .NET, etc packaging is done for interop with Electron

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

Very interesting gameplay - I played a bit :)

> 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?

Could you elaborate a bit more about the a12y-focussed architectural constraints that you want to enforce?

Do you see a future where cross-platform could essentially be a set of tools/frameworks to build high performance native experiences targeting the browser as the primary runtime?

Curious - could you elaborate how you think this abstraction will happen over time?

great - I sent you a note over on LI. Hoping we can jam a bit on the network logic and tooling available to fast track things.

Cool product! are you guys using wasm under the hood?

Nifty start. The need for a hosted service like this is more for secure apps where third-party services may have some privacy implications.

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?

Inclusions usually come from the community - users tend to add products to their stack, a lot of them obviously being OSS. We have tried to reach out to creators/admins in the past to understand if they'd like to represent themselves in the right way in front of a large buyer group.

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.

Yeah, NPS is a good way to understand how actual customers feel about a product. We have collected tens of thousands of sentiment over the last six months on a wide range of products, and at scale, this sentiment data set can be quite valuable.

In this case, the primary category for Intercom is `User onboarding and Engagement` which can be broken down separately to `User Onboarding` and `In-app Support` or `In-app Chat`. That will suddenly spike up the sanity of both categories (maybe we can even normalize further - siftery has more than 700 categories/tags, a first for any such platform).

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?