5 ms·
> Amazon Corretto is a no-cost, multiplatform, production-ready distribution of the Open Java Development Kit I really, really wish AWS would start using pract
by lenova 8y ago
> Amazon Corretto is a no-cost, multiplatform, production-ready distribution of the Open Java Development Kit
I really, really wish AWS would start using practical/self-explanatory names for their products.
- deleted 8y ago[deleted]
- finaliteration 8y agoI’m honestly surprised they didn’t go with “Simple Java Service”. /s Edit: Added sarcasm indicator
- sroussey 8y agoProbably because they don’t own the trademark on Java.
- Spivak 8y agoWithin reason, you are actually allowed to use someone else's trademark for something like this provided your own trademark is the more prominent. So something like "Amazon Distribution for Java" would be fine.
- ksec 8y agoOr something as Simple as Amazon JDK.
- coldtea 8y agoUnless JDK is trademarked to death by Oracle...
- coldtea 8y agoWell, for one it's not a service...
- fredley 8y agoI'll take names over alphabet soup. My EBS EC2 machines are not playing nicely with ELB (but my EFS ones are), I think it might be to do with EMR, or maybe EKS.
- deleted 8y ago[deleted]
- rad_gruchalski 8y agoYou could always say: "My elastic block service elastic cloud compute machines are not playing nicely with elastic load balancers (but my elastic file system ones are), I think it might be to do with elastic map reduce, or maybe elastic kubernetes service." No soup.
- akuji1993 8y agoSo much better.
- mxiia 8y agoso elastic!
- rad_gruchalski 8y agoThat's a different company!
- _verandaguy 8y agoIt feels like English should have a provision to factor out the word "elastic" in this case. Just assume every word in the sentence is elastic.
- kbutler 8y ago"My elastic block service elastic cloud compute machines are not playing nicely with elastic load balancers (but my elastic file system ones are), I think it might be to do with elastic map reduce, or maybe elastic kubernetes service." "My elastic services are not working. Cloud compute machines..."
- vydd 8y agoWell, it's corrected coffee, which matches their intention and general java/beans/jar theme. I kinda like it. https://en.wikipedia.org/wiki/Caff%C3%A8_corretto https://en.wikipedia.org/wiki/Caff%C3%A8_corretto
- fredley 8y agoTIL you 'correct' coffee by adding alcohol.
- foolfoolz 8y agoit doesn’t matter when you have this many products. if you know the product, you will find or learn the name. if you don’t know the product, the name doesn’t matter
- laumars 8y agoI'd argue it matters more when you have that many products because it takes a greater amount of mental mind games to remember what all the arbitrary names and acronyms refer to in terms of real world services. It also makes discoverability harder. eg when you're already on AWS and you think "is there a service that does something like [insert problem]?"
- coldtea 8y ago>would start using practical/self-explanatory names for their products So like "Java" and "Swing"?
- castlecrasher2 8y agoFunny, because I can rarely remember GCP's services yet AWS' I don't forget.
- exabrial 8y agoSpeaking of, CoveffeJDK hasn't been taken yet.
- jfoster 8y agoIt's like they're trying to add an extra layer of stuff that must be learnt in order to use AWS. I have to wonder if it's intended to gear them toward being able to create AWS-specific exams & certifications.
- bborud 8y agoI'd settle for properly written documentation. I'm a long time AWS customer and I love AWS, but to be honest, the documentation is bad. I don't think they understand how to write for developers at all. It feels like they hired an army of Kevin Turvey clones.
- ravenstine 8y agoI find that the structure of their documentation could use some work, but the actual language to be fairly good. And by good, I mean less bad when contrasted with most documentation. To go off on a bit of a tangent, I'd prefer that documentation be split up into two parallel versions that are heavily linked but mostly separate: - Code examples describing everyday usage - Detailed API/system descriptions AWS should do a better job on the former, although that'd be a massive amount of work for them at this point with little payoff. I find that I end up relying much more on Stack Overflow and even code from wrapper libraries to understand how to do relatively uncomplicated things with their API. In general, however, I'd prefer it that all documentation be more the former than the latter. I find that when I'm given everyday examples, that aren't hideously formatted on the webpage, I can get a better understanding much quicker and become far more productive. Most documentation isn't good at either providing practical examples or actually explaining usage. I feel like there's a missing link between English-majors and software engineering; if there are English-majors who also understand programming, they should be paid handsomely to write documentation. But when do we ever see job postings for specialists in writing documentation? I've never seen such a job title.