Was actually pulling on a similar thread as I saw announcement so I integrated it just for fun. Have been only running this on my Framework Desktop but should be runnable elsewhere
https://github.com/olafura/gemma-4-mic-transcribe
I still don't understand this. If you are big enough then you get Amazon to make an official sdk, if you aren't then what exactly are you looking for?
The official aws cli used to talk to the soap interface and used regex instead of actually doing correct error handling and that was used by so many tools. Even though it used to break horrible.
It's quite a niche you are talking about, not big enough to debug open source code but still big enough to require SLA for SDK and not being able to talk Amazon into creating it. It's generated code, it's not rocket science.
What I have experienced is that software licence, where you are sending data to, where you are hosting it and having access to audit the code has usually been a bigger concern.
But then again big organisations often have really specific concerns. So I'm not doubting your statement it's just that I have never heard it before.
What are you talking about, there has been a AWS client forever and I've never had a problem. It's not something you really need an official sdk for they are anyway often just reference because you might want different performance characteristics.
I've usually not seen more than 3 or so official SDK for most services and there are a lot more programming languages than that. For example Microsoft's Graph API doesn't have an official Ruby client, they have one that sort of works.
Very exciting, there are so many things happening in the Elixir Machine Learning space, with all of it focusing on being easy to deploy and test yourself.
I just love that you can create robust ML services. Which for me, isn't as easy to do in Python, even though I've created async service with core Tornado before asyncio was a thing.
I don't understand how this is a difference between stacked diffs and feature branches. Github allows you to use feature branches. I can see there might be some convenience with tooling
So the question is why a project created in a language that has been around since before the devices being emulated are more mature than ones in a language that is 8 years old?
Sorry to be so snarky. It probably depends on people's time working on it and their familiarity with async processes. This is an inherent problem with any media like that. With sound, it's primarily that it can't come before the image but can lag behind the image. Stuff like this.
I don't think any programming language is going help with that because it's how we perceive things, not just how correct your code is.
I feel like the biggest problem is most COBOL code is heavily tied to the mainframe it's running on [1]. There are already ways of compiling COBOL code with a modern compiler [2].
There are also multiple other translation projects:
I really like Lit. It makes you in most cases write better reusable components, though you should still check all the properties to see if they are too reliant on some property.
We started using it because we knew it could be embedded into any other framework, we are using two others in the company. But are starting to use it for SPA also. Glad to see it growing quickly.
Thinking about possibly reworking our SPA to use Phoenix LiveView most of the abstractions are there already.
There are no links to news articles and they are nowhere to be found. There is an obvious trademark problem which makes it harder to search for the product.
Looks really cheap and if I understand the technology correctly would only have a small area that you can see correctly through.
I like that we have something that will work at such a low bandwidth. But it does sound like real audio with the wobbly ( robotic ) tone of voice is back.
Regarding the my browser isn't supported they are just trying to have it optimized and in the manner that they see as the way forward. You should still be able to send this as data with webrtc. If there was no way of implementing it without this api then it would be different.