GoogleNetworkSpeechSynthesis VS proposal-type-annotations

If you want you can use Google's TTS service without Web Speech API with a proxy, see GoogleNetworkSpeechSynthesis. I made a feature request for Google to release the source code as FOSS Re: Issue 263510047: Release TTS and STT source code and Google voices as FOSS so we don't have to make external requests just to use Web Speech API.

I requested to Google to Release TTS and STT source code and Google voices as FOSS which you can request over the network here GoogleNetworkSpeechSynthesis. Those are the voices Google Chrome uses for Web Speech API. Feel free to chime on the feature request in in support of Google releasing the source code of its network-based cloud service (that google uses for Web Speech API implementation) TTS and SST code as FOSS.

Technically you can use Google API key shipped in the browser see guest271314/ GoogleNetworkSpeechSynthesis . No need to sign up for a Google account to use this. I don't think Google's TTS is related to "AI".

This is how you can make the request yourself GoogleNetworkSpeechSynthesis.

If anybody want to build a TTS "module" or "component" that accepts and processes SSML input, and that the user can control - to an appreciable degree - on the front-end you can play around with this https://github.com/guest271314/GoogleNetworkSpeechSynthesis. (Makes an external request). Have fun!

It is possible to use Google Network Speech Synthesis service "free of charge", see GoogleNetworkSpeechSynthesis. On Chrome if you use Google voices with SpeechSynthesisUtterance() and window.speechSynthesis.speak() you are doing that anyway.

I implemented SSML parsing in JavaScript by hand for Web Speech API per SSML specification https://github.com/guest271314/SSMLParser, where the Web Speech API nor Firefox nor Chrome or Chromium browsers (Google does implement SSML parsing as a service https://github.com/guest271314/GoogleNetworkSpeechSynthesis) have implemented SSML parsing.

FYI when Google voices are used on Chrome or Chromium-based browsers the browser also makes a remote request, see https://github.com/guest271314/GoogleNetworkSpeechSynthesis.

How is processing SSML an attack vector? Google provides that capability as a service - with embedded limitations on character input that are not specified. This can and should be implemented in the browser - without making an external request; native-messaging-espeak-ng, GoogleNetworkSpeechSynthesis.

That proposal is not fully compatible with Typescript: https://github.com/tc39/proposal-type-annotations?tab=readme...

They held a meeting a few months ago so it's alive but probably still years away.

https://github.com/tc39/proposal-type-annotations/issues/184

I particularly like this thread in the TC39 types proposal. TypeScript IS a development trojan horse and locks you into the Microsoft Way of being a JS developer.

Edit: There is a proposal to extend JavaScript with type annotations, which would allow ("a reasonably large subset") of TypeScript to run directly in the browser. Yay!

https://github.com/tc39/proposal-type-annotations

More importantly, TypeScript typically commits to build things into itself when the proposal in JavaScript reaches Stage 3. The pattern matching proposal in JavaScript is Stage 1, but depends on many other proposals as well that may or may not need to be at Stage 3 as well for it to work. This particular proposal is interested on pattern matching on JavaScript Objects and other primitives, just like Python does with it’s native primitives. These are also dynamic types which helps in some areas, but makes it harder than others. Additionally, the JavaScript type annotations proposal needs to possibly account for this. So it’s going to be awhile. Like many years.

this is exactly what I want from the _Types as Comments_ proposal[0] as I think it's the only way that types can feasibly become part of the language. It's hard to imagine how all of the concepts TS introduces via special syntax can be covered otherwise.

[0] https://tc39.es/proposal-type-annotations

Crossing my fingers that the proposal for allowing (browser-ignored) type annotations in javascript progresses: https://tc39.es/proposal-type-annotations/

Between that, HTTP2/3 and ES modules many of the downsides for building apps with no compile step are almost completely mitigated.

JSDoc can get you pretty far, but it can be clumsy sometimes. There’s a [TC39 proposal](https://github.com/tc39/proposal-type-annotations) to allow types to live in JS code and be treated as comments (similar with Python types today)