3 ms·

> Microsoft refuses to port System.Speech for text-to-speech and speech recognition. I think it's more complicated than just 'porting'... Something tells me th

> Microsoft refuses to port System.Speech for text-to-speech and speech recognition. I think it's more complicated than just 'porting'... Something tells me that System.Speech is a nice wrapper for a very windows specific API. Similar to how Microsoft isn't bringing over WCF Hosting (Because too many parts of it are dependent on Windows itself.) Now, ideally, it would be nice if Microsoft would expose the existing System.Speech source code, so that somebody could begin the efforts of making it into an OSS Project that could eventually become multiplatform.

ocdtrekkie 6y ago
Windows Forms and WPF are also both Windows API wrappers, and they've been brought over for when you are targeting Windows-based platforms. System.Speech is no longer available on Windows in .NET 5, even if you're using Windows Forms or WPF, which are Windows-only frameworks. In theory, if Microsoft was at least holding up compatibility for such things on Windows, I could move my target towards .NET Core/.NET 5, then gradually replace Windows-specific code with cross-platform code. But as per usual, I'm getting the impression it'd be easier to start over than migrate. I agree it'd be really nice if they open sourced the code necessary to look at porting System.Speech, but I imagine it'd be unpleasant as a business decision: It'd erode their ability to bill people for the Azure "replacement".
CodesInChaos 6y ago
Being windows dependent shouldn't prevent offering System.Speech as a library that targets only windows.
worble 6y ago
.NET Core/Standard already has windows specific API's, and .NET 5 is going to make them safer to use going forward with static analysis[0], so I doubt the Windows specificness is the reason why. 0: https://devblogs.microsoft.com/dotnet/the-future-of-net-standard/#problem-3-net-standard-exposes-platform-specific-apis https://devblogs.microsoft.com/dotnet/the-future-of-net-stan...

ocdtrekkie 6y ago

Windows Forms and WPF are also both Windows API wrappers, and they've been brought over for when you are targeting Windows-based platforms. System.Speech is no longer available on Windows in .NET 5, even if you're using Windows Forms or WPF, which are Windows-only frameworks. In theory, if Microsoft was at least holding up compatibility for such things on Windows, I could move my target towards .NET Core/.NET 5, then gradually replace Windows-specific code with cross-platform code. But as per usual, I'm getting the impression it'd be easier to start over than migrate. I agree it'd be really nice if they open sourced the code necessary to look at porting System.Speech, but I imagine it'd be unpleasant as a business decision: It'd erode their ability to bill people for the Azure "replacement".

CodesInChaos 6y ago

Being windows dependent shouldn't prevent offering System.Speech as a library that targets only windows.

worble 6y ago

.NET Core/Standard already has windows specific API's, and .NET 5 is going to make them safer to use going forward with static analysis[0], so I doubt the Windows specificness is the reason why. 0: https://devblogs.microsoft.com/dotnet/the-future-of-net-standard/#problem-3-net-standard-exposes-platform-specific-apis https://devblogs.microsoft.com/dotnet/the-future-of-net-stan...