Marcel Offermans
Registered
UIs are easy to write (compared to real-time code certainly) and I assume all the code that does the heavy lifting behind the scenes (what actually happens when you select a car or change a spring rate) already exists.
UIs are very difficult to design well but simracing UIs are not new.
I'm mystified why it's taking so long.
(Speaking as a software engineer with 40 years' experience.)
Since you're a software engineer, let me give you some insights into this task:
- When designed well, UI and logic are totally separated (often using a pattern like MVC) but this was not the case here. The UI contained both state and logic in the actual UI elements, so there was a lot to analyze and untangle. Did I say a lot?

- Whilst I can somewhat agree with the statement that "UIs are easy to write" there is definitely a lot of nuance there. It's not uncommon for developers to spend most of their time on the UI, compared to whatever backend, as that is what users are exposed to every day and if you look at companies like Apple you could say they obsess over all the graphical and functional details and probably even spend up to 80% of all their time on that.