About the author
I got an email from an irate customer who wants to know why a particular issue affecting him is not fixed. The issue is an irritation, that doesn't affect his work and production. To put things in perspective and context, it's a sample file that he cannot delete, and doesn't use, which he wishes to delete.
Generally, for any project to be profitable, the R&D for that project has to cater to the common denominator.
At some point in time, the project will become so popular that there are more people using it than the number of people in that R&D group. And the users will file feature requests, change requests, etc. The longer the project is in existence, the higher the number of change requests, enhancement requests and feature requests. At some point in time, there will be more CRs, ERs and FRs than the resources and time available to R&D to implement them.
That is why not every CR, ER, FR can be implemented. This explanation is not just for project X, but for every project in existence.
And no, Project X doesn't refer to Delphi. It's something else. I could be talking about a particular notorious OS.
Learn why the map is cool in Go!
A method to design records so that they're allocated on a specific byte boundary, such as 16 bytes, 512 bytes, 4096 bytes, etc.
Learn the command line used to compile System.pas in Delphi
How to free more space on your home drive by redirecting the location for SDKs in RAD Studio