The Impact of Log4j on Software Development with Delphi and C++Builder - Delphi-PRAXiS
Summary
As was mentioned last week, (while not directly responsible for the Log4j issue) is a coding style on the flip side of writing secure applications. The idea that you can use open-source to save costs without contributing back any time, resources, or money to the projects you leverage is becoming a huge problem in the industry. The coincidental discovery of this critical bug in the context of Minecraft console messages (typing a message on the Minecraft game client could let someone execute code on a Minecraft server) due to the use of an extremely popular Java logging library called Log4j , caused every single IT company and every company using software applications to check if the issue was affecting the companys software, hosted services, internal web sites, and any other use case scenario.The list of affected software applications (there is one here , for example) is fairly impressive, because despite having lost some of the hype and marketing push, Java is and remains one of the worlds most popular languages, and the JVM one of the most popular runtime execution environments.Now, what does this mean for Embarcadero in general andStudio in particular? As was mentioned last week, copy-and-paste coding (while not directly responsible for the Log4j issue) is a coding style on the flip side of writing secure applications.There is also another key issue that the Log4j problems made obvious: there are multi-million dollar projects managed by large corporations that rely on open source projects with no funding, managed by developers in their spare time (outside their regular jobs). The idea that you can use open-source to save costs without contributing back any time, resources, or money to the projects you leverage is becoming a huge problem in the industry.This is also true of the Delphi and C++Builder ecosystem: Embarcadero has started funding and donating to a few open source libraries, but we should do more.