If the requirements for what it needs to integrate with stay stationary then no, but they usually don't.

For example, SQL Server Reporting Services is awesome and still has significant use cases where it is the most appropriate tool. But you'd be waiting forever for an updated report viewer control to place in, say, a new Blazor based app.

It's always up to the owners if they turn tools into abandonware. It's easy to kill products through neglect.

Mind you, I spent the day integrating ADF, AAS, and Power BI again with an app (still in use) that was written in Progress in 1983.

Regards 

Greg

Dr Greg Low
Director
SQL Down Under Pty Ltd
Office: 1300SQLSQL (1300775775)
Mobile: +61419201410
About me: https://greglow.me 

From: mike smith via ozdotnet <ozdotnet@ozdotnet.com>
Sent: Wednesday, June 29, 2022 6:11:46 PM
To: ozDotNet <ozdotnet@ozdotnet.com>
Cc: mike smith <meski.oz@gmail.com>
Subject: Re: It's that time of year - F#
 
Do languages need constant evolution to be seen as successful?  

As a recent post said, look at c++

Mike 

On Wed, 29 June 2022, 11:06 Dr Greg Low via ozdotnet, <ozdotnet@ozdotnet.com> wrote:

In fact, the messaging changed fairly abruptly.

 

Compare Kathleen’s article in Nov 2018: https://devblogs.microsoft.com/vbteam/visual-basic-in-net-core-3-0/

 

With the one 15 months later: https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/

 

Regards,

 

Greg

 

Dr Greg Low

 

1300SQLSQL (1300 775 775) office | +61 419201410 mobile

SQL Down Under | Web: https://sqldownunder.com | About Greg:  https://about.me/greg.low

 

From: Greg Keogh <gfkeogh@gmail.com>
Sent: Wednesday, 29 June 2022 11:21 AM
To: ozDotNet <ozdotnet@ozdotnet.com>
Cc: David Burstin <david.burstin@gmail.com>; David Kean <David.Kean@microsoft.com>; Dr Greg Low <greg@sqldownunder.com>
Subject: Re: It's that time of year - F#

 

Mind you, there have been many interesting languages over the years. And their fate has not always seemed logical.

 

I think a year ago I said something like ... I was excited about F# when it first came out, but never got to write any production software using it. Whenever I sat down to write something serious I got bogged down in choices and syntax details and "bridging" over to other C# libraries to do the heavy lifting. There were lots of other irritations like long searches for good samples, less tooling, less (and bewildering) documentation, smaller community, lack of T4 templates, etc. If I were writing lots of algorithmic code then F# would be a superior choice and all the "bridging" would be pushed to the edges, but lots of typical LOB coding is best done in C#.

 

C# has evolved so far now that it must be the best hybrid language in popular use by a long shot, and its functional features are deflating F#'s functional fame. The downside is that C# is accumulating so many features that I can't remember them all, so I'm thankful when Visual Studio light bulbs appear and remind me to replace my force-of-habit clumsy code. I hope they ease off on new C# features in the future, I don't want it to turn into C++ 20/23 or PL/I (the language that was going to solve every problem in the world).

 

Cheers, Greg K

 

P.S. What happened to VB.NET? No sarcasm, it just seems to have dropped out of articles and announcements.

--
ozdotnet mailing list
To manage your subscription, access archives: https://codify.mailman3.com/