News for hackers. Stuff that matters.
Re:.NET JIT and CLR – Joined at the Hip by epx on Thursday July 05, 2018 @04:43PM (#17466670)
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.

Re:.NET JIT and CLR – Joined at the Hip by manigandham on Thursday July 05, 2018 @09:45PM (#17468332)
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.
Re:.NET JIT and CLR – Joined at the Hip by setquk on Friday July 06, 2018 @03:03AM (#17469525)
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.
Re:.NET JIT and CLR – Joined at the Hip by manigandham on Friday July 06, 2018 @04:19AM (#17469801)
What are you talking about specifically?
Re:.NET JIT and CLR – Joined at the Hip by setquk on Friday July 06, 2018 @07:25AM (#17470529)
WPF, WCF churn, silverlight, appfabric/velocity, the disaster that was windows workflow etc etc
Re:.NET JIT and CLR – Joined at the Hip by manigandham on Saturday July 07, 2018 @04:08PM (#17480281)
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.

Re:.NET JIT and CLR – Joined at the Hip by magicalbeans on Friday July 06, 2018 @12:19PM (#17472639)
Is WPF dead? And what's it been replaced with?
Re:.NET JIT and CLR – Joined at the Hip by CodeCube on Friday July 06, 2018 @02:03PM (#17473683)
Re:.NET JIT and CLR – Joined at the Hip by benaadams on Thursday July 05, 2018 @06:50PM (#17467529)
.NET Core has pretty strong backwards compatibility rules:

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