diff options
| author | neodarz <neodarz@neodarz.net> | 2017-04-28 19:05:18 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2017-04-28 19:05:18 +0200 |
| commit | cdabe7a75ea14f14ca8d4cd3bf9ac36cb1817531 (patch) | |
| tree | a3a9557d77f376394bb8e49fc48dcdef556ecb38 /build/blog/2015-06-10-chrome-disappointment-the-shabby-and-boring-old-bookmark-system-from-stone-age-strikes-back.html | |
| parent | d08bc695f396f8e2d7fc96de7efe61818c7c9a15 (diff) | |
| download | my_new_personal_website-cdabe7a75ea14f14ca8d4cd3bf9ac36cb1817531.tar.xz my_new_personal_website-cdabe7a75ea14f14ca8d4cd3bf9ac36cb1817531.zip | |
Delete some usless file
Diffstat (limited to 'build/blog/2015-06-10-chrome-disappointment-the-shabby-and-boring-old-bookmark-system-from-stone-age-strikes-back.html')
| -rw-r--r-- | build/blog/2015-06-10-chrome-disappointment-the-shabby-and-boring-old-bookmark-system-from-stone-age-strikes-back.html | 80 |
1 files changed, 0 insertions, 80 deletions
diff --git a/build/blog/2015-06-10-chrome-disappointment-the-shabby-and-boring-old-bookmark-system-from-stone-age-strikes-back.html b/build/blog/2015-06-10-chrome-disappointment-the-shabby-and-boring-old-bookmark-system-from-stone-age-strikes-back.html deleted file mode 100644 index b39f282d..00000000 --- a/build/blog/2015-06-10-chrome-disappointment-the-shabby-and-boring-old-bookmark-system-from-stone-age-strikes-back.html +++ /dev/null @@ -1,80 +0,0 @@ -<!DOCTYPE html> -<html> -<head> -<meta charset="utf-8"/> -<meta content="pandoc" name="generator"/> -<meta content="Zhiming Wang" name="author"/> -<meta content="2015-06-10T23:17:05-07:00" name="date"/> -<title>Chrome disappointment: the shabby and boring old bookmark system from Stone Age strikes back</title> -<link href="/img/apple-touch-icon-152.png" rel="apple-touch-icon-precomposed"/> -<meta content="#FFFFFF" name="msapplication-TileColor"/> -<meta content="/img/favicon-144.png" name="msapplication-TileImage"/> -<meta content="width=device-width, initial-scale=1" name="viewport"/> -<link href="/css/normalize.min.css" media="all" rel="stylesheet" type="text/css"/> -<link href="/css/theme.css" media="all" rel="stylesheet" type="text/css"/> -</head> -<body> -<div id="archival-notice">This blog has been archived.<br/>Visit my home page at <a href="https://zhimingwang.org">zhimingwang.org</a>.</div> -<nav class="nav"> -<a class="nav-icon" href="/" title="Home"><!--blog icon--></a> -<a class="nav-title" href="/"><!--blog title--></a> -<a class="nav-author" href="https://github.com/zmwangx" target="_blank"><!--blog author--></a> -</nav> -<article class="content"> -<header class="article-header"> -<h1 class="article-title">Chrome disappointment: the shabby and boring old bookmark system from Stone Age strikes back</h1> -<div class="article-metadata"> -<time class="article-timestamp" datetime="2015-06-10T23:17:05-07:00">June 10, 2015</time> -</div> -</header> -<p>I just restarted my machine (in the process of planning a fresh OS re-install), and something in Chrome's UI immediately felt wrong. After a few moments I realized it was the star button (bookmark button) in the far right of the omnibox giving me the uneasy feeling — the old bookmark system is back. Broadcasting from stable channel, build 43.0.2357.124 on OS X.</p> -<div class="figure"> -<a href="/img/20150610-omnibox-with-aged-star.png" target="_blank"><img alt="What caught my immediate attention." src="/img/20150610-omnibox-with-aged-star.png"/></a> -<p class="caption">What caught my immediate attention.</p> -</div> -<div class="figure"> -<a href="/img/20150610-old-bookmark-manager.png" target="_blank"><img alt="The heart sinking feeling when I saw this again." src="/img/20150610-old-bookmark-manager.png"/></a> -<p class="caption">The heart sinking feeling when I saw this again.</p> -</div> -<p>I went to flags and made sure "Enable the new bookmark app system" wasn't tempered with. It wasn't. Anyway, I changed it to "Enabled" and restarted Chrome. No go, still the old crap. So I Googled my way to <a href="https://productforums.google.com/forum/#!topic/chrome/mhIX5LB23As">the announcement</a>:</p> -<blockquote> -<p>Hi Everyone,</p> -<p>Our team is committed to improving Chrome’s bookmarks experience, but for the time being, we’ve decided to bring back the previous version. Our team will continue to explore other ways to improve the bookmarks experience. You’ll see the previous version of the bookmarks manager return to your Chrome browser shortly.</p> -<p>For those of you who enjoyed using the new bookmarks manager, you can still keep the new experience by downloading the Bookmarks Manager extension from the Chrome Web Store.</p> -<p>We appreciate hearing all of your thoughtful feedback. Feel free to leave us with any additional comments here in this thread.</p> -<p>Best,<br/> The Chrome team</p> -</blockquote> -<p>This is just very disappointing. My default browser changes a lot, but I've been tagging along with Opera for <a href="/blog/2014-12-14-the-google-chrome-comic-a-classic.html">almost the entirety of 2014</a>, so I've long been used to visual bookmarks. And honestly, it never felt weird or anything; I saw it as an improvement the first time I was introduced to the concept.</p> -<p>I know, there's always a demographic that would fiercely resist any change; they would reject anything new at a glance (or after using for a second) and start moaning right away, disregarding all the new benefits here and there. There's also another demographic who not only have no taste in design at all, but would also actively seek to tear down any visual enhancement — 90s visual is enough for them for life, any more is unsolicited and insulting. When these two demographics meet<a class="footnoteRef" href="#fn1" id="fnref1"><sup>1</sup></a> and somehow make the developers retreat, the outcome is simple and sad: <em>we can never have nice things.</em></p> -<p>I'm not saying I'm 100% satisfied with Chrome's visual bookmarks. In fact far from that. For one thing, Google is really pretty bad at visual design.<a class="footnoteRef" href="#fn2" id="fnref2"><sup>2</sup></a> Also, not being able to adjust tile size or toggle a list view is rather lame. However, whatever problems there are, the new system is at least 200% better than the old one (just look that the screenshots!).<a class="footnoteRef" href="#fn3" id="fnref3"><sup>3</sup></a> <em>The team should focus on making the new system better,</em> such as implementing the features I mentioned above, rather than throw it into the trash can and resurrect the old system from Stone Age.</p> -<p>I know, throwing things away is part of Google's philosophy. They usually toy with a wide range of ideas and discard the ones that people don't buy into. Not that I whole-heartedly agree with strategy, but to advance technology there has to be some Brownian motion out there, and Google usually listens to the market, which is fine. In this case, however, there's really nothing innovative about visual bookmarks, and I can't see how the new system could harm market share or anything either. In fact, it could only help, since except the anti-design demographic, who would choose the aged and boring layout from the old system?<a class="footnoteRef" href="#fn4" id="fnref4"><sup>4</sup></a> Moreover, people tend to ignore the fact that the new system is also functionally superior — it offers to</p> -<ul> -<li>Learn and suggest folder for a new bookmark (which is often accurate);</li> -<li>Create auto folders based on site or keyword;</li> -<li>Allow arbitrary text data to be stored with each entry (e.g., a page-specific non-sensitive access code);</li> -<li>One tap pop from assigned folder;</li> -</ul> -<p>and more. Those that resist everything new are simply blind. The team claim that they are listening to "thoughtful feedback"; well, can they tell "thoughtful feedback" from blind suspicion and denial about everything? And they do realize that feedback is heavily biased, as someone with positive experience (unless he is a hardcore fan) is unlikely to leave them a thank you message? I think it's pretty clear that the majority of users won't care either way<a class="footnoteRef" href="#fn5" id="fnref5"><sup>5</sup></a>; the majority of the rest was happy with the change; and the rest, comprising only a diminishingly small percentage, is what kept us from having nice things.</p> -<p>Even if one agrees with nothing from the last paragraph, one has to realize that randomly dropping a big change this way is just irresponsible.<a class="footnoteRef" href="#fn6" id="fnref6"><sup>6</sup></a> There were hurt feelings when the change was first introduced (not that I care about them), so don't change mind again three weeks later, hurting yet another camp. Whether it was a change for the good or the bad, admit it was done (admit you screwed up if you did) and focus on improving it.</p> -<p>End of rant, off to install the <a href="https://chrome.google.com/webstore/detail/bookmark-manager/gmlllbghnfkpflemihljekbapjopfjik">Bookmark Manager extension</a>.</p> -<div class="footnotes"> -<hr/> -<ol> -<li id="fn1"><p>There's actually a pretty big overlap between these two demographics.<a class="footnotes-backlink" href="#fnref1">↩︎</a></p></li> -<li id="fn2"><p>The giant blue search bar at the top is especially ridiculous.<a class="footnotes-backlink" href="#fnref2">↩︎</a></p></li> -<li id="fn3"><p>I didn't bother to switch to an earlier build just to take a screenshot of the visual system, so unfortunately there's no comparison here. But anyone who's been there knows what I'm saying.<a class="footnotes-backlink" href="#fnref3">↩︎</a></p></li> -<li id="fn4"><p>Unless one has hundreds of bookmarks in a single folder (which probably means some cleanup or refactoring is long overdue), the old layout is unlikely to be easier on the eyes or anything.<a class="footnotes-backlink" href="#fnref4">↩︎</a></p></li> -<li id="fn5"><p>Well, grandmas have one more thing to learn, I guess...<a class="footnotes-backlink" href="#fnref5">↩︎</a></p></li> -<li id="fn6"><p>In other news, Google dropped YouTube collections two weeks ago (<a href="https://support.google.com/youtube/answer/6233832?hl=en">May 26, 2015</a>), causing another round of agony. Also, subscriptions were all over the place once more, just like Google's project landscape.<a class="footnotes-backlink" href="#fnref6">↩︎</a></p></li> -</ol> -</div> -</article> -<hr class="content-separator"/> -<footer class="footer"> -<span class="rfooter"> -<a class="rss-icon" href="/rss.xml" target="_blank" title="RSS feed"><!--RSS feed icon--></a><a class="atom-icon" href="/atom.xml" target="_blank" title="Atom feed"><!--Atom feed icon--></a><a class="cc-icon" href="https://creativecommons.org/licenses/by/4.0/" target="_blank" title="Released under the Creative Commons Attribution 4.0 International license."><!--CC icon--></a> -<a href="https://github.com/zmwangx" target="_blank">Zhiming Wang</a> -</span> -</footer> -</body> -</html> |