But with SwiftUI, Swift has also become "unfun." SwiftUI and Apple's half-assed, broken observation and "reactive" paradigm have made programming a joyless slog.
I wonder if Xcode does any better with them. Now that would be something.
It's a bit tongue in cheek but: "Are we modules yet? Nope. ... Estimated finish by: Wed Sep 20 2541"
Having to define header files in C++ is pretty annoying after doing Swift for many years.
There is nothing wrong with header files. In fact, there is no such thing as a header file specified in C++. There are only forward declarations and definitions, and how those can be managed by developers.
Meaning, any talk about header files is a discussion on software engineering practices, and how developers create or avoid their own problems.
Why do we need to manage them?
Why do developers need to write code that makes sense and does what they want it to do?
Is that supposed to mean anything at all?
They do, except they don't have the bandwagon effect motivating them to complain about other solved problems.