Update on the Colossal Backlog Publishing Endeavor

I need every drop of writing power in me to go toward writing this monument so I’ll keep this short. Per my last post I’m taking my 12-page outline for the ModVB language enhancements and expanding it out into a high-ish level conceptual overview of each enhancement with a short-ish motivating scenario and/or example of each. I hoped to be done by end of July. That was pure foolishness. As it stands this overview will definitely be over 100 pages printed!

Unlike my original Exhausting List of Differences Between VB.NET and C# post, this won’t be a single monolithic document. To make it easier to publish, revise, read, comment on, link, etc. instead I’ll be publishing each enhancement as a separate post. They’ll all be published at the same time and linked from a master table of contents (and maybe an index) which will be the “post”. Right now that means something over 110 (and counting) separate posts each averaging about a printed page, organized into 14 sections (and counting).

I’m trying to keep them all at a similar level of detail which is more than “I got an idea”/suggestion on GitHub/UserVoice level but not as detailed as a feature speclet that a inexperienced compiler dev could immediately start work off. I have several reasons for not wanting to publish each post one at a time over the next 4 months, one of which is that it would mean publishing each post one at a time over the next 4 months. But also, doing it this way will empower us to have a much better conversation about the entire scope of the backlog, prioritization, and how and where it could make sense for future contributors to pitch in.

Sorry it’s taking so long, but this is the culmination of 20 years of professional experience working in and on VB.NET, we’re all going to have to be patient with it. Thanks!

Regards,

-ADG

2 thoughts on “Update on the Colossal Backlog Publishing Endeavor

  1. Impressive.
    I just think it would be better to publish these posts at GitHub, as we can quote and format code better.

    Like

    • I understand. I’m trying to keep this at a blog post level of detail for discussion and eventually have GitHub issues that are proper speclets and full feature specifications. The blog will focus more on the high level what and why whereas GitHub would be low-level what and how. But I’m always conflicted. What do you think of the GitHub discussions feature?

      Like

Leave a reply to م. محمد حمدي غانم Cancel reply