The Importance of Releasing Archived Legacy Software

Ryan Walpole Enterprises has a rich history within software development. Before starting Pudince, the CEO of RWE (founder and long time CEO of Pudince LLC) Ryan Walpole, was releasing software online including early iterations of Pudince AeroBrowse, Pudince Anima (later a part of Microsoft Silverlight) and more.

When looking to the future of software development, we see things becoming more unified, simplified and streamlined. We see being able to program software for multiple different devices and architectures at the same time, with the same code and languages. This innovation in the software development industry comes as a direct result of looking back on the past. What has been the most difficult for developers? What would make things better and easier for developers? How do we keep this art of software engineering alive?

We look back on legacy software to see our mistakes, our successes, our past, our future and our present. We look back on this legacy software to learn and improve. For this reason, Ryan Walpole Enterprises is announcing an intent and a plan to bring some of our legacy software back into the hands of consumers for nostalgia, historic evaluation and general evaluation.

In the coming months, Ryan Walpole Enterprises will be repackaging and rereleasing legacy versions of products in the following software families:

  • Pudince AeroBrowse (AeroBrowse, AeroDev, AeroBrowse Rendering Engine for Developers, AeroApps)
  • Ninko (Ninko Explore, Ninko Configurator)
  • Development Software (Code LX IDEs, DevBox, TPNDN Software)

We’d like to say that we will have some of this software in your hands in a short time, however, this is just something we cannot promise.

We’d also like to clarify that while this software will be legacy software, it will not be as is when it was released. There are resources that are no longer hosted online that will simply render the software inaccessible. We will be making an effort to restore the software to working order whilst not changing the fundamental code of the application. This might mean updating to a slightly newer version of the .NET framework, re-uploading web related content to and changing all references within the code to reflect the new web location, and more.

We are also extending our commitment to record keeping and hosting to cover this new project. We currently have committed to storing all future changelogs on our website as well as any software content that is hosted online for a long time to come. So much of our old legacy software could still work today if we had made this commitment 10 years ago.

We hope to have some fun legacy software for you to try in the coming months.
Thank you for a wonderful thirteen years of software.