I thought I was building a C replacement. I was wrong

The writer initially believed they were developing a C replacement with C3, but gradually realized their mistake. In the 80s and 90s, when the writer started programming, C was considered an application language. The writer's experience with BASIC, assembly, Pascal, and C led them to appreciate procedural programming. After learning Java, the writer developed a love for object-oriented programming (OOP) despite finding it challenging initially.

Throughout their career, the writer observed that OOP's up-front architecture and reliance on methods often hindered the ability to refactor code, which in turn, made them reluctant to make changes. The writer's experience with PHP demonstrated that OO parts were not necessary for creating abstractions, further solidifying their belief that OOP was making it harder to write good programs with good architecture.

As a result, the writer concluded that C3, a C-like language, was not the solution they were seeking for modern application development.