A rare Google UI failure

A Google UI employee contemplating how to make
Larry and Sergei some money

I updated my Google Chrome mostly because I trust Google in terms of UI. In the past they've always released updates that make things faster or easier to reach (while perhaps adding new extra functions).

Why am I so disappointed? Well now when you open a new tab you're confronted with a Google search bar and your most visited sites. This most probably sounds like a good thing. BUT... your tab is in the omnibar which is the same as a Google search if you don't specify a valid URL. So to make use of the default Google search requires you to tab or click into the box.

More annoyingly you can't choose to have your installed apps show instead of a Google search box and an acknowledgement that they track your browsing activity and share that with the American spy agency. So instead of hitting CTRL-T and clicking feedly I have to face NSA surveillance by Google showing me they're tracking me, click on the top left to open apps, then click Feedly. Why? Because for some reason Google thinks it is more important for me to have no option but to use their search engine and that I am incapable of deciding to use applications instead of sites I visit regularly.

Do I support American spy surveillance? Not really. This nation has invaded a foreign nation every decade for the past 60 years. They're the only nation to have ever used nuclear WMD on civilian targets. They routinely hack and spy on neutral foreign nations. I trust the American government a great deal less than I trust Google.

Nonetheless, lets assume for the moment that using an American Internet product is somehow "safe".

You can't choose which search engine is default. Google says "Don't be evil" .... really? As soon as you have a majority browser share you enforce your search engine as a mandatory non-changeable option? And you require me to click into it? Fuck off Larry and Sergei.... you click (since you charge people for clicks ).

And now instead of pressing CTRL-T and hitting an app (like RescueTime or my REST interface or my news browser) I have to move my mouse to the top left? How is this beneficial to me, Larry or Sergei? It really reduces the usefulness of Chrome as a developer browser. What benefit is there for Chrome to load your Google default search into my app tabs when your omnibar works the same? Are you fucking retarded? Don't you see you're stopping me from hitting my apps quickly?

Fork Chromium and get a sensible community version.

Comments

Solving Doctrine - A new entity was found through the relationship

There are so many different problems that people have with the Doctrine error message: exception 'Doctrine\ORM\ORMInvalidArgumentException' with message 'A new entity was found through the relationship 'App\Lib\Domain\Datalayer\UnicodeLookups#lookupStatus' that was not configured to cascade persist operations for entity: Searching through the various online sources was a bit of a nightmare. The best documentation I found was at http://www.krueckeberg.org/ where there were a number of clearly explained examples of various associations. More useful information about association ownership was in the Doctrine manual , but I found a more succinct explanation in the answer to this question on StackOverflow . Now I understood better about associations and ownership and was able to identify exactly what sort I was using and the syntax that was required. I was implementing a uni-directional many to one relationship, which is supposedly one of the most simpl...

Grokking PHP monolog context into Elastic

An indexed and searchable centralized log is one of those tools that once you've had it you'll wonder how you managed without it. I've experienced a couple of advantages to using a central log - debugging, monitoring performance, and catching unknown problems. Debugging Debugging becomes easier because instead of poking around grepping text logs on servers you're able to use a GUI to contrast and compare values between different time ranges. A ticket will often include sparse information about the problem and observed error, but if you know more or less when a problem occurred then you can check the logs of all your systems at that time. Problem behaviour in your application can occur as a result of the services you depend on. A database fault will produce errors in your application, for example. If you log your database errors and your application errors in the same central platform then it's much more convenient to compare behaviour between...

Translating a bit of the idea behind domain driven design into code architecture

I've often participated in arguments discussions about whether thin models or thin controllers should be preferred. The wisdom of a thin controller is that if you need to test your controller in isolation then you need to stub the dependencies of your request and response. It also violates the single responsibility principal because the controller could have multiple reasons to change. Seemingly, the alternative is to settle on having fat models. This results in having domain logic right next to your persistence logic. If you ever want to change your persistence layer you're going to be in for a painful time. That's a bit of a cargo cult argument because honestly who does that, but it's also a violation of the single responsibility principal. One way to decouple your domain logic from both persistence and controller is to use the "repository pattern". Here we encapsulate domain logic into a data service. This layer deals exclusively with imple...

Adventures in IT

Search This Blog