Not surprising to me. Tons of gigs I’ve had the corporate browser was locked to IE. mainly because of internal site compatibility. Those poor few IT folk I bet are using AWS for their “voodoo computer magic” they provide those uncaring businesses for everything technical.
Considering that IE was sunset in Nov 2019 and officially becomes abandonware next June this shouldn't be a shock. Microsoft still considers IE to be an operating system component, which suggests that they may arbitrarily remove it from user devices in forth coming security patches following June 2022.
Since edge has an IE mode, there is no reason to not just drop it. Internal sites can keep using compat mode and external sites automatically use the chrome based engine.
It seems odd that so much is required for basic access. Shouldn't there be some kind of mode that makes a marked up document out of everything and takes basic input?
Basic CSS layout features are missing from IE. If you want have a toolbar with some icons in it, you either have to do some hacky things with negative margins to prevent double margins on the edges or you can set "gap: 10px" on the container. Sure, the negative margins did get the job done, but at what point do you stop wasting all this time doing everything the more complex way to support a browser almost no one uses and has not been updated since 2013.
Not a counterpoint, but there is an AWS CLI repl/shell out there with suggestions, type-ahead, and etc. I don't use it but I've seen it and it's pretty flash.
Each AWS partition can have its own browser support SLA. China's AWS console has its own [1], although it almost overlaps completely with the "classic" AWS console [2].
For the government/secret partition, I have no clue what their SLA is, but it wouldn't be a leap to assume they may something different.
From an outsider's perspective: AWS has a strong anti-google-tools policy. I appreciate Chrome is listed at all ;-)
One time I tried to have a video call with someone higher up in AWS, and they were unable to join a Google Meet call we have scheduled for that meeting (and only realized at t+2m).
This is every remote meeting in my experience, regardless of technology. The first 5-10 minutes or longer are spent getting everyone online, seeing and hearing each other, resolving echos and feedback, etc.
One of my best video conferencing purchases was a Jabra speaker/microphone that has a ring of LED's that tells me when it's muted. It's not always clear in a UI whether the mic is muted or not "The mute icon is bold white, does that mean it's muted or does that mean I need to click to mute?", but I can tell from the red LED's on my speaker, and it has a mute button on it so I always know how to mute.
Chime tried to be the internal Slack equivalent for an embarrassingly long time. Slack has only been used for a handful of months, and some (frustratingly) have not yet switched over.
Used it for an interview and was pretty disappointed in the video quality. Rather choppy and audio felt really compressed, but that might just be on the far end.
Google Meet, at least after their redesign, works really smoothly for me. We use it for our day-to-day meetings at work with non-government clients. Pre-redesign I really didn't care for Meet though.
Said it is the company policy to not use certain competitor's products, and it was neither time not place to drill down further. How it's enforced, I have no idea.
Don’t think that’s Firefox. And what does it matter, really? Who cares how fast you can get to the wrong place, realize this looks not quite anything like the screen you are thinking of and have to message a coworker to see if they had bookmarked the screen you really want.
I really hope Epic wins that lawsuit against Apple, not because I particularly care about Epic, but because I'd like to see Apple forced to allow alternative web browsers.
Still don't get how it was a problem for Microsoft to "bundle" Internet Explorer, but it's apparently not a problem for Apple to bundle and also actively block any installation of competing browsers.
What Apple offers is Apple's vision of how they want the products they sell to work. You might not agree with Apple, but that's fine because alternative products are available.
Whereas Microsoft was using their operating system monopoly power to mandate how other companies' products could be configured prior to sale to customers.
(This distinction is why—in my opinion—Google is in more trouble against Epic than Apple. Because unlike Apple, Google has strong leverage over how other companies' Android devices can work.)
This title shouldn't be "AWS [admin panels and documentation] Support for Internet Explorer 11 is Ending" or something like that?
The title can create a confusion and read as "Services hosted on AWS will not support IE11" and create some freak outs.
The things of AWS that will not support AWS are:
> AWS Management Console, web-based services such as Amazon Chime or Amazon Honeycode, or other parts of the AWS web site (AWS Documentation, AWS Marketing, AWS Marketplace, or AWS Support).
That they are putting that much effort into it at all is surprising and commendable.