<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: ksec</title><link>https://news.ycombinator.com/user?id=ksec</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 18 Oct 2026 04:08:34 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=ksec" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Sake-lang: Experimental language based on Ruby but with types for each operation]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/ko1/sake-lang">https://github.com/ko1/sake-lang</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=50133927">https://news.ycombinator.com/item?id=50133927</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Sat, 17 Oct 2026 18:55:25 +0000</pubDate><link>https://github.com/ko1/sake-lang</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50133927</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50133927</guid></item><item><title><![CDATA[New comment by ksec in "Apple's new 'Switch to Safari' campaign details why you should ditch Chrome"]]></title><description><![CDATA[
<p>While all my day to day browsing annoyance were all gone by Safari 18.x, there are still bugs or rendering issues that i had to use Chrome now and then. Safari needs to keep grinding for the next 2-3 years and not cut any resources. I am not even asking for Safari on Windows, but Apple needs to up or sustain its current development and give it more time. Especially memory resources usage and multi tab operations.</p>
]]></description><pubDate>Sat, 17 Oct 2026 18:12:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=50133522</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50133522</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50133522</guid></item><item><title><![CDATA[New comment by ksec in "Firefox Enterprise"]]></title><description><![CDATA[
<p>20 years later they are finally taking Enterprise seriously. I still remember how hard it was to push Mozilla just to support Windows Group Policy along with other enterprise requirements and they were simply <i>not interested</i> in enterprise. Even though later they did some bare minimum to support it.</p>
]]></description><pubDate>Sat, 17 Oct 2026 18:11:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=50133518</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50133518</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50133518</guid></item><item><title><![CDATA[New comment by ksec in "Solar surpasses nuclear power globally for first time"]]></title><description><![CDATA[
<p>China themselves could have installed all of that capacity. But they are limited by batteries and other infrastructure and are catching up to those while planning a bigger play in the dessert solar farm.<p>They plan to increase 50% for Wind and Solar in 5 years, and possibly double in 10 years. Since 80%+ of all future planned Nuclear reactor are also in China, they would have more than double their renewable energy in 10 years. China is the number one in electricity production and usage, more than twice the size of US and 33%+ of the world. Given the size of China this is both exciting and scary.</p>
]]></description><pubDate>Sat, 17 Oct 2026 15:10:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=50131818</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50131818</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50131818</guid></item><item><title><![CDATA[New comment by ksec in "JPEG XL vs. AVIF for web use-cases"]]></title><description><![CDATA[
<p>>now there are comparisons popping up showing how AVIF actually compresses better.<p>You perfectly summarise how I felt as well. The revisionist also tries to paint the story as JPEG XL was first banned due to security issues which is again not true.<p>But that is OK. Since JPEG XL has finally and rightfully won its place, mostly thanks for Safari. We can now hopefully wait for better encoder.</p>
]]></description><pubDate>Sat, 17 Oct 2026 14:34:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=50131550</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50131550</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50131550</guid></item><item><title><![CDATA[New comment by ksec in "Apple routed a graphite pipe through the iPhone Duo's hinge to dissipate heat"]]></title><description><![CDATA[
<p>It wasn't always the case with software, before the internet era and updates. Software were done with a lot more cares because burning discs and distribution were costly. Exactly the same reason why Hardware put a lot of thoughts into it for failure because recalling product is expensive.</p>
]]></description><pubDate>Fri, 16 Oct 2026 22:27:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=50125605</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50125605</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50125605</guid></item><item><title><![CDATA[New comment by ksec in "Apple routed a graphite pipe through the iPhone Duo's hinge to dissipate heat"]]></title><description><![CDATA[
<p>I think you just happen to have the worst era in MacBook hardware. Happening 2015 - 2020. It has gotten better or back on track since then.<p>Keyboard is finally back to semi decent now. The old scissor is still better. But I think 2024 or 2025 they finally make some minor changes that is closer to old scissors.</p>
]]></description><pubDate>Fri, 16 Oct 2026 22:22:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=50125558</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50125558</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50125558</guid></item><item><title><![CDATA[New comment by ksec in "JPEG XL vs. AVIF for web use-cases"]]></title><description><![CDATA[
<p>Thank You. I was about to post I suspect both of those images would have worked better with JXL lossless.<p>Curious what is the better encoder here referring to?</p>
]]></description><pubDate>Fri, 16 Oct 2026 20:48:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=50124451</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50124451</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50124451</guid></item><item><title><![CDATA[New comment by ksec in "JPEG XL vs. AVIF for web use-cases"]]></title><description><![CDATA[
<p>I don't get it. And to me it wasn't clear in the post. As others have explained the container and codec are two separate issues.</p>
]]></description><pubDate>Fri, 16 Oct 2026 20:43:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=50124374</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50124374</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50124374</guid></item><item><title><![CDATA[New comment by ksec in "JPEG XL vs. AVIF for web use-cases"]]></title><description><![CDATA[
<p>That was done before AVIF had any improvements. Arguably one could even say JPEG XL competition brought the best of AVIF out.</p>
]]></description><pubDate>Fri, 16 Oct 2026 20:38:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=50124313</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50124313</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50124313</guid></item><item><title><![CDATA[New comment by ksec in "JPEG XL vs. AVIF for web use-cases"]]></title><description><![CDATA[
<p>It extracts the already quantized DCT coefficients and related data from the JPEG bitstream and re-encodes them with JPEG XL’s more efficient entropy coding and container,<p>Think of it as zip compression that is specially designed for JPEG and putting the JPEG data in a different/better container.</p>
]]></description><pubDate>Fri, 16 Oct 2026 20:34:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=50124265</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50124265</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50124265</guid></item><item><title><![CDATA[New comment by ksec in "JPEG XL vs. AVIF for web use-cases"]]></title><description><![CDATA[
<p>AVIF ( or even AV1 itself ) has had massive increase in quality improvements over the past 6 years. JPEG XL was close to release in 2020 and finalised in 2021. A lot of the sentiments hold true back then.<p>JPEG XL has always been targeting high quality encoding metric first before the lower end low BPP images, which AV1 excels at with or without the last 6 years of improvements.<p>The current top comments about MP3 and LAME is again about how encoder extract maximum potential. JPEG XL was may be the best in 2021, but has been fighting for survival since then.<p>There a lot of different images that JPEG XL encode better. Screenshots with text is known to be not something they have optimised for or think it could be good at. Lossless mode may be better. Edit: As one of the other comment here proved my point.<p>Had all of these, even just a hint of AVIF improvement be told, may be the sentiments would have been a little different. But then again I am not one who would trust the same people who sold me WebP and AOM roadmaps.<p>But at least AV2 is coming. And JPEG XL is finally in every browser. Hopefully we can all have something even better in the future.</p>
]]></description><pubDate>Fri, 16 Oct 2026 20:28:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=50124173</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50124173</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50124173</guid></item><item><title><![CDATA[New comment by ksec in "Apple may have an iPhone 18 Pro demand problem"]]></title><description><![CDATA[
<p>I thought Apple did poorly in this year 18 Pro Marketing.<p>The A20 Pro was a massive jump in performance per watt, meaning higher efficiency. A lot of site that latter discovered what A20 Pro were doing thought Apple under sell its achievement.<p>They should have provided battery life compare to 14 Pro and 15 Pro. Which is anywhere from 30% to 40% more. That is a huge jump and a lot of people are still on 13 - 15 range. That single reason should have pushed an upgrading cycle alone.<p>Every other phone has increased their price for a lot more in terms of percentage. Apple is actually on the lower side especially to entry model. Some how this message should have been marketed. A lot of iPhone user aren't aware that Android have gotten a lot more expensive as well for their flagship.</p>
]]></description><pubDate>Sun, 11 Oct 2026 01:52:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=50039050</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50039050</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50039050</guid></item><item><title><![CDATA[New comment by ksec in "Apple may have an iPhone 18 Pro demand problem"]]></title><description><![CDATA[
<p>I would expect the 18 Pro to have 30% more battery life if not more compared to 15 Pro on a new battery.</p>
]]></description><pubDate>Sun, 11 Oct 2026 01:45:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=50039012</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50039012</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50039012</guid></item><item><title><![CDATA[ZJIT is now as fast as YJIT]]></title><description><![CDATA[
<p>Article URL: <a href="https://railsatscale.com/2026-10-09-zjit-is-now-as-fast-as-yjit/">https://railsatscale.com/2026-10-09-zjit-is-now-as-fast-as-yjit/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=50035383">https://news.ycombinator.com/item?id=50035383</a></p>
<p>Points: 4</p>
<p># Comments: 0</p>
]]></description><pubDate>Sat, 10 Oct 2026 17:55:14 +0000</pubDate><link>https://railsatscale.com/2026-10-09-zjit-is-now-as-fast-as-yjit/</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50035383</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50035383</guid></item><item><title><![CDATA[New comment by ksec in "Our $445M Series D"]]></title><description><![CDATA[
<p>>we're paying taxes because we're profitable.<p>I guess the question is why not invest those profits to further expand when there are already a backlog of orders to fill.<p>But on the other hand Huge Congrats being a profitable company! Hardware business is insanely brutal, and having the backlog is great to hear. AMD being investor I hope you guys get Zen 6c and Zen 7c earlier in the future.</p>
]]></description><pubDate>Sat, 10 Oct 2026 01:03:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=50028447</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50028447</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50028447</guid></item><item><title><![CDATA[New comment by ksec in "Cloudflare acquires Deno"]]></title><description><![CDATA[
<p>>but there is nothing to “win” here.<p>In the context of Deno here, it obviously implies market share.</p>
]]></description><pubDate>Sat, 10 Oct 2026 00:45:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=50028321</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50028321</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50028321</guid></item><item><title><![CDATA[New comment by ksec in "Shipping JPEG XL in Chrome"]]></title><description><![CDATA[
<p>1. Not true before modern AV1 encoder got major improvements in the past 3 years. There is no reason why JPEG-XL can't be improved in the low bpp range. JPEG itself got improvement 20 years after its initial introduction. Not to mention the last time I check, JPEG XL is still better at high end fidelity.<p>2. JPEG XL lossless can be 10-13% or in some cases up to 50% better. Of course WebP could also be better in some cases. And again, JPEG-XL potential is far fully optimised. Both in encoder and decoder.<p>On another note, the AOM camp should really have played the AV2 card suggesting it to be better.</p>
]]></description><pubDate>Thu, 08 Oct 2026 18:23:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=50009823</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50009823</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50009823</guid></item><item><title><![CDATA[New comment by ksec in "Shipping JPEG XL in Chrome"]]></title><description><![CDATA[
<p>Just want to say thank you for keeping the record straight. I am too late to this thread.</p>
]]></description><pubDate>Thu, 08 Oct 2026 18:08:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=50009582</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50009582</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50009582</guid></item><item><title><![CDATA[New comment by ksec in "Shipping JPEG XL in Chrome"]]></title><description><![CDATA[
<p>Again, JPEG XL is not currently optimised for low bpp images. Compared to AVIF which just spend the past 3 years optimising it before writing that blog post.</p>
]]></description><pubDate>Thu, 08 Oct 2026 18:01:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=50009469</link><dc:creator>ksec</dc:creator><comments>https://news.ycombinator.com/item?id=50009469</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50009469</guid></item></channel></rss>