<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: gregfurman</title><link>https://news.ycombinator.com/user?id=gregfurman</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 14:07:17 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=gregfurman" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by gregfurman in "MinIO repository is no longer maintained"]]></title><description><![CDATA[
<p>That’s fair. There’s still a free tier that you can use.<p><a href="https://blog.localstack.cloud/the-road-ahead-for-localstack/#will-i-need-to-start-paying-for-localstack-for-aws" rel="nofollow">https://blog.localstack.cloud/the-road-ahead-for-localstack/...</a><p>But IMO, LocalStack community’s S3 service is pretty stable, so I’m doubtful there’ll be much parity drift in the short to medium term.</p>
]]></description><pubDate>Sat, 14 Feb 2026 19:26:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=47017477</link><dc:creator>gregfurman</dc:creator><comments>https://news.ycombinator.com/item?id=47017477</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47017477</guid></item><item><title><![CDATA[New comment by gregfurman in "MinIO repository is no longer maintained"]]></title><description><![CDATA[
<p>Have you heard of LocalStack’s AWS emulator? [1] It’s runnable within a docker container and has a high fidelity S3 service.<p>Disclosure, I’m a SWE at LocalStack.<p>[1] <a href="https://github.com/localstack/localstack" rel="nofollow">https://github.com/localstack/localstack</a></p>
]]></description><pubDate>Fri, 13 Feb 2026 20:50:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=47007645</link><dc:creator>gregfurman</dc:creator><comments>https://news.ycombinator.com/item?id=47007645</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47007645</guid></item><item><title><![CDATA[New comment by gregfurman in "What If We Could Rebuild Kafka from Scratch?"]]></title><description><![CDATA[
<p>Fluvio looks awesome!<p>Any chance you’re going to be reviving support for the Kafka wire protocol?<p><a href="https://github.com/infinyon/fluvio/issues/4259">https://github.com/infinyon/fluvio/issues/4259</a></p>
]]></description><pubDate>Fri, 25 Apr 2025 20:09:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=43798034</link><dc:creator>gregfurman</dc:creator><comments>https://news.ycombinator.com/item?id=43798034</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43798034</guid></item><item><title><![CDATA[New comment by gregfurman in "Go, Containers, and the Linux Scheduler"]]></title><description><![CDATA[
<p>Discovered this sometime last year in my previous role as a platform engineer managing our on-prem kubernetes cluster as well as the CI/CD pipeline infrastructure.<p>Although I saw this dissonance  between actual and assigned CPU causing issues, particularly CPU throttling, I struggled to find a scalable solution that would affect all Go deployments on the cluster.<p>Getting all devs to include that autoprocs dependency was not exactly an option for hundreds of projects. Alternatively, setting all CPU request/limit to a whole number and then assigning that to a GOMAXPROCS environment variable in a k8s manifest was also clunky and infeasible.<p>I ended up just using this GOMAXPROCS variable for some of our more highly multithreaded applications which yielded some improvements but I’ve yet to find a solution that is applicable to all deployments in a microservices architecture with a high variability of CPU requirements for each project.</p>
]]></description><pubDate>Tue, 07 Nov 2023 20:19:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=38182214</link><dc:creator>gregfurman</dc:creator><comments>https://news.ycombinator.com/item?id=38182214</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38182214</guid></item></channel></rss>