#nodeapi — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #nodeapi, aggregated by home.social.
-
via #AIFoundry : Foundry Local 1.1: Live Transcription, Embeddings, and Responses API
https://ift.tt/O1MorgK
#FoundryLocal #LiveTranscription #EmbeddingsAPI #ResponsesAPI #WebGPU #ONNXRuntime #NodeAPI #PythonSDK #JavaScriptSDK #CSharpSDK #DotNet #NetStandard #WinML #Koffi #No… -
via #AIFoundry : Foundry Local 1.1: Live Transcription, Embeddings, and Responses API
https://ift.tt/O1MorgK
#FoundryLocal #LiveTranscription #EmbeddingsAPI #ResponsesAPI #WebGPU #ONNXRuntime #NodeAPI #PythonSDK #JavaScriptSDK #CSharpSDK #DotNet #NetStandard #WinML #Koffi #No… -
via #AIFoundry : Foundry Local 1.1: Live Transcription, Embeddings, and Responses API
https://ift.tt/O1MorgK
#FoundryLocal #LiveTranscription #EmbeddingsAPI #ResponsesAPI #WebGPU #ONNXRuntime #NodeAPI #PythonSDK #JavaScriptSDK #CSharpSDK #DotNet #NetStandard #WinML #Koffi #No… -
via #AIFoundry : Foundry Local 1.1: Live Transcription, Embeddings, and Responses API
https://ift.tt/O1MorgK
#FoundryLocal #LiveTranscription #EmbeddingsAPI #ResponsesAPI #WebGPU #ONNXRuntime #NodeAPI #PythonSDK #JavaScriptSDK #CSharpSDK #DotNet #NetStandard #WinML #Koffi #No… -
via #AIFoundry : Foundry Local 1.1: Live Transcription, Embeddings, and Responses API
https://ift.tt/O1MorgK
#FoundryLocal #LiveTranscription #EmbeddingsAPI #ResponsesAPI #WebGPU #ONNXRuntime #NodeAPI #PythonSDK #JavaScriptSDK #CSharpSDK #DotNet #NetStandard #WinML #Koffi #No… -
Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.
Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?
-
Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.
Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?
-
Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.
Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?
-
Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.
Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?
-
Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.
Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?