<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shogo Sensui on Medium]]></title>
        <description><![CDATA[Stories by Shogo Sensui on Medium]]></description>
        <link>https://medium.com/@1000ch?source=rss-1edb20469358------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CdQc7a512w2wpdPuGtTKIA.jpeg</url>
            <title>Stories by Shogo Sensui on Medium</title>
            <link>https://medium.com/@1000ch?source=rss-1edb20469358------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:56:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@1000ch/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Visualize the correlation between web performance and product KPI]]></title>
            <link>https://medium.com/@1000ch/visualize-web-performance-and-product-kpi-b1feca635e37?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1feca635e37</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 01:17:11 GMT</pubDate>
            <atom:updated>2017-11-10T02:46:41.162Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, I introduce my activity to visualize web performance and product KPI using some metrics such as Speed Index, First Paint, First Contentful Paint.</p><h3>Traditional Web Performance Metrics</h3><p>In the past, I think that the value of DOMContendLoaded event or load event was treated as a good metric of Web page performance in many cases. However, it is no longer an appropriate indicator to measure the performance of Web pages that are getting more and more complicated in architecture.</p><h4>DOMContentLoaded — DOM construction is completed</h4><p>The DOMContentLoaded event represents completion of construction of the DOM tree, but it does not guarantee completion of subresource loading occurring while evaluating the HTML document. From here, the browser loads the CSS files, synthesizes the DOM tree and the CSSOM tree and finally draws the page, so it does not indicate the display state of the page content that might be related to the user’s experience.</p><h4>Load — All resources are loaded</h4><p>The load event means loading of CSS files, JavaScript files, subresources such as images, and so on. The display of the content is almost finished when the load event occurs, but in reality most of the content is often displayed before the load event occurs.</p><h3>Modern Web Performance Metrics</h3><p>New metrics are introduced in <a href="https://developers.google.com/web/updates/2017/06/user-centric-performance-metrics">Leveraging the Performance Metrics that Most Affect User Experience</a> focusing on user experience in these days. Some of them are being defined as Web Standards.</p><h4>First Paint and First Contentful Paint — Anything displayed</h4><p>Both First Paint and First Contentful Paint are indicators to evaluate how quickly the page starts to display after the browser navigates. First Paint refers to the timing when something is displayed, and First Contentful Paint refers to the timing when some content (text, image, etc.) is displayed. Although neither may be a numerical value directly linked to the user experience, it is useful to evaluate the performance of the web application, suggesting the status of loading subresources and the state of critical rendering paths.</p><p>The timing defined for First Paint and First Contentful Paint is clear and standardization is being promoted as an index of Paint Timing API. <a href="https://blog.chromium.org/2017/06/chrome-60-beta-paint-timing-api-css.html">The Paint Timing API is already supported by Chrome 60</a> and can be measured.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*Jh0JcHkIaH8gPXtek3AxUg.png" /><figcaption>First Paint and First Contentful Paint</figcaption></figure><p>We can use them with the <a href="https://blog.chromium.org/2017/06/chrome-60-beta-paint-timing-api-css.html">Paint Timing API introduced in Chrome 60</a>.</p><h4>First Meaningful Paint — Anything meaningful for user displayed</h4><p>First Meaningful Paint refers to the timing when a meaningful display is made to the user. It is equal to whether the user is able to provide the expected content, so shortening this can be expected to have a positive effect on the product as it is.</p><p>However, it is difficult to standardize unlike First Paint and First Contentful Paint, because “depends on the user’s meaning” depends on the nature of the product and how it is implemented. To measure First Meaningful Paint, you will define the timing according to the nature of the product and calculate it using the <a href="https://www.html5rocks.com/ja/tutorials/webperformance/usertiming/">User Timing API</a> etc.</p><h4>Speed Index — Score of drawing amount in first view</h4><p><a href="https://sites.google.com/a/webpagetest.org/docs/using-webpagetest/metrics/speed-index">Speed ​​Index</a> is a score obtained by summing the proportion of unrendered content with respect to the elapsed time from the start of navigation in the visible region, and it is an index introduced in the performance measurement tool called <a href="https://www.webpagetest.org/">WebPagetest</a> developed by Google.</p><p>Assume that there is a page A and a page B that display the same content, and the timing of page load completion (generation of load event) is the same for both pages. If, <strong>on page A, 93% of the visible region is displayed after one second</strong>, whereas for <strong>page B only 18% of the visible region is displayed after one second</strong>, it is clear that page A has excellent performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*4ojwWi-yGgDYKc5GdiF0Pg.png" /></figure><p>In order to compare them, try graphing with the elapsed time on the X axis and the drawing amount on the Y axis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*kQs-8nxWweRABaB-Pb_NHA.png" /><figcaption>Visually Complete Progress of “A” and “B”</figcaption></figure><p>Although the completeness with respect to the elapsed time can be set as the drawing progress rate, there is a disadvantage that the value becomes unlimitedly large as the loading time until the completeness reaches 100% is prolonged. Therefore, if you calculate the area above the graph with respect to the elapsed time, the smaller it is, the better it is (more is drawn in a short time from the start). This is the Speed ​​Index.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*Rg4o2TrW50iWDlCN4ieObg.png" /><figcaption>Remaining to be rendered for “A” and “B”</figcaption></figure><p>WebPagetest uses the video capture when the test agent accesses the measurement page to calculate the Speed Index using the degree of matching between the frame at completion of loading of each loaded frame as the completeness. <a href="https://speedcurve.com/">SpeedCurve</a> which uses WebPagetest as the backend uses the same calculation method.</p><p>There is another way to calculate from the drawing event of the browser (Layout, Paint). By executing <a href="https://github.com/WPO-Foundation/RUM-SpeedIndex">RUM-SpeedIndex</a> which is calculated by using the Resource Timing API, it can measure even on the browser, and <a href="https://developers.google.com/web/tools/lighthouse/?hl=ja">Lighthouse</a> which is bundled with DevTools also uses a tool called <a href="https://github.com/paulirish/speedline">speedline</a> to measure it.</p><p>For this time, I decided to use Speed Index as a comprehensive performance evaluation index of First View related to user experience, and to measure with each Web product. Although it is not being developed as a Web standard, introduction is easy because there are already measurement methods such as WebPagetest, <a href="https://speedcurve.com/">SpeedCurve</a>, Lighthouse, RUM-SpeedIndex.</p><h3>Synthetic Monitoring and Real User Monitoring</h3><p>There are already a lot of ways to measure performance as introduced. They are largely categorized as Synthetic Monitoring and Real User Monitoring.</p><h4>Synthetic Monitoring</h4><p>In synthetic monitoring, we measure the performance when accessing the target URL from a controlled environment. As browser, server location, network speed, etc. are fixed, variance per measurement is small, and it is suitable for detecting application bottleneck. The previously mentioned WebPagetest and Synthetic of SpeedCurve etc belong to synthetic monitoring, and the Web product of our media business has continued the performance measurement by SpeedCurve. Following articles are written in Japanese :)</p><ul><li><a href="https://developers.cyberagent.co.jp/blog/archives/636/">アメブロ2016 ~ React/ReduxでつくるIsomorphic web app ~</a></li><li><a href="https://developers.cyberagent.co.jp/blog/archives/6057/">FRESH! Web パフォーマンス改善 〜クライアントサイド編〜</a></li><li><a href="https://developers.cyberagent.co.jp/blog/archives/8441/">横断組織の力を借りてプロダクトをより良くするには？電子書籍サービス「読書のお時間です」パフォーマンス改善の進め方</a></li></ul><p>As the environment for specifying the bottleneck of the application is in place, it is becoming important to detect regressions such as loading speed unintentionally decreasing in the function release, and how much effect is obtained when tuning the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n9cjpqSe38gW6aO0aQ9K4g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/45FJgZMXCK8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Joey Kyber</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Real User Monitoring</h4><p>With synthetic monitoring, we can improve application performance with confidence, but cannot measure how performance is affecting the user experience. In a real user monitoring, performance is measured in real user environment where both device performance and network environment varies, so we can measure performance effect on the user experience.</p><h3>Aggregation of real users’ SpeedIndex for each product</h3><p>The purpose of using real user monitoring is to measure what kind of performance the real user is experiencing and to know how it correlates with the project indicator. For this project, we introduced a measurement script of RUM-SpeedIndex for each project, we decided to send the calculated Speed Index to Google Analytics and gather data.</p><p>There are a couple of reasons why I used Google Analytics as your aggregate destination.</p><ul><li>Since the function to measure the bounce rate and the page view per session is originally provided, you can see the correlation with them by sending the Speed Index as custom data</li><li>Since we have already installed Google Analytics on most projects, the barriers to measurement are small. Simply load RUM-SpeedIndex and send the execution result to Google Analytics to complete</li><li>Many people are familiar with tools. I also have a full-time marketing staff for the project so I can ask for detailed analysis</li><li>Data can be acquired through add-on, so you can freely format and visualize using Google spreadsheet etc.</li></ul><p>After the real user’s Speed Index is aggregated for each project, we can see how it correlates with the bounce rate and page view for each session. When preparing and introducing, we received a lot of cooperation from every project (<a href="https://seleck.cc/1053">especially Suma-san, web analyst</a>) 🙏</p><h3>Correlation between real user Speed Index and bounce rate and pageview number per session</h3><p>The following graph shows the results of Project A as a graph. The horizontal axis is the Speed Index of the actual user environment calculated with RUM — SpeedIndex. The blue line shows the distribution of the number of users, and it can be seen that the ratio of users with the Speed Index near 1000 is high (The cases where the Speed Index is 0 are also graphed, but ignored as outliers ). In addition, the number of users has been sampled, it does not accurately represent the actual number of users.</p><p>The red line is the bounce rate (Bounce Rate, top graph) and the page view per session (PageViews / Session, bottom graph).</p><p>First, looking at the bounce rate, the better the score of the Speed Index (the smaller the value) the lower the bounce rate tends to be. In addition, it is flat with the Speed Index = 1500 as a boundary, and on the mobile Web of Project A, you can see that there is no change in bounce rate when it is more than a certain delay.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*tqySoKo6l6qybwnuXcgICQ.png" /><figcaption>Bounce Rate distribution map of Project A</figcaption></figure><p>Next, I will look at the page view per session. As the score of the Speed Index gets better, the number of page views has also increased, and it has remained almost flat from the vicinity of Speed Index = 1500.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*_wYYEHMK1xferznMWC8pOA.png" /><figcaption>PV/Session distribution map of Project A</figcaption></figure><p>From these two points you can see that the better the score of the Speed Index, the better the performance, the lower the bounce rate and the more page views per session. This is the result of a certain day of Project A, which basically changes like this without being influenced by release of functions, although there is some increase or decrease depending on the day. From this we can confirm that the user’s behavior depends on the nature of the product, but the performance will affect the KPI of the product.</p><h3>Speed Index and Product KPI, Milestone in Project</h3><p>I was convinced that the performance is directly linked to the product KPI, so I will set performance objectives and improvements as project objectives.</p><p>As a project, since it is only necessary to increase the ratio of users who have good performance when accessing, the value of the Speed Index separating the top 50% and bottom 50% of the users with good performance is used as a threshold value, and thereafter it is better than the Speed Index We will follow the ratio of users to users experiencing bad performance in days. This should increase the ratio of users with better performance (better than the threshold of the Speed Index you decide) when performance is improved.</p><p>After improving the monitoring environment, we improved the performance in Project B and the result was as follows. We released the tuning on the night of July 20th.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*4PjgjSR0fqQxQE1U1cBiPA.png" /><figcaption>Daily Active Users of Project B</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*zJyvT3DJEijYCEg61zMqiw.png" /><figcaption>PV/Session and Bounce Rate of Project B</figcaption></figure><p>The DAU that can be read from the above graph seems to be on a slightly increasing trend although it is a usual trend as increasing trends on Saturdays and Sundays. In the graph below, we plot the page view per session (PV number per visit in the figure) and the bounce rate in addition to the index set in Project B (gray fill in figure), but in the graph below, You can see that the number of page views has improved by about 30% to 40%.</p><p>While performance and accessibility are very important for Web products, their effect is difficult to see and tend to be postponed. However, if you can visualize the degree of influence on KPI and show that the quality improvement of the product is a merit to the business, you can begin with prioritizing.</p><h3>Future of Web performance initiatives</h3><p>By constantly measuring and visualizing performance and visualizing how it correlates with the product’s KPI, we have made a foundation on which engineers can relax and improve their performance.</p><p>In the future, we will analyze by adding the most important KPI set for each project (whether it is purchases at an EC site or whether it is purchases of movie media, etc.), analyze and add First Paint as a performance indicator We also plan to analyze how we correlate with product KPI by adding First Contentful Paint and other metrics.</p><p>I would be pleased if this effort for performance is helpful to further improve the quality of your web product. Thank you for reading.</p><h3>Related links</h3><ul><li><a href="https://developers.google.com/web/updates/2017/06/user-centric-performance-metrics">Leveraging the Performance Metrics that Most Affect User Experience | Web | Google Developers</a></li><li><a href="https://blog.chromium.org/2017/06/chrome-60-beta-paint-timing-api-css.html">Chromium Blog: Chrome 60 Beta: Paint Timing API, CSS font-display, and Credential Management API improvements</a></li><li><a href="https://sites.google.com/a/webpagetest.org/docs/using-webpagetest/metrics/speed-index">Speed Index — WebPagetest Documentation</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1feca635e37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Component including Fundamental Image Features]]></title>
            <link>https://medium.com/freshdevelopers/react-component-including-fundamental-image-features-c10a0636f198?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/c10a0636f198</guid>
            <category><![CDATA[image]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Tue, 15 Aug 2017 16:06:42 GMT</pubDate>
            <atom:updated>2020-09-08T15:37:30.183Z</atom:updated>
            <content:encoded><![CDATA[<p>On web development using React, we often create &lt;Image&gt; component. That is stateless and including basic features such as lazy-load, accessibility, and some others.</p><p>Today, I try to implement such &lt;Image&gt; component using <a href="https://github.com/openfresh/super-image">openfresh/super-image</a> and <a href="https://github.com/openfresh/viewport-observer">openfresh/viewport-observer</a> which are React Component libraries by FRESH! developers.</p><h3>SuperImage — provide basic features for image</h3><p>&lt;SuperImage&gt; provides basic features for an image by wrapping &lt;img&gt;.</p><ul><li>Render images with object-fit and its fallback using background-size</li><li>Provide alt with empty string automatically for accessibility</li></ul><p>object-fit is a quite convenient property, but <a href="http://caniuse.com/#feat=object-fit">some browsers don’t support it yet</a>. So when you have to support browsers widely, &lt;SuperImage&gt; will be a great component.</p><pre>import SuperImage from &#39;super-image&#39;;</pre><pre>// ...</pre><pre>&lt;SuperImage<br>  src=&quot;image.jpg&quot;<br>  width=&quot;160&quot;<br>  height=&quot;90&quot;<br>  alt=&quot;super-image&quot;<br>  fit=&quot;contain&quot;<br>/&gt;</pre><p>When using object-fit with fallback, &lt;SuperImage&gt; will render images on &lt;div&gt; ‘s background. And then, it creates aria-labelattribute when alt property is specified with assuming &lt;img&gt; .</p><p>Further ideas: support convenient properties wrapping &lt;picture&gt; elements or srcset attributes for responsive image rendering.</p><h3>ViewportObserver — observe changes of a target element intersection</h3><p>&lt;ViewportObserver&gt; observe changes of a target element intersection using <a href="https://github.com/WICG/IntersectionObserver">IntersectionObserver</a> with nicer interface for React.</p><pre>import ViewportObserver from &#39;viewport-observer&#39;;</pre><pre>// ...</pre><pre>&lt;ViewportObserver<br>  onChange={() =&gt; console.log(&#39;onChange&#39;)}<br>  onEnter={() =&gt; console.log(&#39;onEnter&#39;)}<br>  onLeave={() =&gt; console.log(&#39;onLeave&#39;)}&gt;<br>  &lt;div&gt;Target Element&lt;/div&gt;<br>&lt;/ViewportObserver&gt;</pre><p>As you know, &lt;ViewportObserver&gt; can be used for general-purpose not only for image lazy-load. This is very useful.</p><p>IntersectionObserver is supported by Chrome, Firefox, Opera, Edge now. So you probably need to polyfill it for Safari with <a href="http://IntersectionObserver polyfill">WICG/IntersectionObserver polyfill</a>. Because the feature may be needed especially for the Mobile Web!</p><h3>Image Component base implementation</h3><p>Now combine them to create &lt;Image&gt; component which has fundamental features: lazy-loading, easily layout using object-fit , alt fallback for accessibility.</p><p>DUMMY_IMAGE is a base64 encoded string of 1px square GIF image set as default not to load an original image until intersected into a viewport.</p><p>ROOT_MARGIN is a <a href="https://developer.mozilla.org/docs/Web/API/DOMString">DOMString</a> passed to IntersectionObserver constructor option to add bounding box to the root when calculating intersections.</p><pre>// You probably might need to polyfill<br>import &#39;intersection-observer&#39;;<br>import &#39;object.assign&#39;;</pre><pre>import React from &#39;react&#39;;<br>import PropTypes from &#39;prop-types&#39;;<br>import SuperImage from &#39;super-image&#39;;<br>import ViewportObserver from &#39;viewport-observer&#39;;</pre><pre>const DUMMY_IMAGE = &#39;data:image/gif;base64,R0lGODlhAQABAIAAAP//////zCH5BAEHAAAALAAAAAABAAEAAAICRAEAOw==&#39;;<br>const ROOT_MARGIN = &#39;200px 0&#39;;</pre><pre>export default class Image extends React.Component {<br>  static propTypes = {<br>    src: PropTypes.string.isRequired,<br>    fit: PropTypes.oneOf([&#39;contain&#39;, &#39;cover&#39;]),<br>    width: PropTypes.string,<br>    height: PropTypes.string<br>  };</pre><pre>  state = {<br>    src: DUMMY_IMAGE<br>  };</pre><pre>  constructor(props) {<br>    super(props);</pre><pre>    this.onEnter = this.onEnter.bind(this);<br>  }</pre><pre>  onEnter() {<br>    this.setState({<br>      src: this.props.src<br>    });<br>  } </pre><pre>  render() {<br>    return (<br>      &lt;ViewportObserver<br>        rootMargin={ROOT_MARGIN}<br>        onEnter={this.onEnter}&gt;<br>        &lt;SuperImage<br>          src={this.state.src}<br>          fit={this.props.fit}<br>          width={this.props.width}<br>          height={this.props.height}<br>        /&gt;<br>      &lt;/ViewportObserver&gt;<br>    );<br>  }<br>}</pre><p>For more detail usage, see READMEs of each repository, <a href="https://github.com/openfresh/super-image">openfresh/super-image</a>, and <a href="https://github.com/openfresh/viewport-observer">openfresh/viewport-observer</a>.</p><p>If you any idea about base implementation for &lt;Image&gt;, feel free to comment here☺️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c10a0636f198" width="1" height="1" alt=""><hr><p><a href="https://medium.com/freshdevelopers/react-component-including-fundamental-image-features-c10a0636f198">React Component including Fundamental Image Features</a> was originally published in <a href="https://medium.com/freshdevelopers">FRESH LIVE Developers Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Whale — Unofficial Trello app]]></title>
            <link>https://medium.com/@1000ch/whale-unofficial-trello-client-b520c1734e8f?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/b520c1734e8f</guid>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[trello]]></category>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Fri, 17 Mar 2017 13:22:21 GMT</pubDate>
            <atom:updated>2017-08-08T16:58:29.463Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I’d like to introduce <a href="https://github.com/1000ch/whale">Whale</a> app that is <a href="https://trello.com/">Trello</a> client for macOS, Windows and Linux.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7uqNi62IBd55M8Z6IhpVlA.png" /></figure><h3>Install</h3><h4>Download from GitHub repository</h4><p>Download a Whale archive for your OS from the <a href="https://github.com/1000ch/whale/releases">release page of GitHub repository</a>, and unzip it. If you are using macOS, move it into /Applications.</p><h4>Install via Homebrew Cask</h4><p>You can also install Whale via <a href="https://caskroom.github.io/">Homebrew Cask</a>. Homebrew Cask is bundled with Homebrew itself, so you can use it if you have already installed Homebrew.</p><pre>$ brew cask install whale</pre><h3>Update</h3><p>Sometimes newer version of Whale will be published to update bundled Chromium, add some features, and fix some problems. But you don’t have to update manually if you are using Whale on macOS, because it update automatically itself if update exists.</p><h3>Usage</h3><p>Just click or double-click Whale app icon to start, then you have to login to Trello for the first time only.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*4F9_zv6rFvpiD7GlW8Z16A.png" /></figure><h3>Motivation</h3><p>Sometime you don’t want to open Trello on a browser. To avoid to open too many browser tabs, not to manage TODOs on browsers, to switch context with ⌘ + Tab… Whale could be an alternative solution to use Trello without these problems.</p><h3>Links</h3><ul><li><a href="https://github.com/1000ch/whale">1000ch/whale: Unofficial Trello app</a>: Open sourced on GitHub.</li><li><a href="https://www.producthunt.com/posts/whale-5">Whale — Product Hunt</a>: Feel free to upvote or send a feedback.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b520c1734e8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Markdown Apps for Mac]]></title>
            <link>https://medium.com/@1000ch/markdown-apps-for-mac-91319404500a?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/91319404500a</guid>
            <category><![CDATA[markdown]]></category>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 03:15:38 GMT</pubDate>
            <atom:updated>2016-01-29T14:24:40.134Z</atom:updated>
            <content:encoded><![CDATA[<p>I write anything using Markdown Syntax frequently. There are some online Markdown editor such as <a href="https://gist.github.com/">Gist</a>, <a href="http://dillinger.io/">Dillinger</a> and w<a href="https://wri.pe/">ri.pe</a>, but in my own case I write with some Application for Markdown on my Mac. I would like to introduce them.</p><h3><a href="https://ia.net/writer/mac/">iA Writer</a></h3><p>In 10 September of last year, <a href="https://ia.net/writer/updates/ia-writer-3">Version 3 has released</a>. This release includes 2 features using swipe. Swipe from the left to show the document library, swipe from the right to reveal an HTML preview of editing Markdown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*R8RErWYMYP1XvCEKfO1YgA.png" /></figure><h3><a href="http://macdown.uranusjr.com/">MacDown</a></h3><p>MacDown is open-sourced Markdown Editor for Mac. As you can see, it it 2 panes structure. Left pane is input area, right pane is for live preview. You can configure Markdown auto-formatting mode, Editor appearance (base font, color theme, line spacing…), and Rendering appearance (CSS to apply).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Gy8N61vNWl7vkU5QSkjZgQ.png" /></figure><h3><a href="http://usewhiskey.com/">Whiskey</a></h3><p>Whiskey is being developed by <a href="http://nothingmagical.com/">Nothing Magical</a> project which is just a one man show of <a href="https://medium.com/u/3e65166c6061">Sam Soffes</a>. It does not include so many features, simple and just works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*uX2ZAWygr1VDiQKmbJidyQ.png" /></figure><h3><a href="http://caret.io/">Caret</a></h3><p>Caret is beautiful App made by <a href="https://medium.com/u/5f565edc8ad1">Antonio Stoilkov</a> and <a href="https://medium.com/u/e0a428879fe3">Emanuil Rusev</a>. It has useful functions such as Code Highlighting, Auto-Completion, Context Commands, Preview, File Navigation, and others.</p><p>But Undo action does not work correctly now. I hope fixed soon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9CnYsOGANsEVkWmxruUPTA.png" /></figure><h3><a href="https://71squared.com/focused">Focused</a></h3><p>Recently I started to use new one, <strong>Focused</strong>. It includes 2 modes (Typewriter mode or Focus mode), some themes, and other good features.</p><p>I love the SoundTrack feature. We can play 8 calming soundtracks when we editing. Of course,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*pLq2ydt1WP9TgYrLGMMa8w.png" /></figure><h3><a href="http://www.typora.io/">Typora</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f9U0UFnFU8W-S8A1FiO5ew.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91319404500a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Frontend Weekly 購読のススメ]]></title>
            <link>https://medium.com/@1000ch/frontend-weekly%E8%B3%BC%E8%AA%AD%E3%81%AE%E3%82%B9%E3%82%B9%E3%83%A1-126928758d16?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/126928758d16</guid>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Tue, 18 Aug 2015 05:06:05 GMT</pubDate>
            <atom:updated>2016-09-02T05:05:57.287Z</atom:updated>
            <content:encoded><![CDATA[<p>今日は <a href="http://frontendweekly.tokyo/">Frontend Weekly</a> というメールマガジンを紹介したいと思います。私自身も編集に関わっているので宣伝にはなりますが、 <strong>Frontend Weekly が何を目的としているか</strong>、 <strong>Frontend Weekly を購読することで読者がどんなメリットを得られるか</strong>を考えてみます。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*WETdFpbwf3b1UoEXgnytkQ.png" /><figcaption>Frontend Weekly Logo</figcaption></figure><h3>Frontend Weekly の概要</h3><p>まずは <strong>Frontend Weekly とは一体何なのか</strong> を説明する必要がありそうです。 Frontend Weekly は、 HTML や CSS 、 JavaScript などの Web フロントエンド技術に関する記事・ライブラリなどの情報を中心に、週に一度水曜日に配信しているメールマガジンです。</p><p>キュレータは @<a href="http://twitter.com/cssradar">cssradar</a> ・ <a href="http://twitter.com/hiloki">@hiloki</a> ・ <a href="http://twitter.com/t32k">@t32k</a> ・ <a href="http://twitter.com/ahomu">@ahomu</a> ・ <a href="http://twitter.com/1000ch">@1000ch</a> の5人です。この5人で集めたリソースの中から、今後のトレンドになりそうな、あるいはキャッチアップすべきリソースをピックアップし、それぞれに日本語のサマリーを付けて配信しています。</p><h3>英語リソースを中心に紹介</h3><p>紹介するリソースの多くは英語ですが、これには理由があります。</p><p>技術仕様に関するリソースのドキュメントのほとんどは英語で書かれています。英語が国際的な公用語に最も近い言語であることも理由の1つですが、技術経済が英語圏で生まれ、今も存在していることが最も大きな理由でしょう。これは Web 技術も例外ではありません。</p><p>英語リソースを日本語に翻訳してくれるメディアもありますし、有志もたくさんいます。しかし、これらだけを期待することにはいくつかリスクがあります。</p><ul><li>英語から日本語へ誤訳される可能性が生まれる</li><li>翻訳を待つ時間、情報の鮮度が落ちる</li></ul><p>こうしたリスクと Frontend Weekly の <strong>最新情報を届けるというメディアの性質</strong> を考慮すると、英語リソースの紹介が必然的に多くなります。日本語が世界のデファクトになることは恐らくないでしょうから、最新動向を追っていく上で英語は避けて通れません。</p><p>英語を恐れる必要はありません。英語は苦手という人も、時間をかけて1記事ずつ消化してください。<a href="http://css.studiomohawk.com/english/2012/01/29/reading-english-is-not-so-hard/">ウェブデベロッパのための英語</a>という記事に英語を読むヒントが書かれています。</p><p>もちろん、日本語にも素晴らしいリソースがあります。質の高い英語リソースをピックアップして届けることもミッションの1つですが、同時に素晴らしい日本語リソースが増えていくことも期待しています。</p><h3>情報源を絞る</h3><p>こうしている間にも、新たな情報が世界中で発信され続けています。その中から価値のある情報を探し出すには、次のような労力が発生します。</p><ul><li>大量のメディアの中から <strong>信頼できる購読する情報源を選択する</strong></li><li>古い・誤っているなどの <strong>価値の小さい情報源をフィルタする</strong></li></ul><p>これらを実践し続けることは、とても労力の要ることです。 Frontend Weekly では情報を集める過程でこれらを行うことで、価値の高い情報を求める人が払う労力をなるべく取り除けるとも考えています。</p><p>キュレーターは私を含めて5人ですが、皆 Web の最新動向を追いかけている人ばかりです。とりわけ <a href="http://twitter.com/cssradar">@cssradar</a> は、 Frontend Weekly が生まれる前からこうした活動を続け、そして実績を挙げていることは皆さんもご存知かと思います。もちろん私も、よりよい情報を提供できるように、常に注意して情報を探っています。</p><h3>Frontend Weekly を購読するメリット</h3><p>ここまで説明した通り、 Frontend Weekly は <strong>Web にまつわる技術動向を追う上で発生するコスト</strong> を小さくしているメディアです。</p><p>Web 界隈の技術進化は目覚ましく、今は最新と呼ばれる技術も<strong>一年後には陳腐化しているかもしれません</strong>。枯れた技術を棄て、新たな技術を選択し続けていくことも、 Web を生業にする人間にとって必要な技術ではないでしょうか。そんなご時世を生き抜くツールの1つとして Frontend Weekly を活用してください。</p><p>Frontend Weekly はまだまだ未完成のメディアです。皆さんのフィードバックを受けながら、常にブラッシュアップしていきたいと考えています。皆さんの意見を聞かせてください。</p><h3>日本のWebを前に進める</h3><p>最後になりますが、 <strong>Frontend Weekly の購読は無料</strong> です。購読していない人は、これを機に<a href="https://frontendweekly.tokyo/">是非登録してみてください</a>。</p><p>また、<strong>「どんなメールが来るのか気になる…！」</strong>、<strong>「過去の配信記事を見てみたい！」</strong>という人のために、配信したメールも<a href="http://frontendweekly.tokyo/backnumbers">バックナンバーとしてアーカイブ</a>してあります。</p><p>Frontend Weekly が Web のメインストリームに飛び込むきっかけになれば幸いです。</p><p>それでは、次号の配信をお楽しみに。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=126928758d16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to WebP]]></title>
            <link>https://medium.com/@1000ch/introduction-to-webp-b593dfe1d1d1?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/b593dfe1d1d1</guid>
            <category><![CDATA[webp]]></category>
            <category><![CDATA[image]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Sun, 03 May 2015 12:37:53 GMT</pubDate>
            <atom:updated>2020-08-14T06:49:34.005Z</atom:updated>
            <content:encoded><![CDATA[<h4>WebP is a new image format by Google.</h4><p>As I have mentioned <a href="http://bit.ly/we-should-optimize-images">before</a>, images account for about 60%~70% of web bandwidth. That is to say, image is one of the most important factor for web performance. WebP is superior to other image formats in some points.</p><h3>WebP Features</h3><h4>Lossy and Lossless compression</h4><p>PNG and GIF support lossless compression, JPEG supports lossy compression, but WebP supports both lossy and lossless compression. And it should be specially mentioned that WebP contains higher compression than other image formats.</p><blockquote>WebP lossless images are 26% smaller in size compared to PNGs. WebP lossy images are 25–34% smaller in size compared to JPEG images at equivalent SSIM index. via <a href="https://developers.google.com/speed/webp/">WebP - Google Developers</a></blockquote><h4>Transparency &amp; Animation support</h4><p>WebP also supports an alpha channel (like PNG) and animation (like GIF) with lossless and lossy compression.</p><blockquote>WebP supports lossless transparency (also known as alpha channel) with just 22% additional bytes. Transparency is also supported with lossy compression and typically provides 3x smaller file sizes compared to PNG when lossy compression is acceptable for the red/green/blue color channels. <em>via </em><a href="https://developers.google.com/speed/webp/">WebP — Google Developers</a></blockquote><h3>Browser Support</h3><p>WebP is available on the following browsers.</p><ul><li>Chrome, Chrome for Android, Chrome for iOS</li><li>Edge</li><li>Opera</li><li>Firefox (65~)</li><li>Safari (14~)</li></ul><p>Firefox and Safari do not currently support WebP. But interestingly, Chrome on iOS seems to contain WebP decoder and is able to display WebP images!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UEGe_QfPJslExO7L3kiHNQ.jpeg" /><figcaption>Safari &amp; Chrome on iOS</figcaption></figure><p>This means that WebP is available on every Android and iOS application that bundles a WebP decoder.</p><p>Safari once tried to support WebP, but dropped support, unfortunately. I wish WebP is supported on any platforms, tools.</p><h3>Dean Jackson on Twitter</h3><p>Safari from the macOS Sierra and iOS 10 seeds released today no longer supports WebP. Unfortunately this causes some compat. issues (cont)</p><p><strong>Updated on 2019/02/01: Firefox 65 will support WebP!</strong></p><h3></h3><p>Heck of a release for Firefox! https://t.co/3mWVDhFXTC- Flexbox Inspector- WebP- env()- steps()- break-*</p><p><strong>Updated on 2020/08/11: Safari 14 will support WebP finally!</strong></p><h3></h3><p>Safari 14 Beta Release Notes* Added WebP* Changed to derive aspect ratio from size attributes* Added :is()* Added :where() * Safari no longer supports Flash* Added Safari Web Extensions* Added Webpage Translation (Beta)&amp; much more: https://t.co/qO2Cy7rK4A</p><h3>Falling Back to Other Formats</h3><h4>The &lt;picture&gt; and &lt;source&gt; elements</h4><p>As you may know, the <strong>&lt;picture</strong>&gt; and <strong>&lt;source&gt;</strong> elements are a new way for responsive resource loading. The <strong>&lt;source&gt; </strong>element<strong> </strong>has a<strong> type </strong>attribute to specify the resource’s <strong>mime-type</strong> for supporting browsers,<strong> </strong>so we can make browsers load images which specified with them such as the following:</p><pre>&lt;picture&gt;<br>  &lt;source srcset=&quot;image.webp 1x&quot; type=&quot;image/webp&quot;&gt;<br>  &lt;img src=&quot;image.jpg&quot;&gt;<br>&lt;/picture&gt;</pre><p>In this case, a browser will load <strong>image.webp</strong> if WebP is supported, and load <strong>image.jpg</strong> otherwise.</p><h4>WebPJS</h4><p><a href="http://webpjs.appspot.com/">WebPJS</a> is JavaScript library that converts WebP images into a data URI string on the client-side.</p><h4>Check Accept Headers on the Server-side</h4><p>Browsers send <strong>Accept </strong>Headers with each request. Something like…</p><pre>Accept: image/webp, image/png, image/jpeg, image/gif, image/svg+xml, image/bitmap</pre><p>So, the server can choose images to return to browsers by checking whether the request header sent from the client-side contains <strong>Accept: image/webp</strong> or not. If it does not contain <strong>image/webp</strong>, we can make our servers return PNG or JPEG or GIF images which, maybe original before converted into WebP ☺</p><p>I recommend you check the following resources.</p><ul><li><a href="https://www.igvita.com/2013/05/01/deploying-webp-via-accept-content-negotiation/">Deploying WebP via Accept Content Negotiation </a>— by <a href="https://www.igvita.com/">Ilya Grigorik</a></li><li><a href="https://www.igvita.com/2013/03/07/faster-smaller-and-more-beautiful-web-with-webp/">Faster, smaller and more beautiful web with WebP</a><a href="https://www.igvita.com/2013/05/01/deploying-webp-via-accept-content-negotiation/"> </a>— by <a href="https://www.igvita.com/">Ilya Grigorik</a></li><li><a href="https://www.igvita.com/2012/12/18/deploying-new-image-formats-on-the-web/">Deploying New Image Formats on the Web</a> — by <a href="https://www.igvita.com/">Ilya Grigorik</a></li><li><a href="https://github.com/igrigorik/webp-detect">igrigorik/webp-detect</a>—WebP with Accept negotiation by <a href="https://www.igvita.com/">Ilya Grigorik</a></li></ul><h3>Tools for WebP</h3><h4>cwebp-bin</h4><p>If you want to convert images into WebP, you can get <a href="https://github.com/imagemin/cwebp-bin">cwebp-bin</a> which is Node.js wrapper of cwebp via NPM.</p><pre>$ npm install cwebp-bin</pre><p>Of course, a <a href="https://developers.google.com/speed/webp/docs/precompiled">pre-compiled binary</a> and the <a href="http://downloads.webmproject.org/releases/webp/index.html">source code</a> to manually build it are available from the <a href="https://developers.google.com/speed/webp">official web site</a>.</p><h4>grunt and gulp</h4><p>Integrating with Grunt and Gulp? <a href="https://github.com/1000ch/grunt-cwebp">grunt-cwebp</a> and <a href="https://github.com/1000ch/gulp-cwebp">gulp-cwebp</a> are also available via NPM.</p><pre>$ npm install grunt-cwebp<br>$ npm install gulp-cwebp</pre><h4>WebPonize</h4><p><a href="https://webponize.org/">WebPonize</a> is a macOS application that converts images to WebP. It accepts PNG, JPEG, and GIF. If you are using macOS High Sierra or higher, you can <a href="https://apps.apple.com/us/app/id1526039365?mt=12">download from the App Store</a>. Just drag and drop images!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jbdcMaOAiuFwSLaHnga3_w.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b593dfe1d1d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Components Pitfalls]]></title>
            <link>https://medium.com/@1000ch/web-components-pitfalls-c291b763014a?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/c291b763014a</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-components]]></category>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Fri, 10 Apr 2015 09:24:12 GMT</pubDate>
            <atom:updated>2015-10-05T15:53:02.086Z</atom:updated>
            <content:encoded><![CDATA[<p>Web Components composed of Custom Elements, Templates, Shadow DOM and HTML Imports definitely solve CSS problems which cause front-end developer trouble.</p><p>It’s easy to use distributed Web Components, but I think it’s really doubtful that processing HTML components using Web Components will become popular. It’s too difficult to create Web Components with a full understanding their specs in a conventional way (eg. writing native HTML, and styling it with CSS).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*y_afFo_4YVuBL8b8lF54xg.jpeg" /><figcaption><a href="https://www.flickr.com/photos/mattijn/4419973636">the difficult route</a> by <a href="https://www.flickr.com/photos/mattijn/">Mattijn Franssen</a></figcaption></figure><p>It’s only shifting the problem from worrying about CSS scope to worrying about a Web Components architecture, isn’t it?</p><h3>Technical Awkwardness with Web Components</h3><p>It’s too difficult to use Shadow DOM only to solve the CSS scope problem for the developer. In addition, shifting the description style from Declarative to Imperative may be a little boring for non-programmers.</p><pre>&lt;template&gt;<br>  &lt;style&gt;<br>    input {...}<br>    button {...}<br>  &lt;/style&gt;<br>  &lt;input type=&quot;text&quot;&gt;<br>  &lt;button&gt;Button&lt;/button&gt;<br>&lt;/template&gt;<br>&lt;script&gt;<br>  var ownerDocument = document.currentScript.ownerDocument;<br>  var ElementPrototype = Object.create(HTMLElement.prototype);</pre><pre>  ElementPrototype.createdCallback = function () {<br>    var template = ownerDocument.querySelector(&#39;template&#39;);<br>    var clone = document.importNode(template.content, true);<br>    this.shadowRoot = this.createShadowRoot();<br>    this.shadowRoot.appendChild(clone);<br>  };</pre><pre>  document.registerElement(&#39;sample-element&#39;, {<br>    prototype: ElementPrototype<br>  });<br>&lt;/script&gt;</pre><p>Polymer attempts to make these steps simpler. Troublesome API calling from JavaScript to create a Shadow DOM is omitted through the use of the Polymer Element. The following code is written in Polymer style (version 0.5):</p><pre>&lt;polymer-element name=&quot;sample-element&quot; noscript&gt;<br>  &lt;template&gt;<br>    &lt;style&gt;<br>      input {...}<br>      button {...}<br>    &lt;/style&gt;<br>    &lt;input type=&quot;text&quot;&gt;<br>    &lt;button&gt;Button&lt;/button&gt;<br>  &lt;/template&gt;<br>&lt;/polymer-element&gt;</pre><p>Element registration way is changed in newest Polymer (version 0.8). But it’s already easier than Pure Web Components style.</p><pre>&lt;dom-module id=&quot;sample-element&quot;&gt;<br>  &lt;style&gt;<br>    input {...}<br>    button {...}<br>  &lt;/style&gt;<br>  &lt;template&gt;<br>    &lt;input type=&quot;text&quot;&gt;<br>    &lt;button&gt;Button&lt;/button&gt;<br>  &lt;/template&gt;<br>&lt;/dom-module&gt;<br>&lt;script&gt;<br>  var SampleElement = Polymer({is: &#39;sample-element&#39;});<br>&lt;/script&gt;</pre><p>Trying to simplify this process is important.</p><p>I don’t know which is correct — whether the spec should be simple for developers, or libraries such as Polymer should simplify complex specs. But the gap between them will be closed in time.</p><h3>Difficulty Processing Components</h3><p>There is not a lot of know-how gathered about Componentizatoin. A developer learns mainly through experience about:</p><ul><li>Which features the component include</li><li>Which is public attribute</li><li>Abstractness and versatility</li><li>Components consistency</li></ul><p>First, we should share the idea of Componentizing with designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*wlW2NhQyO9_aT2QG8liDSQ.jpeg" /><figcaption><a href="https://www.flickr.com/photos/37634075@N03/5964993508">Laura + Jaime Wedding | Mercury Hall</a> by <a href="https://www.flickr.com/photos/37634075@N03/">The Simplifiers</a></figcaption></figure><p>The scope provided by Shadow DOM should be praised. But don’t forget that we can style the Shadow DOM from outside through selectors such as “<strong>::shadow”</strong>, “<strong>&gt;&gt;&gt;” </strong>combinator.</p><p><a href="https://twitter.com/ebidel">Eric Bidelman</a> said in <a href="http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-201/">Shadow DOM 201 — HTML5Rocks</a>.</p><blockquote>As authors of custom elements, we have a ton of options for controlling the look and feel of our content. Shadow DOM forms the basis for this brave new world.</blockquote><blockquote>Shadow DOM gives us scoped style encapsulation and a means to let in as much (or as little) of the outside world as we choose. By defining custom pseudo elements or including CSS Variable placeholders, authors can provide third-parties convenient styling hooks to further customize their content. All in all, web authors are in full control of how their content is represented.</blockquote><p>Adding the above selectors to temporarily fix styling causes the same mistakes as before. In the end, we should refactor and be literate in dealing with Web Components.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c291b763014a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ドラム式洗濯乾燥機「プチドラム」で快適洗濯生活]]></title>
            <link>https://medium.com/@1000ch/-b2cbcfc4a4c1?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2cbcfc4a4c1</guid>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Sun, 15 Feb 2015 05:52:08 GMT</pubDate>
            <atom:updated>2016-05-18T05:00:31.139Z</atom:updated>
            <content:encoded><![CDATA[<p>もともと洗濯は好きだった方だけど、ドラム式洗濯乾燥機という高価な買い物を久々にしたら、快適になり過ぎてパンツが吹っ飛んだ話。</p><h3>Point.1「洗濯から乾燥まで全自動」</h3><p>それまでは、いわゆる一槽式の洗濯機を使ってた。今どきは、乾燥までやってくれるタイプの一槽式もあるみたいだけど、自分が使っていたのはもちろん脱水までのタイプ。絞った雑巾のようになった洗濯物を、ハンガーや洗濯干を駆使して一つ一つ干していた。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*APp3bowsYMB2tiC06xBIpw.jpeg" /></figure><p>ところがドラム式洗濯乾燥機は、洗濯した服がふっくらホカホカの状態で出てきてくれるので、あとは畳んで収納するだけだ。急ぎであればそのまま着ても気持ちいい。</p><p>だから、<strong>乾燥場を使うこともないし、雨の日に干す場所に悩むこともない。洗った洗濯物を忘れて、生乾きなんてこともない。</strong></p><p>もちろん「洗濯→乾燥」だけじゃなくて、「洗濯だけ」「乾燥だけ」のコースもあるので、洗濯・乾燥のどちらかだけやりたい場合でも大丈夫。私の場合は、シャツやボトムス類はシワにならないように洗濯までしていて、その他のTシャツやタオル等は乾燥しても問題なさそうなので「洗濯→乾燥」のフルコースにしている。</p><h3>Point.2「ヒートポンプ乾燥で衣類が縮みにくく、電気代も安い」</h3><p><strong>「ドラム式洗濯乾燥機で乾燥したら、衣類が縮んだ！」</strong>なんていう話もチラホラあるようだけど、自分の場合はこれに遭遇したことがない。購入した洗濯機の乾燥はどうやら<a href="http://www.hptcj.or.jp/study/tabid/102/Default.aspx">ヒートポンプ</a>という技術で乾燥をしているらしく、より少ないエネルギーで乾燥できる上に、従来よりも縮みにくいらしい。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*1pM1kUF7STs-RcaxVJBWXQ.jpeg" /></figure><p>以下<a href="http://ja.wikipedia.org/wiki/%E3%83%92%E3%83%BC%E3%83%88%E3%83%9D%E3%83%B3%E3%83%97">Wikipedia</a>より引用。</p><blockquote>ヒートポンプ（英: heat pump）は、熱媒体や半導体等を用いて低温部分から高温部分へ熱を移動させる技術である。手法はいくつかあるが主流は気体の圧縮・膨張と熱交換を組み合わせたもので、一般家庭でもみられる製品でヒートポンプを使っているものとして冷凍冷蔵庫、エアコン、ヒートポンプ式給湯器などがある。</blockquote><p>縮みにくいとはいえ、高価な服だったり、シャツみたいにシワを付けたくない部類の洋服は乾燥までしないほうが無難だろう。大事をとって洗濯だけのコースにして、今までどおりハンガーで干す方が安全かと思う。</p><p>ちなみにヒートポンプ式ではないモデルもあって、こちらはもう少し廉価になっている。</p><p><a href="http://www.amazon.co.jp/dp/B00I0OAR92/?tag=1000ch-22">パナソニック 7.0kg ドラム式洗濯乾燥機【左開き】クリスタルホワイトPanasonic　プチドラム　エコナビ NA-VH310L-W</a></p><h3>Point.3「コンパクトでスペースを取らない」</h3><p>ドラム式乾燥洗濯機というと、かなり大型なイメージがあったけど、各メーカーが一人暮らし向けのコンパクトなドラム式のラインナップを出しているそうで、これもその中のひとつになる。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*okCdRWNCFrht3R8jJyDNqg.jpeg" /></figure><p>当方ワンルームだが、搬入に苦労することもなく備え付けの洗濯機置き場にすっぽり収まった。<strong>幅・奥行きともに60cmに収まれば問題無い</strong>ようで、一般的な集合住宅の洗濯機置き場であれば充分に満たしているサイズだ。</p><p>洗濯容量は7.0kg、乾燥容量は3.5kg。一人暮らしであれば充分な容量だし、干す手間が省ける分こまめに洗濯するようになったので、洗いきれずに大変ということもない。</p><p>その他の機能としては「<a href="http://panasonic.jp/wash/product/na_vh310l/econavi.html">エコナビ</a>」「<a href="http://panasonic.jp/wash/product/na_vh310l/auto_cleaning.html">自動槽洗浄</a>」「<a href="http://panasonic.jp/wash/product/na_vh310l/dancing.html">泡洗浄・ダンシング洗浄</a>」「<a href="http://panasonic.jp/wash/product/na_vh310l/speedy.html">お急ぎコース</a>」と、至れりつくせり。</p><p><a href="http://www.amazon.co.jp/dp/B00U2569GW/?tag=1000ch-22">パナソニック 7.0kg ドラム式洗濯乾燥機【左開き】クリスタルホワイトPanasonic　プチドラム　エコナビ　ECONAVI　ヒートポンプ乾燥 NA-VH320L-W</a></p><p>場所・天気と干すことに気を遣わなくなったし、洗ったものはホカホカふっくら出てくるし、何より<strong>洗濯という家事に対してかける時間が減ったのに満足度がグッと上がった</strong>。</p><p><strong>QoL挙がること間違いなし。</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2cbcfc4a4c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We should optimize images]]></title>
            <link>https://medium.com/@1000ch/we-should-optimize-images-8435760e0ec9?source=rss-1edb20469358------2</link>
            <guid isPermaLink="false">https://medium.com/p/8435760e0ec9</guid>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Shogo Sensui]]></dc:creator>
            <pubDate>Fri, 04 Apr 2014 09:55:37 GMT</pubDate>
            <atom:updated>2015-08-21T09:11:49.730Z</atom:updated>
            <content:encoded><![CDATA[<h4>for the better web performance</h4><p>Steve Souders said on <a href="http://stevesouders.com/hpws/">High Performance Web Site</a>,</p><blockquote><em>80-90% of the end-user response time is spent on the frontend.</em><br><em>Start there.</em></blockquote><p>Web performance mostly depends on the frontend. This means to make the web faster, we have to optimize the frontend. For example, it contains following factors:</p><ul><li>Minimize <a href="https://developers.google.com/speed/docs/best-practices/rtt">round trip times</a> and <a href="https://developers.google.com/speed/docs/best-practices/request">request overhead</a></li><li><a href="https://developers.google.com/speed/docs/best-practices/payload">Minimize payload size</a></li><li><a href="https://developers.google.com/speed/docs/best-practices/rendering">Optimize browser rendering</a></li><li>And others…</li></ul><p>Minimizing payload size is one of the easiest to apply. To reduce the number and payload size, we have to reduce HTML, CSS, and image files. Especially, the file size of images takes most bandwidth in most cases. So I will introduce you to some tools for image optimization.</p><h3>GUI Tools for image optimization</h3><ul><li><a href="http://imageoptim.com/">ImageOptim</a> — image optimizer which contains PNGOUT, Zopfli, Pngcrush, AdvPNG, extended OptiPNG, JpegOptim, jpegrescan, jpegtran, and Gifsicle.</li><li><a href="http://pngmini.com/">ImageAlpha</a> — reduce file sizes of 24bit PNGs by converting them to 8bit.</li><li><a href="http://www.jpegmini.com/">JPEGmini</a> — reduce file sizes of JPEG images by applying lossy compression (But it looks keeping original quality!).</li><li><a href="https://code.google.com/p/pngoo/">pngoo</a> — PNG image compressor for Windows.</li><li><a href="https://webponize.github.io/">WebPonize</a> — a Mac OS App for converting images into WebP.</li></ul><h3>Image comparison</h3><p>They are GUI applications so you can use them to easily apply compression to your images. Here is the sample result of PNG image compression:</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*bo9IF9O9Ah77fSAbCQUDjA.png" /><figcaption>Uncompressed PNG (71,834bytes)</figcaption></figure><p>This is original PNG image without compression. This image is 24bit oriented and contains lots of meta such as location, date, and time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*jHvcLUUt0m9aE3aecxY5ww.png" /><figcaption>Compressed PNG (28,369 bytes) with ImageAlpha &amp; ImageOptim</figcaption></figure><p>This is the 8bit-converted PNG compressed with ImageAlpha and ImageOptim. It looks <strong>not</strong> <strong>degraded.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*h6CK4BJ17MkEdrkzU_wnBg.jpeg" /><figcaption>Optimized JPEG (213171 bytes) with ImageOptim. Meta is removed. But lossy-compression is not applied.</figcaption></figure><p>As other example, this one is a JPEG. Meta is removed with ImageOptim and lossy-compression is not applied.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*_MiUa3o8Y7-zXO_a5W5miQ.jpeg" /><figcaption>Compressed JPEG (71874 bytes) with JPEGmini &amp; ImageOptim</figcaption></figure><p>This one is compressed with JPEGmini. It does not look too degraded, and the file size is about 34% of the original (66% cut!!!). Photos that contain many colors will be degraded, so we have to check the image after compression. It is a little boring, but it’s worth it.</p><h3>CUI Tools for image optimization</h3><p>I also wanted CLI tool, so I created the tool as grunt task and gulp one.</p><ul><li><a href="https://github.com/1000ch/grunt-image">grunt-image</a> — Optimizes PNG, JPEG, GIF images without GUI.</li><li><a href="https://github.com/1000ch/gulp-image">gulp-image</a> — Gulp one of above.</li></ul><p>You can optimize PNG, JPEG, GIF images with using them. Installation? It’s simple and easy if you have used Grunt or Gulp. (I guess you have already used them☺)</p><pre># download them using npm</pre><pre>$ npm install —-save-dev grunt-image</pre><pre>$ npm install —-save-dev gulp-image</pre><p>Detailed settings are on the projects’ GitHub repositories.</p><h3>WebP is a new image format by Google</h3><p><a href="https://developers.google.com/speed/webp/">WebP</a> is also awesome. This is a new image format by Google. It says,</p><blockquote>WebP lossless images are <a href="https://developers.google.com/speed/webp/docs/webp_lossless_alpha_study#results">26% smaller</a> in size compared to PNGs. WebP lossy images are <a href="https://developers.google.com/speed/webp/docs/webp_study">25-34% smaller</a> in size compared to JPEG images at equivalent SSIM index.</blockquote><p>WebP is supported by Chrome and other browsers which contains <a href="http://www.google.com/chromeframe">Chrome Frame</a>. Firefox and Safari do not currently support WebP. But interestingly Chrome on iOS is able to display WebP images (It seems to have Chrome Frame)!</p><p>WebP is available from <a href="https://developers.google.com/speed/webp/">here</a>. I want to show you WebP image, but it is not available on Medium sadly ☹ However in my test, the PNG file size before converting into WebP is <strong>28,369 bytes</strong>. After converting, file size of WebP one is <strong>17382 bytes</strong>, and it looks not degraded Yay!</p><p>If you have ever not taken care of image optimization, you should apply optimization for the better web performance. Finally, I recommend the following articles to learn more about image:</p><ul><li><a href="http://www.phpied.com/give-png-a-chance/">Give PNG a chance</a> — by <a href="http://www.phpied.com/bio/">Stoyan Stefanov</a></li><li><a href="http://calendar.perfplanet.com/2013/mobile-isp-image-recompression/">Mobile ISP image recompression</a> — by <a href="http://pornel.net/">Kornel Lesiński</a></li><li><a href="http://www.sitepoint.com/png8-the-clear-winner/">PNG8 — The Clear Winner</a> —by <a href="http://www.sitepoint.com/author/alex-walker/">Alex Walker</a></li><li><a href="http://calendar.perfplanet.com/2010/png-that-works/">PNG that works</a> — by <a href="http://pornel.net/">Kornel Lesiński</a></li><li><a href="http://www.html5rocks.com/en/tutorials/speed/img-compression/">Image Compression for Web Developers</a> — by <a href="http://www.html5rocks.com/en/profiles/#coltmcanlis">Colt McAnlis</a></li><li><a href="https://bit.ly/introduction-to-webp">Introduction to WebP</a> — by <a href="http://github.com/1000ch">Me</a></li></ul><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8435760e0ec9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>