Alexander Morou
Sponsor
Don't feel bad.
Sometimes things like this are to be expected in a development life-cycle. It just happens. You take steps to make sure it doesn't happen, but it's at least better than saying 'It's canceled'.
Myself, I feel the same way with Abstraction. The project in the OIL framework alone is 61,000 lines in over 796 files. It's not even half done.
The entire project is over 1,070 files and 200,000+ lines. While lines don't relate to quality or functionality, it marginally relates to the time spent on a project. Right now Abstraction doesn't build due to a structural rework I'm doing which segments Array Types, Generic Types, and other specific functionality away from the base IType. Which caused 300+ errors to crop up in a heart beat. Most of the disambiguating code, System.Type->IType relationships, and a large series of other core functionality needs to be rewritten as a result. I could stop and rewrite the entire project because of the slight oversight; however, I thought it best to continue because of the functionality that was not affected by the change.
I envy that your project is at a scope where you can aim for December, amidst a rewrite, while I'm looking at May of 20??.
Sometimes things like this are to be expected in a development life-cycle. It just happens. You take steps to make sure it doesn't happen, but it's at least better than saying 'It's canceled'.
Myself, I feel the same way with Abstraction. The project in the OIL framework alone is 61,000 lines in over 796 files. It's not even half done.
The entire project is over 1,070 files and 200,000+ lines. While lines don't relate to quality or functionality, it marginally relates to the time spent on a project. Right now Abstraction doesn't build due to a structural rework I'm doing which segments Array Types, Generic Types, and other specific functionality away from the base IType. Which caused 300+ errors to crop up in a heart beat. Most of the disambiguating code, System.Type->IType relationships, and a large series of other core functionality needs to be rewritten as a result. I could stop and rewrite the entire project because of the slight oversight; however, I thought it best to continue because of the functionality that was not affected by the change.
I envy that your project is at a scope where you can aim for December, amidst a rewrite, while I'm looking at May of 20??.