5 ms·

Can you expand a bit on what you mean by "PTSD from frameworks"?

epx 8y ago
Sure. Basically, fear from lock-in, fear from having to do major rewrites because version+1 is completely different, or because vendor ditches the whole thing or goes bankrupt. To be fair, Java and .NET fared well since then - both still exist and it it is very convenient to e.g. drop an old JAR in a project and just use it without issues.
- benaadams 8y ago
  .NET Core has pretty strong backwards compatibility rules: https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/breaking-changes.md https://github.com/dotnet/corefx/blob/master/Documentation/c... > We generally don't accept change proposals that are in bucket #1. ... > Bucket 1: Public Contract Clear violation of public contract. > Examples: > - Renaming or removing of a public type, member, or parameter > - Changing the value of a public constant or enum member > - Sealing a type that wasn't sealed > - Making a virtual member abstract > - Adding an interface to the set of base types of an interface > - Removing a type or interface from the set of base types > - Changing the return type of a member > - ...or any other incompatible change to the shape of an API
- manigandham 8y ago
  Microsoft is arguably the best in the entire software industry at maintaining backwards compatibility. They go to extreme lengths to maintain support for older code and it's relied upon by many major enterprises so you're not going to run into issues unless you're planning on having something running for 50 years.
  - setquk 8y ago
    No it’s really not. We’ve been left SOL on numerous occasions and the churn rate is so high that it’s literally only safe to use the bits right at the middle of their products. And we’re talking on a relatively short three year window here.
    - manigandham 8y ago
      What are you talking about specifically?
      - setquk 8y ago
        WPF, WCF churn, silverlight, appfabric/velocity, the disaster that was windows workflow etc etc
        magicalbeans 8y ago
        Is WPF dead? And what's it been replaced with?
        CodeCube 8y ago
        WPF lives :) https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-support-for-windows-desktop-applications/ https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-...
        manigandham 8y ago
        WPF is still supported and developed. Appfabric/velocity is now Service Fabric which has much more functionality, runs many Azure and MS cloud services, and is open source. Silverlight was unfortunate but overall good for the web. You must realize that even Flash, the vastly larger competitor, also died and gave way to much better browser native APIs. I don’t know about Windows workflow but it’s important to keep in mind the difference between abandoned products vs the changing software trends landscape.

epx 8y ago

Sure. Basically, fear from lock-in, fear from having to do major rewrites because version+1 is completely different, or because vendor ditches the whole thing or goes bankrupt. To be fair, Java and .NET fared well since then - both still exist and it it is very convenient to e.g. drop an old JAR in a project and just use it without issues.

benaadams 8y ago
.NET Core has pretty strong backwards compatibility rules: https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/breaking-changes.md https://github.com/dotnet/corefx/blob/master/Documentation/c... > We generally don't accept change proposals that are in bucket #1. ... > Bucket 1: Public Contract Clear violation of public contract. > Examples: > - Renaming or removing of a public type, member, or parameter > - Changing the value of a public constant or enum member > - Sealing a type that wasn't sealed > - Making a virtual member abstract > - Adding an interface to the set of base types of an interface > - Removing a type or interface from the set of base types > - Changing the return type of a member > - ...or any other incompatible change to the shape of an API
manigandham 8y ago
Microsoft is arguably the best in the entire software industry at maintaining backwards compatibility. They go to extreme lengths to maintain support for older code and it's relied upon by many major enterprises so you're not going to run into issues unless you're planning on having something running for 50 years.
- setquk 8y ago
  No it’s really not. We’ve been left SOL on numerous occasions and the churn rate is so high that it’s literally only safe to use the bits right at the middle of their products. And we’re talking on a relatively short three year window here.
  - manigandham 8y ago
    What are you talking about specifically?
    - setquk 8y ago
      WPF, WCF churn, silverlight, appfabric/velocity, the disaster that was windows workflow etc etc
      - magicalbeans 8y ago
        Is WPF dead? And what's it been replaced with?
        CodeCube 8y ago
        WPF lives :) https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-support-for-windows-desktop-applications/ https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-...
      - manigandham 8y ago
        WPF is still supported and developed. Appfabric/velocity is now Service Fabric which has much more functionality, runs many Azure and MS cloud services, and is open source. Silverlight was unfortunate but overall good for the web. You must realize that even Flash, the vastly larger competitor, also died and gave way to much better browser native APIs. I don’t know about Windows workflow but it’s important to keep in mind the difference between abandoned products vs the changing software trends landscape.