However, APIs like Watson Assistant or Amazon Lex make it easy to build services that can apply logic to observed patterns in those natural-language requests. These services may, for instance, observe a sudden rush of calls from an airport suffering take-off delays and change the sequence of options to prioritize rescheduling flights. Or they may see that calls from a particular country or region tend to be... - Source: dev.to / 14 days ago

Amazon's doesn't care about Mturk, they have their own AI that will eventually automate all their work too https://aws.amazon.com/lex/. Source: about 1 year ago

Amazon Lex, AWS's natural language conversational AI service. With Amazon Connect, it seamlessly leverages Amazon Transcribe to understand what is being said (speech-to-text), and Amazon Polly to provide the verbal response (text-to-speech). We aren't really using the Natural Language powers of Lex, but it has other uses for us:. - Source: dev.to / over 1 year ago

AWS has three high-quality tools: Amazon Lex, Amazon Rekognition, and Amazon SageMaker. - Source: dev.to / over 1 year ago

Introducing DTMF slot settings within Amazon Lex.Amazon Lex is a service for building conversational interfaces into any application using voice and text. With Amazon Lex, you can quickly and easily build conversational bots ("chatbots"), virtual agents, and interactive voice response (IVR) systems. Amazon Lex is excited to launch DTMF-only slot settings and configurable session attributes within the Lex console. - Source: dev.to / over 1 year ago

It has, but it wasn't adopted by the pragmatists in that time. It's hard to tell if the early adopters adopted it either - It doesn't show up at all in the 2023 stack overflow survey (nor in the previous two years) - https://survey.stackoverflow.co/2023/#technology-most-popular-technologies - It doesn't show up in questions asked on Stackoverflow since 2008 -... - Source: Hacker News / 6 months ago

> In 2017 I had React projects in production for years. I doubt that. React wasn't stable until 2015, and wasn't mainstream until 2016. > And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are faster than React out-of-the-box. Again, Next.js != React; the former builds on the latter, it doesn't replace it nor does it claim to be the same... - Source: Hacker News / 8 months ago

> Prior to Next.js, React was hard to setup and maintain No, it wasn't. > I started using Next.js in 2017. It made React a real production framework In 2017 I had React projects in production for years. > React was hard to setup and maintain and hard to make it go fast (on first load) And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are... - Source: Hacker News / 8 months ago

Based on what? https://insights.stackoverflow.com/trends?tags=python%2Cjava. - Source: Hacker News / 10 months ago

Fair enough, my information is outdated. StackOverflow agrees. [1] [1] https://insights.stackoverflow.com/trends?tags=django%2Cruby-on-rails. - Source: Hacker News / 10 months ago