What's the biggest design mistake you'd fix in Reform?

question 2 connections

Audience member (Alexei) asks what Nick Sutterer would change if building Reform from scratch. Sutterer jokes that maybe Ruby isn't the right language, but confirms the right decision was to build Reform 3 on Trailblazer — tracing and plug-and-play nested forms are huge time savers. Points to the recorded talk for '45 minutes of pure regrets and design mistakes.'

answer_summary

Nothing fundamental about Reform 3 itself — maybe a non-Ruby language would have been an option. Building on Trailblazer was the right call for tracing and composable nested forms.