So I was discussing with the Admiral on a C# and Janeva support case. Suddenly, he asked when I'm joining the Delphi development team.
He then pitched the following idea:Manage Delphi as an open-source project internally within Borland. Give access to interested people, such as consultants (like, The Wrist), managers (like Green Fingers), tech support guys (like me) to the StarTeam for Delphi, CaliberRM for Delphi repository.
Then, when we have feedback/bugs/QC entries from customers, we can, after some discussion (over IM, email, CaliberRM discussion, etc), update the Delphi source on our own, and let some guy (a Torvalds-like figure) within the company approve the changes. He's been trying to pitch this idea for a while.
If this idea goes through, it could be applied similarly to all products within the company.
Some wild and brilliant idea huh?
In 2017, with the release of Delphi 10.2 Tokyo, Embarcadero introduced a specialized implementation of the Observer pattern into the System.Classes unit. While it has been in the wild for 9 years, it remains a "hidden" architecture for many, primarily because it serves as the invisible engine behind LiveBindings. Other than live bindings, you can also use the Observer pattern as a way to update component settings to the Windows registry, an .ini file, or persist it elsewhere.
System.Classes