<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: C6C6C6C</title><link>https://news.ycombinator.com/user?id=C6C6C6C</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 13 May 2026 16:04:32 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=C6C6C6C" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by C6C6C6C in "Apple Says It Slows Older iPhones to Save Their Battery Life"]]></title><description><![CDATA[
<p>The battery can't handle 1 year of use because they undersized it. A 1 715 mAh battery will, once aging, be less able to provide the voltage asked by peak CPU usage than a 2900 mAh battery that has aged for about the same amount of charge cycles.<p>iPhones are the only device sold by Apple that are only rated for 500 charge cycles before degradation starts. Macbook, iPads and Apple Watches are rated for 1000 cycles. In the case of the Apple Watch I'd guess it's because despite being tiny, the SOC also doesn't ask for as much peak voltage as the phone SOC.<p>I've had the Honor 8 for a year. It's still holding a great amount of charge and running fine and as fast as the day I bought it. And unlike my 5s, no phone update is coming to turn it into a slow crawl.<p>The iPhone battery problem with regards to the topic, spontaneous shutdown at 30% and less battery remaining, is probably exacerbated since the evolutions that made those SOC more powerful than before. There wasn't a large wave of 5s owners having spontaneous shutdown requiring an OS update to throttle the CPU. That only started with the iPhone 6. A combination of paltry battery and modern SOCs having peak power usage that stress such battery more than before.</p>
]]></description><pubDate>Thu, 21 Dec 2017 18:41:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=15981577</link><dc:creator>C6C6C6C</dc:creator><comments>https://news.ycombinator.com/item?id=15981577</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=15981577</guid></item><item><title><![CDATA[New comment by C6C6C6C in "Apple Says It Slows Older iPhones to Save Their Battery Life"]]></title><description><![CDATA[
<p>Same experience, but I went back to the iPhone once, only once, with the iPhone 5s, and then already deeply regretted it after updating iOS to the latest. I should have known they'd do it again after what I experienced with the iPhone 3g last update, which made the thing so slow it was unusable.<p>The iPhone 5s should have hardware that is much faster than what's in a Moto G2. Yet, my friend's Moto G2 feels smoother in use, transitioning between apps and the like, than the 5s. I bought the Honor 8 to replace it, a somewhat cheap, midrange android device. Everything on it feels so fast I probably won't replace it until its battery gives out completely. On the paper, the hardware of the Honor 8 is not as fast as modern iPhones. In practice when I open apps it's pretty much instantaneous.  The device has enough RAM to keep everything running.<p>People keep complaining android manufacturers aren't updating the OS fast enough. I'd say good on them to make sure they only give us an OS build that's actually usable on said hardware. Apple doesn't even let you install previous iOS versions. 
Unlike iOS, most of Android's platform APIs are updated through the Play Store. Things like your web browser are also updated through the play store. So unlike iPhones where refusing new iOS updates means being stuck with browser engines that can't keep up with the web, your android handset stuck on older android is not actually becoming obsolete.<p>No matter how much nicer Apple's hardware looks and feels in the hands, I ain't ever giving them more of my money again. Premium prices should command more durability in time than this. Chosing to stay on an old iOS means you can't install new apps built on newer SDKs or get newer browsers and so on, so you really have to suffer the slow down treadmill with Apple. You don't have to on Android.</p>
]]></description><pubDate>Thu, 21 Dec 2017 18:06:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=15981200</link><dc:creator>C6C6C6C</dc:creator><comments>https://news.ycombinator.com/item?id=15981200</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=15981200</guid></item><item><title><![CDATA[New comment by C6C6C6C in "Retrotechnology – PC desktop screenshots from 1983-2005"]]></title><description><![CDATA[
<p>Some older computers had weird resolution / aspect ratio combination.<p><a href="https://www.gamasutra.com/blogs/FelipePepe/20150423/241730/No_MSDOS_games_werent_widescreen_Tips_on_correcting_aspect_ratio.php" rel="nofollow">https://www.gamasutra.com/blogs/FelipePepe/20150423/241730/N...</a><p>Basically, if you play video games from the DOS era on a modern computer without correcting their aspect ratio they look stretched, and that was not how they were supposed to look.<p>So, the same goes for fonts. They look weird if you look at it with your current resolution and aspect ratio. They would look more condensed/thinner on the CRT monitors of the DOS era.<p>> The thing is, most MS-DOS games were actually rendered in 320x200, which is a 16:10 aspect ratio and thus widescreen – but they weren't displayed that way. I won't pretend I know all the technical details – there are way better sources for that – simply put, the CRT monitors back then stretched images to fit the screen.<p>> The 320x200 image was stretched to fit the entire 4:3 screen, to something close to 320x240. What today we see as a sharp, square pixel was actually a blurry rectangle back then, about 20% taller than wider (the Amiga, Apple II, Atari ST and other home computers all had different resolutions, but the principle is quite similar).<p>Even if you're lowering your current monitor resolution you're not actually seeing those fonts the way they were meant to be rendered. That's because your monitor will display a native DOS resolution as widescreen. When CRT monitors of the time took that widescreen resolution and turned it square.<p>There's a lot of understanding about old rendering methods that has been lost in the mainstream. The article I linked also showed how people exploited scanlines to make water look transparent in a very smoothed way. Your LCD pixel grid just doesn't show things the way old low resolution CRTs did.</p>
]]></description><pubDate>Wed, 20 Dec 2017 18:06:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=15972084</link><dc:creator>C6C6C6C</dc:creator><comments>https://news.ycombinator.com/item?id=15972084</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=15972084</guid></item><item><title><![CDATA[New comment by C6C6C6C in "Retrotechnology – PC desktop screenshots from 1983-2005"]]></title><description><![CDATA[
<p>They're actually represented just about right if the screenshot collection goal is to show changes throughout time. There's screenshots of Windows 2.1, 3.0 and NT 4.0. Windows from 95 to 2000 kept the exact same look. There's absolutely no point in having a screenshot of each iteration in between. There's just not enough visual and conceptual UI change to really make it worth it having shots of 95, 98, NT4, ME, 2000. A shot of any of these will speak for the entire timeframe.<p>Compare this shot of Windows 2000 to the one of NT4 they feature on their page :<p><a href="https://guidebookgallery.org/pics/gui/desktop/full/win2000advserv.png" rel="nofollow">https://guidebookgallery.org/pics/gui/desktop/full/win2000ad...</a><p>See any major change? right.<p>Windows XP is missing but in a way it might not count as retro enough because it has lived and been with us for far, far longer than most OS usually do.</p>
]]></description><pubDate>Wed, 20 Dec 2017 17:35:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=15971749</link><dc:creator>C6C6C6C</dc:creator><comments>https://news.ycombinator.com/item?id=15971749</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=15971749</guid></item><item><title><![CDATA[New comment by C6C6C6C in "Unknown Mozilla dev addon "Looking Glass 1.0.3" on browser"]]></title><description><![CDATA[
<p>Not to mention the great amount of money they've wasted in certain previous frivolous, doomed projects, like Firefox OS - great idea, by the way, to make your "native" app platform the most power hungry, slowest of them all, and then market the OS only for pairing it with low end devices sold to third worlders - because third worlders totally need slow software running on the hardware they can barely afford - it's not as if they were people, with real world needs, just like us, and not lab rats. For a company that prides itself on its open values.. that's really treating people with contempt.</p>
]]></description><pubDate>Sat, 16 Dec 2017 00:17:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=15936469</link><dc:creator>C6C6C6C</dc:creator><comments>https://news.ycombinator.com/item?id=15936469</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=15936469</guid></item></channel></rss>