Skip to main content
I'm not sure if a bus will show up.
Source Link
Reaces
  • 5.6k
  • 14
  • 24

To be honest I'm kinda torn by this.

I know people who are still using WfW 3.11, they will continue to do so for the next decade or so too. They knew this would happen when they started the project and took appropriate actions. From a hardware perspective they bought sufficient extra to last them the lifetime of the project. From a software perspective they got stable with the platform and developed their programs against it. Any busbug that may turn up will get fixed against the same platform or the program gets migrated (at considerable cost) to a newer more supported platform. These guys are good - we will never see a question from them.

If someone asks a question about maintaining a legacy environment then it's helpful to answer it.

If though, someone is developing with a legacy environment then it is not helpful to answer it because using a legacy environment for something new is the wrong thing to do. It should be closed off topic with the reason: Questions should demonstrate reasonable business information technology management practices.

We are not the internet's support safety net.

To be honest I'm kinda torn by this.

I know people who are still using WfW 3.11, they will continue to do so for the next decade or so too. They knew this would happen when they started the project and took appropriate actions. From a hardware perspective they bought sufficient extra to last them the lifetime of the project. From a software perspective they got stable with the platform and developed their programs against it. Any bus that may turn up get fixed against the same platform or the program gets migrated (at considerable cost) to a newer more supported platform. These guys are good - we will never see a question from them.

If someone asks a question about maintaining a legacy environment then it's helpful to answer it.

If though, someone is developing with a legacy environment then it is not helpful to answer it because using a legacy environment for something new is the wrong thing to do. It should be closed off topic with the reason: Questions should demonstrate reasonable business information technology management practices.

We are not the internet's support safety net.

To be honest I'm kinda torn by this.

I know people who are still using WfW 3.11, they will continue to do so for the next decade or so too. They knew this would happen when they started the project and took appropriate actions. From a hardware perspective they bought sufficient extra to last them the lifetime of the project. From a software perspective they got stable with the platform and developed their programs against it. Any bug that may turn up will get fixed against the same platform or the program gets migrated (at considerable cost) to a newer more supported platform. These guys are good - we will never see a question from them.

If someone asks a question about maintaining a legacy environment then it's helpful to answer it.

If though, someone is developing with a legacy environment then it is not helpful to answer it because using a legacy environment for something new is the wrong thing to do. It should be closed off topic with the reason: Questions should demonstrate reasonable business information technology management practices.

We are not the internet's support safety net.

Source Link
user9517
  • 116.8k
  • 4
  • 55
  • 131

To be honest I'm kinda torn by this.

I know people who are still using WfW 3.11, they will continue to do so for the next decade or so too. They knew this would happen when they started the project and took appropriate actions. From a hardware perspective they bought sufficient extra to last them the lifetime of the project. From a software perspective they got stable with the platform and developed their programs against it. Any bus that may turn up get fixed against the same platform or the program gets migrated (at considerable cost) to a newer more supported platform. These guys are good - we will never see a question from them.

If someone asks a question about maintaining a legacy environment then it's helpful to answer it.

If though, someone is developing with a legacy environment then it is not helpful to answer it because using a legacy environment for something new is the wrong thing to do. It should be closed off topic with the reason: Questions should demonstrate reasonable business information technology management practices.

We are not the internet's support safety net.