The people I worked with were not specifically HN audience. Rather in the Java bubble in Germany-Austria-Switzerland which is also surprisingly a small world. If BPMN is not really needed, then I would also not use it nowadays. It increases complexity, and who knows if it makes project communication better at all.
Update: On the Camunda website there are 60 case-studies of customers/clients using BPMN, https://camunda.com/case-studies/. One of them has the teaser: "The 10th largest US Bank created an omnichannel onboarding platform that handles 12m process instances per year across 100 workflows". Now I have something to read for this Sunday evening.
That's a lot less that what TSGO promised when it was first announced (A 10x faster Typescript¹). Hopefully this is just the result of it being experimental.
1: https://devblogs.microsoft.com/typescript/typescript-native-...
Maybe the `tsc` type-checker was already fast (so we only get some speed improvements in `tsgo`), or the `tsc` compiler was not that fast (so we get a lot of speed improvements in `tsgo`)?
*Update:* There was a performance regression in incremental type-checking between `tsgo` preview 20251209 and 20251211 [1]. But `deno` is using `tsgo` 0.1.11 which was already released last week (before this regression). So, does not seem to influence the type-checking times here.
[1] https://github.com/microsoft/typescript-go/issues/2341 [2] https://github.com/denoland/deno/blob/v2.6.0/cli/tsc/go/tsgo...