4 ms·
I didn't know Amazon also had a translation service. I wonder how it compares to Bing, Systrans, and Google?
by fouc 8y ago
I didn't know Amazon also had a translation service. I wonder how it compares to Bing, Systrans, and Google?
- philshem 8y agoAdd Deepl to the list
- markdown 8y agoFrupr as well.
- 11235813213455 8y agoAzure too
- hiccuphippo 8y agoIt would be fun to see a website that lets the user input a string and compare all these APIs.
- amaccuish 8y agoAs an undergrad in French, German and Russian, Deepl has been amazing. Always used linguee to see stuff in context, but deepl is very impressive!
- jak92 8y agothrow everything on the wall and see what sticks... how much of these amazon services are even remotely worth using?
- trhway 8y agoit seems that AMZN's spaghetti has pretty high coefficient of stickiness or may be some secret marinara sauce ...
- whoisjuan 8y agoAWS is not an indie maker trying to see what sticks. They literally build what their customers ask for and a $30 billion ARR shows that most bets payoff. If they don't build their own Translate service then they can't compete in that area with other cloud vendors. If you think AWS services are not worth using, then you don't understand the value proposition of managed services built on top of fully integrated elastic/highly-available insfrastructure. That's not a bad thing. You don't necessarily need to understand that value proposition. But you're definitely not the target audience for this.
- kahnjw 8y agoOn the other hand some services from AWS are downright bad. For instance, Elastic Beanstalk is an operational nightmare. The one selling point is that it's easy to get started with, but from there it seems they rely on ops lock-in to pay the bills for this product. It's slow, clunky, and opaque. There are much better alternatives that don't force you to tradeoff usability and lock-in for initial ease of use.
- DanFeldman 8y agoThen again, ELB was amazing a few years back when the tooling for dealing with AWS/GCP/Azure was not as mature. ELB wrapped a huge percentage of the use cases (webapps) in one or two configs. Sure, now there's a ton of better/more scaleable/cheaper options, but ELB was great before.
- bg24 8y agoRemember that some services live their life (peak growth and in top 10 list of management), do their job (stable phase) and then run out of steam (tech landscape change, corporate priorities change). It is natural for folks to eventually move off beanstalk into lambda, ecs and forgate. In it peak, beanstalk was the go to service to set up an auto scaling app from code. People have moved on into containers and serverless now. Not so much about beanstalk being bad.
- jjoonathan 8y agoMore than a few AWS services lean rather heavily on "being AWS" for their value proposition as opposed to being any good at their job. They do this because they can, and they can because, as you pointed out, once infrastructure and permissions and billing are set up with one cloud vendor, it's usually easier to deal with a mediocre-to-bad product than with integrating an entirely new cloud or tech stack. AWS is the new IBM, with all the good and bad that entails.