<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: serhalp</title><link>https://news.ycombinator.com/user?id=serhalp</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 22 Apr 2026 08:34:56 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=serhalp" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by serhalp in "Vercel April 2026 security incident"]]></title><description><![CDATA[
<p>Netlify and Vercel both use AWS. AFAIK neither uses Cloudflare. Vercel did use Cloudflare for parts of its infra until about a year ago though.</p>
]]></description><pubDate>Sun, 19 Apr 2026 23:09:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=47828544</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=47828544</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47828544</guid></item><item><title><![CDATA[New comment by serhalp in "NPMX – a fast, modern browser for the NPM registry"]]></title><description><![CDATA[
<p>We're working on it :)</p>
]]></description><pubDate>Sun, 15 Feb 2026 15:25:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=47024415</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=47024415</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47024415</guid></item><item><title><![CDATA[New comment by serhalp in "Front end frameworks: a (belated) 2025 year in review"]]></title><description><![CDATA[
<p>My job involves keeping a finger on the pulse of frontend web frameworks. I wrote a post about all I tracked in 2025.<p>Themes I saw:
1. So. Many. CVEs.
2. The Next.js team delivered!
3. Frameworks made changes for coding agents
4. RSCs entered a new phase
5. Signals won... almost
6. Rustification continues</p>
]]></description><pubDate>Wed, 28 Jan 2026 15:11:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=46796357</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=46796357</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46796357</guid></item><item><title><![CDATA[Front end frameworks: a (belated) 2025 year in review]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.netlify.com/blog/web-frameworks-2025-year-in-review/">https://www.netlify.com/blog/web-frameworks-2025-year-in-review/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46796356">https://news.ycombinator.com/item?id=46796356</a></p>
<p>Points: 3</p>
<p># Comments: 1</p>
]]></description><pubDate>Wed, 28 Jan 2026 15:11:47 +0000</pubDate><link>https://www.netlify.com/blog/web-frameworks-2025-year-in-review/</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=46796356</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46796356</guid></item><item><title><![CDATA[New comment by serhalp in "Side-by-side comparison of how AI models answer moral dilemmas"]]></title><description><![CDATA[
<p>Hey, I built something somewhat similar a couple months ago: <a href="https://triple-buzzer.netlify.app/" rel="nofollow">https://triple-buzzer.netlify.app/</a>.</p>
]]></description><pubDate>Sat, 10 Jan 2026 21:26:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=46570077</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=46570077</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46570077</guid></item><item><title><![CDATA[New comment by serhalp in "RCE Vulnerability in React and Next.js"]]></title><description><![CDATA[
<p>TanStack Start has its own implementation of Server Functions: <a href="https://tanstack.com/start/latest/docs/framework/solid/guide/server-functions" rel="nofollow">https://tanstack.com/start/latest/docs/framework/solid/guide...</a>. It doesn't use React Server Functions, in part because it intends to be agnostic of the rendering framework (it currently supports React and Solid).<p>To be fair, they also haven't released (even experimental) RSC support yet, so maybe they lucked out on timing here.</p>
]]></description><pubDate>Wed, 03 Dec 2025 19:12:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=46138624</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=46138624</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46138624</guid></item><item><title><![CDATA[New comment by serhalp in "RCE Vulnerability in React and Next.js"]]></title><description><![CDATA[
<p>Same for Netlify: <a href="https://www.netlify.com/changelog/2025-12-03-react-security-vulnerability-response/" rel="nofollow">https://www.netlify.com/changelog/2025-12-03-react-security-...</a><p>and Deno Deploy/Subhosting: <a href="https://deno.com/blog/react-server-functions-rce" rel="nofollow">https://deno.com/blog/react-server-functions-rce</a></p>
]]></description><pubDate>Wed, 03 Dec 2025 19:06:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=46138562</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=46138562</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46138562</guid></item><item><title><![CDATA[New comment by serhalp in "The many JavaScript runtimes of the last decade"]]></title><description><![CDATA[
<p>> I really, really liked how Cargo did things (e.g. optional dependencies and rigid library structure) and it'd be incredible to have that for the JavaScript ecosystem.<p>FYI: <a href="https://thenewstack.io/vites-creator-on-a-unified-javascript-toolchain-and-vite" rel="nofollow">https://thenewstack.io/vites-creator-on-a-unified-javascript...</a></p>
]]></description><pubDate>Mon, 28 Jul 2025 01:00:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=44706159</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=44706159</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44706159</guid></item><item><title><![CDATA[New comment by serhalp in "Vanilla JavaScript support for Tailwind Plus"]]></title><description><![CDATA[
<p>You can use the Tailwind Prettier plugin to automate this: <a href="https://github.com/tailwindlabs/prettier-plugin-tailwindcss">https://github.com/tailwindlabs/prettier-plugin-tailwindcss</a>. I'm not sure if it would support the precise grouping and sorting you prefer, but it may be worth it anyway!</p>
]]></description><pubDate>Sat, 26 Jul 2025 18:50:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=44696198</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=44696198</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44696198</guid></item><item><title><![CDATA[New comment by serhalp in "Netlify deploys hundreds of thousands of Next.js sites – here's what challenging"]]></title><description><![CDATA[
<p>The ability to self-host on serverless compute is just a subset of the challenges. Even with your own VPS or ECS setup, I think it's legitimate to say a serious project requires server redundancy, and as soon as you have more than one running server it opens up requirements to synchronize cache state, which is a significant challenge. This has nothing to do with serverless architecture.</p>
]]></description><pubDate>Thu, 27 Mar 2025 15:40:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=43494778</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=43494778</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43494778</guid></item><item><title><![CDATA[New comment by serhalp in "Netlify deploys hundreds of thousands of Next.js sites – here's what challenging"]]></title><description><![CDATA[
<p>Ooh, interesting. We didn't know about this. Is this it? <a href="https://github.com/caching-tools/next-shared-cache/tree/canary/packages/cache-handler" rel="nofollow">https://github.com/caching-tools/next-shared-cache/tree/cana...</a></p>
]]></description><pubDate>Thu, 27 Mar 2025 15:08:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=43494453</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=43494453</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43494453</guid></item><item><title><![CDATA[New comment by serhalp in "Netlify deploys hundreds of thousands of Next.js sites – here's what challenging"]]></title><description><![CDATA[
<p>This is a great point and definitely something we're mindful of. That sentence actually ended with "and share these with the community" in the draft, but we can't make promises on behalf of the Next.js team.<p>Our hope is that the OpenNext initiative's growth and connections with the Next.js team is just a first step toward shifting some Next.js governance out to the open. The article calls out that the OpenNext members are hoping to contribute to public RFCs in the future, with Next.js core team collaboration.</p>
]]></description><pubDate>Thu, 27 Mar 2025 14:59:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=43494350</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=43494350</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43494350</guid></item><item><title><![CDATA[Netlify deploys hundreds of thousands of Next.js sites – here's what challenging]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.netlify.com/blog/how-we-run-nextjs/">https://www.netlify.com/blog/how-we-run-nextjs/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=43493552">https://news.ycombinator.com/item?id=43493552</a></p>
<p>Points: 89</p>
<p># Comments: 25</p>
]]></description><pubDate>Thu, 27 Mar 2025 13:40:55 +0000</pubDate><link>https://www.netlify.com/blog/how-we-run-nextjs/</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=43493552</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43493552</guid></item><item><title><![CDATA[Netlify joins OpenNext, collaborates with SST and Cloudflare]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.netlify.com/blog/netlify-joins-opennext/">https://www.netlify.com/blog/netlify-joins-opennext/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=41929469">https://news.ycombinator.com/item?id=41929469</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 23 Oct 2024 21:37:34 +0000</pubDate><link>https://www.netlify.com/blog/netlify-joins-opennext/</link><dc:creator>serhalp</dc:creator><comments>https://news.ycombinator.com/item?id=41929469</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41929469</guid></item></channel></rss>