happymellon

The "AI fears" are fears that AI is going to gut Google.

I think that Google did it to themselves by making their search so bad that it encouraged everyone to switch.

They would have had a longer runway as the folks who stuck to Internet Explorer, the folks who stuck with AOL, and all the other businesses that had better options but rode out that friction to switch could have kept them solvent.

Instead, they spent far too much time making Google search difficult to use or to find anything and pushed them off the platform.

NT was criminally underrated by Microsoft.

Far too many features required 3rd party tooling to access, or were buried within menus of menus. Then were slowly either duplicated or replaced with half baked solutions.

I have mixed feelings about this.

Sure it has replaced Google for a lot of people. But was that driven more by Google breaking search and actively ranking down good results and putting blocks in the way of seeing even the bad results?

Google had (have?) people using their service out of habit but built a hostile enough environment. We have this "contradiction" where non-tech folks are supposed to be difficult to move off "what they know" yet here we are where they are using ChatGPT to search and be a doctor.

Having a special Gemini button everywhere is "a new feature", but it isn't a useful feature, so the productivity needle doesn't budge.

Wasn't that just a literal copy of Photopea?

Doesn't AWS stack rank? So having good ratings has a low relationship with your delivery.

The citations are from companies passing the blame so they don't look bad.

I have yet to see a big corp using AI to reduce work and therefore not need the employees. It's an endless pit of work generation!

However it's now an excuse to cut head count because of executive poor decisions, and a poor economy due to having bad leadership.

I don't use the page up/down much, but I do use the arrow keys so the split up/down is a pain.

> some say they are not reliable.

The problem here is that too many people have a vested interest to be unreliable, so we are never sure one way or another.

IIRC, my Blackberry had a dial on the side, in addition to the keyboard and roller ball.

I've been on Emby for a long time, just waiting for them to make the system abrasive enough to switch to Jellyfin.

Breaking the usability of the Android TV app and requiring us to switch to the mobile app on the TV was pretty bad. But since the last update I get delays of "connecting to the server". I think we are there now, I just need a free weekend to get everything set up.

My documentation for events from 2018 at this point are limited, and trying to go back through the lists of events demonstrates the limited reporting for some things deemed "non-critical" such as the early 2019 connectivity issues with EU West 2 when the London fibres were cut and services such as Workspaces experienced an outage.

I will do better at saving exact details for internet strangers in future.

> I respectfully believe you are mistaken about cause and effect

You are allowed to be wrong.

Just because it is your priority, doesn't make it mine.

The current situation I have is that I have 5 people demanding that I have their stuff as a priority, and they will schedule meetings to tell me such.

If I'm in 5 hours of status update and demo meetings every day how much actual work is going to get completed?

While what you say is generally true for 1, I wholly disagree that it is always customers that do the coupling.

One more than one occasion there are AWS URLs, including redirects inside the console, that include US East 1 in the URL that were only spotted during an outage. Manually changing it to an different region allowed us to get around it but to wholely blame customers when you don't know the context is bad form.

But there are also always exceptions. I've seen US East 1 outages cause autoscaling issues in other regions including failing to start new EC2s. A real problem if things have scaled down overnight.